So I will use an infamous phrase here: Open an SR with IBM before you do anything else.
Sometimes they have tools that can help you or at least provide guidance that this list may not be privy to. Next, you need to know what volume the dataset resided on. If you do full volume dumps - weekly, monthly or daily - you might have a chance to find the dataset. DFHSM only knows what it knows. If you did a physical delete and not removed the catalog entry, then you should see a LISTC or 3.4 entry for Data_set_Deleted_Name MIGRAT If the problem is the dataset was just plain deleted and there is no longer a catalog entry, you need to find a full volume or other DR volume backup for recovery. DFHSM will have nothing available to you. If there is anything left in DFHSM, then either a product like VANTAGE with the DFHSM function included could help. Otherwise contact IBM. Please explain further what is the specific events and issues. Otherwise, open an SR with IBM quick. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Staller, Allan > Sent: Monday, June 20, 2016 10:30 AM > To: [email protected] > Subject: Re: DFHSM QUESTION - RECOVER DSN FROM ML2 VOLUME > > If the dataset was *DELETED* you will have a tough time. > > If the dataset was uncataloged, > > DEF NVSAM(name('dsn') DEVT(xxxx) VOL(MIGRAT) > > And then recall the dataset. > > <snip> > I cannot issue the HRECALL because the dsn doesn't exist. The same reason I > cannot issue the HRECOVER because there is no backup. > </snip> > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
