I am checking the journal file hoping to find any trace of the dsn.  I don't 
have a backup of the dsn that is why I am trying to find the ML2 volser.

I cannot issue the HRECALL because the dsn doesn't exist.  The same reason I 
cannot issue the HRECOVER because there is no backup.
--------------------------------------------
On Mon, 6/20/16, retired mainframer <retired-mainfra...@q.com> wrote:

 Subject: Re: DFHSM QUESTION - RECOVER DSN FROM ML2 VOLUME
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Monday, June 20, 2016, 1:05 PM
 
 Why are you looking in
 the JOURNAL?  It contains only "recent" data
 since the last CDS backup.  How long ago was the dataset
 migrated?  To find the DSN, you need to look in the backup
 copy that covers the time frame when the migration
 occurred.  But if you need to look up anything about the
 dataset, you really should be looking in the MCDS.
 
 Why do you think you need to
 know the ML2 volume?  ML2 datasets are catalogued on
 MIGRAT2.  Does the DSN show up in 3.4?
 What
 happens if you issue an HRECALL against the DSN?  If the
 migrated copy is valid, that should be all you need.  
 
 > -----Original Message-----
 > From: IBM Mainframe Discussion List
 [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On
 > Behalf Of willie bunter
 > Sent: Monday, June 20, 2016 9:35 AM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: DFHSM QUESTION - RECOVER DSN FROM
 ML2 VOLUME
 > 
 > Good
 Day To All,
 > 
 > I
 would like to recover a dsn which was migrated to ML2. 
 Because of a mistake in the
 > assigning
 of the management class no back up was taken.
 > 
 > I remember
 recovering a dsn under the same circumstances.  I remember
 locating the dsn in
 > the
 HSM.JOURNAL.BACKUP.V000xxxx (found in column 13 in HEX) and
 the volser of
 > the ML2. (which  I found
 in column 77)
 > 
 > I
 browsed the online HSM.JOURNAL (using the first and second
 HLQ)  however I was
 > unable to locate
 the dsn.  My question is do I need to wait for the CDS
 Journal backup to be
 > run (which will
 execute tonight at 8 p.m) or is there something else I can
 try?
 
 ----------------------------------------------------------------------
 For IBM-MAIN subscribe / signoff / archive
 access instructions,
 send email to lists...@listserv.ua.edu
 with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to