The index limit is built for 40. I checked the production run from the past 2 days and everything seems to be in order. I am still stumped as to what had happened.
"O'Brien, David W. (NIH/CIT) [C]" <[EMAIL PROTECTED]> wrote: No, if noscratch was specified and the gdg wrapped around then the dataset would not be able to roll in. Esmie, how many catalog entries exist under the base gdg name? Just do a 3.4 display under ispf. ________________________________ From: John Kington [mailto:[EMAIL PROTECTED] Sent: Tue 1/16/2007 8:36 AM To: [email protected] Subject: Re: CATALOG ERROR >Do you have noscratch specified in the GDG define? It should be scratch to have the oldest gdg automatically roll off to allow the next generation to be catalogued. The listcat should look as follows: ATTRIBUTES LIMIT-----------------10 SCRATCH NOEMPTY David, He must have had scratch in the GDG or the job would not have had a problem cataloging the new GDS. I do not have DFHSM so I don't know how management class attributes work in this situation. Regards, John ---------------------------------------------------------------------- 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 --------------------------------- The best gets better. See why everyone is raving about the All-new Yahoo! Mail. ---------------------------------------------------------------------- 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
