Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Recalling DSN's from ML1 volume which does not show up in 3.

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
rahulbank

New User


Joined: 25 Sep 2008
Posts: 66
Location: Bengaluruuuuuu

PostPosted: Tue Nov 04, 2008 4:40 pm    Post subject: Recalling DSN's from ML1 volume which does not show up in 3.
Reply with quote

Hi All,

When I do an hsend list mcds on a dsn it shows migvol=online, this migvol is an ML1 volume, I am not able to see this dsn in3.4.

When I do an hsend fixcds d NBKMT1S.NOALT.D201008 display it shows the ml1 volume,how can i progress further on restoring it

This is some more detail from the command.
+0080 00000000 00000000 00000000 00000000 00000000 00000000 0000000F 40E2D4D4
* SMM*
+00A0 C9C74BC8 D4C9C74B E3F1F9F2 F6F0F94B C6C3C8D7 4BC6C3C8 4BD1F8F3 F0F64040
*IG.HMIG.T192609.FCHP.FCH.J8306 *
Back to top
View user's profile Send private message

expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Tue Nov 04, 2008 4:49 pm    Post subject:
Reply with quote

If it does not show under 3.4 then the dataset is not catalogued.

Try to use HRECOVER from the backup sets.
Back to top
View user's profile Send private message
rahulbank

New User


Joined: 25 Sep 2008
Posts: 66
Location: Bengaluruuuuuu

PostPosted: Tue Nov 04, 2008 5:03 pm    Post subject:
Reply with quote

HRECOVER I do not have a bcds for this dsn....I was trying to understand can we recover from an ml1 as it is showing online one more info when i hit hsend fixcds d NBKMT1S.NOALT.D201008 assignedbit(on) it shows an ml1 volume now..but still not in 3.4...
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Wed Nov 05, 2008 12:13 am    Post subject:
Reply with quote

Hello,

Quote:
but still not in 3.4...
Until an entry is in the catalog, it cannot show in 3.4.

I believe you will need to work with your storage management people to manually retrieve the file from an archive volume and catalog it. Once this is done, you will be able to see the dataset in 3.4 and it will be online rather than migrated.
Back to top
View user's profile Send private message
rahulbank

New User


Joined: 25 Sep 2008
Posts: 66
Location: Bengaluruuuuuu

PostPosted: Wed Nov 05, 2008 8:56 am    Post subject:
Reply with quote

I am the storage guy icon_sad.gif
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Wed Nov 05, 2008 9:14 am    Post subject: Reply to: Recalling DSN's from ML1 volume which does not sho
Reply with quote

Quote:
I am the storage guy


Ooops. . . Didn't know that.

Is there possibly an old volume backup of the file from some previous full-volume system backup?

You might open an issue with IBM support.

Maybe one of our storage gurus will be online soon. . .
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Wed Nov 05, 2008 12:25 pm    Post subject:
Reply with quote

As suggested previously, try to use the backup version to perform HRECOVER of the dataset.

Also in the past I have cataloged a dataset to volser MIGRAT which then allows HSM to recall. However this does not always work. You will need to relate the DSN against the HSM internal DSN and then list the VTOC of the ML1 volume (assumed to be DASD) and if it is there -OK. If not - the options are somewhat limited to none if HRECOVER has failed.

I suggest that you read, reread and execute the HSM AUDIT functions using NOFIX mode - unless you can guarantee absolutely no HSM activity during the time taken to perform the audit.

At least with NOFIX it will not attempt corrections for ongoing processes that have changed the CDS inflight.
Back to top
View user's profile Send private message
rahulbank

New User


Joined: 25 Sep 2008
Posts: 66
Location: Bengaluruuuuuu

PostPosted: Thu Dec 04, 2008 5:57 pm    Post subject:
Reply with quote

I tried Define Nonvsam name devicetype volumes(migrat) and the dsn got cataloged in 3.4 but it will not recall as the hsm believes migratvolume = online and when recalling it says dataset not migrated...any suggestions...
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10231
Location: italy

PostPosted: Thu Dec 04, 2008 6:03 pm    Post subject: Reply to: Recalling DSN's from ML1 volume which does not sho
Reply with quote

if the dataset is mission critical You might

find out what a catalog entry for a migrated dataset looks like ( hex dump of the catalog records )

do the same for a generic dataset
run a define nonvsam for he dataset You are trying to recall

and using any zapping tool ( ditto should be able to do it ) fix the record
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Thu Dec 04, 2008 7:48 pm    Post subject:
Reply with quote

You need to look at the MCDS record for the dataset and determine the HSM internal dataset name from the M (or is it A ?) record.

Then do a 3.4 on the ML1 volume that it thinks the internal dataset resides on. If the dataset is there - all well and good. Recatalog the dataset to volser=MIGRAT and then the RECALL should work OK.

If the internal dataset is not on the ML1 volume shown in the MCDS record, then the record is invalid and the dataset will never ever be able to be recalled. Which unfortunately from you last post appears to be the case icon_cry.gif

Hence my recommendation to perform the AUDITs on ALL of the CDS files. Find out what is wrong, and fix it, before it comes back and bites you on the butt !!!
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Storing huge volume of data, compare ... Pradeep K M All Other Mainframe Topics 3 Mon Jan 16, 2017 5:08 pm
No new posts How to show message using batch jobs madprasy TSO/ISPF 7 Fri Sep 09, 2016 6:55 pm
No new posts Reading selected volumes of a multi-v... RickBig JCL & VSAM 6 Wed Jul 13, 2016 7:26 pm
No new posts Need to show date in "DYYMMDD.TH... deepak_shrivastava DFSORT/ICETOOL 2 Tue Jan 05, 2016 7:15 pm
No new posts DFSMSdss full volume backups JCL when... Alan Playford IBM Tools 3 Thu Feb 05, 2015 4:50 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us