>Let me just say that IBM wants us to change this program to run as STC >and not JOB. They want to wash their hands of LSQA cleanup in an INIT.
I find this conclusion extremely unlikely. They (we) might want you to change the program to run as STC so that you can avoid your own program's problem. If there is an IBM problem with LSQA cleanup in an initiator, then IBM in all likelihood will not "wash their hands" of it. As has been stated in many of the appends, LSQA by definition does not get freed automatically. Its life is the life of the address space, not the life of a job. CheckRegionLoss is very nice, but of course simply helps you to avoid running aground on problems that exist, whether they be in IBM, vendor, or customer code. It does not fix such problems. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
