That sounds weird. >From what I can tell, there is nothing in Extended Addressability or Auth Assembler to explain what you are seeing.
Is your init routine still waiting on EAEASWT? (sounds like it is as the TCB is still hanging around) Could you use IEFBR14 as the INIT routine and then put your init logic into the jobstep program in the JCL for the created address space? Rob Scott Rocket Software, Inc 275 Grove Street Newton, MA 02466 617-614-2305 [EMAIL PROTECTED] http://www.rs.com/portfolio/mxi/ -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Binyamin Dissen Sent: 20 September 2006 05:16 To: [email protected] Subject: The ASCRE initialization routine It appears that all task related storage, including loaded modules, are released after the initialization routine ends despite the fact that the TCB remains around. The CDE points to freed storage. The PC routines are defined. Unfortunately the load module is gone. Is there some documented restriction as to what it can do? -- Binyamin Dissen <[EMAIL PROTECTED]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- 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
