You could skip over the bad GDG number to get your production going again while fixing the unrecallable dataset.
On Mon, Aug 1, 2011 at 8:20 AM, O'Brien, David W. (NIH/CIT) [C] <obrie...@mail.nih.gov> wrote: > Gerry, > > Have you tried Delete / noscratch to get around the GDG allocate problem? > > To delete the HSM entry will probably require a Fixcds command, see the HSM > Diagnosis guide for more info. > > Thank You, > Dave O'Brien > NIH Contractor > ________________________________________ > From: Anstey, Gerry [gerry.ans...@jpmorgan.com] > Sent: Monday, August 01, 2011 9:08 AM > To: IBM-MAIN@bama.ua.edu > Subject: Orphan GDG problem > > All, Any ideas here: > > We have a job that fails when creating a GDG entry, > > .ARC1001I PGINTT11.B671.TRANSACT.WINS.BKUP.G1460V00 RECALL FAILED, RC=0002, > REAS=0000 > .ARC1102I DATA SET IS NOT MIGRATED/BACKED UP > .IEF344I PRAH673 IEBGENER SYSUT2 - ALLOCATION FAILED DUE TO DATA FACILITY > SYSTEM ERROR > > The entry concerned is showing as migrated > > Command - Enter "/" to select action Message > Volume . > ------------------------------------------------------------------------------- > . > PGINTT11.B671.TRANSACT.WINS.BKUP ?????? > . > PGINTT11.B671.TRANSACT.WINS.BKUP.G1450V00 > HAP2NC+ . > PGINTT11.B671.TRANSACT.WINS.BKUP.G1451V00 > HAP2NC+ . > PGINTT11.B671.TRANSACT.WINS.BKUP.G1452V00 > HAP2M8+ . > PGINTT11.B671.TRANSACT.WINS.BKUP.G1453V00 > HAP2M8+ . > PGINTT11.B671.TRANSACT.WINS.BKUP.G1454V00 > HAP2M8+ . > PGINTT11.B671.TRANSACT.WINS.BKUP.G1455V00 > HAP2M8+ . > PGINTT11.B671.TRANSACT.WINS.BKUP.G1456V00 > HAP2M8+ . > PGINTT11.B671.TRANSACT.WINS.BKUP.G1457V00 > HAP1BC+ . > PGINTT11.B671.TRANSACT.WINS.BKUP.G1458V00 > HAP13F+ . > PGINTT11.B671.TRANSACT.WINS.BKUP.G1459V00 > HAP109+ . > PGINTT11.B671.TRANSACT.WINS.BKUP.G1460V00 > MIGRAT2 . > ***************************** End of Data Set list > **************************** . > > The problem is that I cannot delete the file using HDELETE, or IDCAMS with > NVS, or standard IEFBR14 with an uncatlg > > Whatever we try we get the message above, ie recall failed, RC=0002 > > It looks like the file has beed created spuriously some how and is in some > sort of orphan state so when we run the job to create +1 HSM seems to want to > recall the orphan version but fails as above in the process. > > Any ideas how we can delete this entry? > > Many thanks > > Gerry Anstey > WSS Technology EMEA - COSMIC PSD | World Wide Securities Services | J.P. > Morgan | Chaseside, Bournemouth, BH7 7DA > T:+44 (0)1202 342596,1 | Email: gerry.ans...@jpmorgan.com > > > > This email is confidential and subject to important disclaimers and > conditions including on offers for the purchase or sale of > securities, accuracy and completeness of information, viruses, > confidentiality, legal privilege, and legal entity disclaimers, > available at http://www.jpmorgan.com/pages/disclosures/email. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
