Esmie, I recommend you check the dasd volume(s) to make sure the dataset that you deleted using noscratch is not still there. I am out of ideas. If no one else figures it out, you could search ibmlink or open a problem with IBM for assistance. Sorry, John esmie moo <[EMAIL PROTECTED]> wrote:
> The dsn is created on dasd and SMS managed. I checked the disk > status and it is always online. The job creates the dsn in the SMS > pool which has 23 dasds in that storage pool. > > John Kington <[EMAIL PROTECTED]> wrote: Keeping with top posting: > Esmie, > Do you recall whether the oldest generation was on dasd or tape? The > scratch error > indicates that it was dasd and the volume was not online. Maybe you > reclaimed a > dasd volume or have a dasd volume offline? > Regards, > John > > >Thanks John. Yes, I noticed that the catalog entry was present. I then > scratched the entry (del noscr). But I >cannot understand why this > happened. I checked the syslog but found nothing that would indicate any > type of a >problem. Any other suggestions? > >>My job put out the >> following error: >> >>IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0 >>IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00 >>IEC331I 050-092(04840000,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3 >>IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE >>IGD104I DATAALL.REND.PC5.PROD.VMAXTD.G0593V00 RETAINED, D >>I ran a diagnose on the volume (compared catalog with vvds and vvds with >>the catalog) but no errors were found catalog. The job creates a gdg with >>a limit of 40 generations. I am not sure why this error occurred. Any >>suggestions? >> ---------------------------------------------------------------------- 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
