Joe Denison wrote:
I'm having an issue with REXX EXECs (interpreted, not compiled) that seem to *not* free storage after they terminate. Is this a known issue? Has anyone else experienced this?
It would be helpful if you could go at least one step beyond what you reported here to determine whether the growth that you're seeing is in a particular subpool. Subpool 78 is intentionally shared by all TSO tasks to permit storage that should persist across command and other task terminations to do so, and authorized programs have the ability to attribute storage ownership to the job step TCB for similar reasons. The identity of the subpool would cut the list of potential culprits down significantly although it would hardly point at just one.
Bob Wright - MVS Service Aids ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
