-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Barkow, Eileen Sent: Wednesday, April 11, 2007 12:39 PM To: IBM-MAIN@BAMA.UA.EDU Subject: gdg question
can one of you gurus out there please shed some light on this, since i am not sure what the answer should be or whether or not this is normal, since these jobs supposedly have been running and working for the last 20 years (although i am not sure if they ever ran at the same time). =20 normally these batch jobs do not pose a problem, but the one waiting on the dataset (JOBA) was also holding another dataset that=20 CICS needed and could not get to. <SNIP> I'll try to answer this. IFF the file had been created on DASD you probably would not have seen a problem. BUT because the file was created on a removeable media (TAPE/CART), the CATALOG process does not complete until JOB END (which I would think should be step end, but hey, what do I know?). This happens whether or not the file is SMS managed when it comes to "tape". However, with DASD, DFP handles the cataloging very differently, and even holds the new generation in a quasi done state so that if you have a second job with (+1), it will get a new G0000V00 number. Meanwhile, the GDG Base is held by the "TAPE" job for the duration, which is what appears to have caused your problem. Regards, Steve Thompson ---------------------------------------------------------------------- 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
