Sorry gang. I got pulled away on other fires and forgot to update what
happened.
As somnone had suggested, I went to the HSM Storage Administration Guide,
Chapter 5.1.9 - Case 9. Reestablish Access to Previously Deleted Mugrated
Data Sets (No Backup Exists, ML2 Only) at
I think you use RECOVER rather than RECALL when it is not cataloged.
Lizette
Hello everyone. I have some datasets on ML2 that have long since been
uncataloged that I need to recall. I've loked for ways to either recatalog
then recall them or recall and recatalog them, but no luckthere yet.
If you tried to recat them to MIGRAT2 and they don't recall, then you'll
need to check the MCDS to see if HSM knows about them- probably not. If
you know the tape that they were migrated to and it hasn't been recycled
you could build a MCDS entry but you'll have to want this data very badly.
On Wed, 3 Jun 2009 11:12:12 -0500, Howard Whitehead
hwhiteh...@statesman.com wrote:
Hello everyone. I have some datasets on ML2 that have long since been
uncataloged that I need to recall. I've loked for ways to either recatalog
then recall them or recall and recatalog them, but no luckthere
I didn't know you COULD recat to MIGRAT2. Could I trouble you for some
sample code for that to save me some time?
I tried the RECOVER command but I got an ARC1128 BACKUP/DUMP COPY DOES NOT
EXIST.
Thanks all.
--
For IBM-MAIN
If you tried to recat them to MIGRAT2 and they don't recall, then you'll
need to check the MCDS to see if HSM knows about them- probably not. If
you know the tape that they were migrated to and it hasn't been recycled
you could build a MCDS entry but you'll have to want this data very
badly.
The onl copy I have is the tape ML2. As far as I can tell, my MCDS data is
good, it's just that the data set has been uncataloged for a very long time
so HSM on't allow the recall. I'm trying to research recating to MIGRAT2
but so far I'm strikin' out.
Thanks,
Howard
Howard,
I am not sure how you would catalog a volser of MIGRAT2 which is 7 chars. The
VSAM Define seems to only allow for 6 chars.
Maybe somebody on the list can figure this out.
Lizette
The onl copy I have is the tape ML2. As far as I can tell, my MCDS data is
good, it's just that the
See my previous post: MIGRAT/MIGRAT2 is a display convention. Catalog to
volser MIGRAT. HSM will figure it out.
DEF NVSAM(NAME('original.dsn') DEVT(3390) VOL(MIGRAT))
Then issue hrecall
snip
The onl copy I have is the tape ML2. As far as I can tell, my MCDS
data is
good, it's just that the
I am not sure how you would catalog a volser of MIGRAT2 which is 7 chars.
The VSAM Define seems to only allow for 6 chars.
That's because the OS only allows 6 chars for a volser (tape or disk).
Maybe somebody on the list can figure this out.
It's not a VSAM restriction, unless you call an OS
Mainframe Discussion List
[mailto:ibm-m...@bama.ua.edu] On Behalf Of Howard Whitehead
Sent: Wednesday, June 03, 2009 12:23 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: HSM: Recall uncataloged data set
The onl copy I have is the tape ML2. As far as I can tell,
my MCDS data is
good, it's just
Thanks for the info. I had missed it before. I also found something in the
HSM Stg Admin Guide 5.1.9 Case 9...reestablish access to Previously Deleted
Migrated Data Sets (No Backup Exists, ML2 Only). You nd this may have me on
the right track. I'll update with what happens.
Thanks all!
Howard
snip
I am not sure how you would catalog a volser of MIGRAT2 which is 7 chars
unsnip
That was my fault. You only catalog the migrat, I put the migrat2 to
indicate it was ml2 BUT it's only a display.
Howard seems sure that the file exists on ML2 and I really hope that he
knows that for sure
[mailto:ibm-m...@bama.ua.edu] On
Behalf Of Staller, Allan
Sent: Wednesday, June 03, 2009 10:33 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: HSM: Recall uncataloged data set
See my previous post: MIGRAT/MIGRAT2 is a display convention. Catalog to
volser MIGRAT. HSM will figure it out.
DEF NVSAM(NAME
AFAIK either will work.
snip
For MIGRAT2, wouldn't you specify DEVT() having as the device
type used for HSM ML2 media rather than specifying 3390?
/snip
--
For IBM-MAIN subscribe / signoff / archive access
MIGRAT2 is code speak for catalogued to volser MIGRAT on a TAPE unit as
opposed to a DASD unit.
Unfortunately, as you saw from the responses, not all of us speak the same
code.
A more specific response may have been more helpful (I mean that in the nicest
possible way).
(8-{]}
-
Too busy
, June 03, 2009 11:29 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: HSM: Recall uncataloged data set
MIGRAT2 is code speak for catalogued to volser MIGRAT on a TAPE unit
as opposed to a DASD unit.
Unfortunately, as you saw from the responses, not all of us speak the
same code.
A more specific response
It is true that MIGRAT2 can also be on as DASD device.
Yes, but.
MIGRAT2, by itself, is meaningless since volsers can only be 6 bytes long.
A detailed description would have helped.
PS: The first shop that I worked with HSM in had ML1 ML2 both on disk.
And, that was back when DISK was
18 matches
Mail list logo
