HSM Migrated DSN - How to find the MVS CATALOG DSN

jsrueg · New User Joined: 22 Jun 2006 Posts: 6

I've got several HSM migrated DSN's that's failing allocation with 213-2c. HSM log only shows the Migrated DSN. How can I find out the real MVS DSN that is in the Catalog?

enrico-sorichetti · Posted: Fri Apr 27, 2007 12:36 pm

A little clarification on how HSM works...

whenever ( according to HSM definition and/or SMS management class ) a dataset is migrated ( ML1/ML2 )
the MVS ( master/user ) catalog entry IS STILL there ...
the only difference is that the dasd volser is changed from a real volser to
( if I remember correctly ) MIGRAT which means that the dataset is now under control of HSM.

try an ISPF 3.4 to see if Your dataset is there and check the volser

regards

e.s

expat · Posted: Fri Apr 27, 2007 12:43 pm

Do you mean that the recall process is failing 213-2c.

jsrueg · New User Joined: 22 Jun 2006 Posts: 6

I'm trying to determine the MVS dataset name from the HSM migrated name that is on ML1/ML2. As you know HSM generates a name for the physical dataset once it is migrated. When I get the 213-2C from within DFHSM, it shows the HSM generated name. I'd like to find out what the real DSN is.

enrico-sorichetti · Posted: Fri Apr 27, 2007 10:49 pm

THE REAL DATASET NAME IS THE ONE YOU ARE USING IN YOUR JCL...

the logic is:
//jobname JOB
//stepname EXEC PGM=yourpgm
//ddname DD DISP=SHR,DSN=yourdatasetname

You do not have to care where yourdatasetname resides..
it is cataloged and if in the catalog the volser is MIGRAT HSM will recall it
putting in real volume... and afterwards it will be ready to be used

if in the hsm log You have errors, then somewhere in your syslogs and/or the console log there must be some messages regarding recall errors relative to the REAL DATASET NAME

It seems to me that some messages were lost

regards

e.s

expat · Posted: Sat Apr 28, 2007 1:59 pm

What are you trying to do with the HSM generated name. In 99.99% of cases there is no need to know the HSM name. You only need use the true name of the dataset.

What are you trying to do and why.

jsrueg · New User Joined: 22 Jun 2006 Posts: 6

I'm trying to determine what the MVS DSN is so I can determine if I the DSNAME owner needs to be notified that the dataset is no longer available.
The HSM log generates:
IEC143I 213-2C,IFG0194D,DFSMSHSM,DFSMSHSM,SYS07429,453F,HSMS06,HSMSAV.HMIG.T0400

I'v already determined that the dataset is no longer on the HSM ML1 volume and apparently has been lost. I need to get with the owner of the data to determine impact.

expat · Posted: Mon Apr 30, 2007 10:05 pm

YES, You can do it, but I'm not back in the office until Wednesday, and will try and post some info then if I get the time after catching up from a long weekend.

expat · Posted: Mon Apr 30, 2007 10:24 pm

In the meantime, I suggest that you audit the MCDS.

This may show much more detail of the nature of the error and may also help if the dataset has moved from ML1 to ML2 and the move was active during a failure which did not update the MCDS correctly. Just a shot in dark, but it has happened before.

jsrueg · New User Joined: 22 Jun 2006 Posts: 6

MCDS Audit reports no error. This occurred when I re-sized my MCDS. I'm not sure exactly why it occurred though as no HSM activity occurred during my process. At any rate I just have this one bad DSN and it is set to expire tomorrow. I'd stil like to know if anyone has a method of getting the true MVS DSN from the HSM generated DSN.

TizMe · New User Joined: 05 Jan 2006 Posts: 72

HSEND FIXCDS A HSMSAV.HMIG.Txxxx etc will list the data that you require.

jsrueg · New User Joined: 22 Jun 2006 Posts: 6

Tizme,
Thanks for the assistance, this is EXACTLY what I was looking for. Obviously I never looked in the HSM DIAGNOSIS doc. Thank you very much again!
Jeff