> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Jim Mulder > Sent: Wednesday, September 20, 2006 3:40 PM > To: [email protected] > Subject: Re: The ASCRE initialization routine > > IBM Mainframe Discussion List <[email protected]> wrote on 09/20/2006 > 11:21:40 AM: > /snip/ > Since the region subpools are not freed, any region subpools used > during the initialization routine will continue to be key 0, when they > would usually be key 8 or the PPT key. So, for example, if you LOAD > a non-reentrant module during the initialization routine, subpool 251 > will be created as a key 0 subpool. Then later when your jobstep task > gets attached, since the region was not freed, subpool 251 will still > exist as a key 0 subpool. Subsequent LOADs of non-reentrant modules > into subpool 251 will be into key 0 storage (and fetch protected), > so you won't be able to execute them unless you are running key 0. > Also, the REGION/IEFUSI limits will not be honored. > > Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY
I would have guessed that attaching the job step task (EXEC PGM=name) would specify on the ATTACHX macro no shared subpools. Doesn't make sense for a job step task to share any subpools with the higher job step tasks. Jeffrey D. Smith Principal Product Architect Farsight Systems Corporation 700 KEN PRATT BLVD. #204-159 LONGMONT, CO 80501-6452 303-774-9381 direct 303-484-6170 FAX http://www.farsight-systems.com/ comments are invited on my encryption project ---------------------------------------------------------------------- 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
