Hi Darth,
By any chance is the catalogue containing the GDG disconnected?. If that were the case, then the MOD would try to write a new dataset, thus requiring space. HTH, Linda Mooney ----- Original Message ----- From: "Allan Staller" <[email protected]> To: [email protected] Sent: Thursday, May 27, 2010 9:06:59 AM GMT -08:00 US/Canada Pacific Subject: Re: zOS1.11 Allocation error Sounds like it could be related to the IEFBR14 change to delete files w/o recall </snip> A stub of the JCL: //DD29 DD DSN=JSDT.D1MKE.IM.RUN2.DTGDIG01, // DISP=(MOD,KEEP,KEEP) Prior to the implementation of zOS1.11, this worked successfully every time. Since we implemented 1.11, every job they have using this process abends every day with the following: snippage... Their work-around is to issue HRECALL's for the migrated GDG's & then re-submit the job. We're following up with IBM, but I'm curious to know if anyone on this august list has implemented 1.11 and seen this same issue. </snip> thanks - ddk ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
