STOKEN does not change from one job (or job step) to another within an initiator address space. But all user-region storage is freed between those stages.
So if you loaded a module into user-region storage in a job and added that as an exit routine with modaddr and STOKEN, the system would find a match via STOKEN when that job was running. When the job ended, the storage would be freed. When the next job started, the system would still find a match via STOKEN and would call the exit routine, only the exit routine would not be there. That is, at minimum, a system integrity problem. Using LOAD with ADDR to an area that is in a suitable key and is not subject to "free region" would be needed. Peter Relson z/OS Core Techology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
