Freeing subpool 236 / 237 seems like a bad idea. As with most private-area subpools, freeing done by the system depends on which task owns the storage, as it is upon termination of that owning task that the storage is freed.
<snip from the book> Virtual storage is located within the scheduler work area (SWA). The storage is freed at the end of the started task or at initiator termination for subpool 236 and at the end of the job for subpool 237. The NSHSPL and NSHSPV parameters on the ATTACH or ATTACHX macro invocation used to create the currently active task determine ownership of the subpool. If the currently active task was given ownership of the subpool, then the TCB of the currently active task owns the storage in this subpool. If the currently active task is sharing this subpool with the attaching task, then the TCB of the attaching task owns the storage in this subpool. <end snip> I don't know anything about converter and interpreter routines provided by JES. I hope that their use is an intended programming interface. If it's not, I hope the risk is worth it, but you should have no expectations that behavior will be what you need. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
