Terry -
Again im not a storage expert but here is my understanding and I
dont think I am explaining this correctly. Its my understanding its the
dump/restore of migrated dsns is where HSM cant rename VSAM dsns. Im told
this is because HSM doent store the components only the cluster name. The
datasets are migrated/restored using import/export, so import/export knows
about the components, not hsm for hsm to rename components, it needs to
know the details or im told doesn't have access to it nor stores it. This
is where the problem lies. How do you get around this?
I was told by the store people in site that dump/restore of DASD
datasets uses adrdssu so then we can rename the VSAM dsns but not migrated
ones.
I hope this makes the problem we have clearer...
Andy S White
Internet: Mailto:[EMAIL PROTECTED]
Terry -=
Would that include VSAM datasets and components? Thanks
Andy S White
Internet: Mailto:[EMAIL PROTECTED]
Andy,
You can recover and rename datasets directly from the ABARS backup
dataset. I would refer you to the HSM Implementation and Customization
Guide and the DSS Storage Administration Reference.
//**********************************************************************
//* RESTORE FILE(S) FROM ABACKUP DATA FILE
//* SEE INDIVIDUAL DATA SET RESTORE WITH ABARS DFSMSDSS DATA FILE IN
//* THE DFSMSHSM IMPLEMENTATION AND CUSTOMIZATION GUIDE UNDER THE
//* SPECIAL CONSIDERATIONS CHAPTER
//**********************************************************************
//JS010 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//TAPE1 DD DISP=OLD,DSN=HSM.APPL01.D.C01V0052,
/
I Wanted to add to this question what is really the problem for us. When
you do a ABARS recover from HSM data its my understanding IBM doesn't
give the user the option to rename a VSAM dataset. Does anyone have a
way or have gotten around this? We really didnt want to define all the
alias's from the system this is all coming from.
Original question:
We were wondering if anyone has had the same problem as us. We have done
a merger with a company but now have a system with a lot of HSM migrated
tapes which contains all type of data e,.g. VSAM, PDSE etc. We were
going to create ABAR backups but im told by the storage people that it
wont handle VSAM correctly if we bring it back to our shop and try to
restore it and use it. This would only be restored if we needed it for
legal reasons. Has anyone else had this problem? And how did they solve
it?
We thought about recalling the data to dasd then using something like
ADRDSSU or FDR and just back up the backs and do a dcollect so we may
get to it some day if needed. The problem is its about 5TB of HSM data
and they only have 2 TB of dasd etc Again was wondering if there was an
easier solution? If you want to share your thoughts offline id
appreciate it.
Thanks
Andy S White
Internet: Mailto:[EMAIL PROTECTED]
The information contained in this message may be CONFIDENTIAL and is for the
intended addressee only. Any unauthorized use, dissemination of the
information, or copying of this message is prohibited. If you are not the
intended addressee, please notify the sender immediately and delete this
message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
