|
View previous topic :: View next topic
|
| Author |
Message |
lemon123
New User
Joined: 12 Feb 2013
Posts: 10
Location: India
|
|
|
|
Hi,
I need to Restore a VSAM dataset from tape without replacing the existing dataset in production..
Thanks in Advance..
Regards,
lemon123 |
|
| Back to top |
|
 |
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| And it was backed up with...? |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
Congratulations and good luck.
Seriously, you didn't define what your problem is, nor did you tell us what utility was used to create the backup, you didn't tell us what you have tried already and what happened when you tried it -- there is nothing we can do to help you at this point.
And have you talked to your site support group? They should be the FIRST point of contact for an issue like this. |
|
| Back to top |
|
|
lemon123
New User
Joined: 12 Feb 2013
Posts: 10
Location: India
|
|
|
|
Hi ,
For PHYSICAL backup i used the pgm -ADRDSSU
This is the jcl i used for restoration
//RESVSAM1 JOB 'DUMP',CLASS=A,NOTIFY=&SYSUID,
// REGION=0M,
//REST1 EXEC PGM=ADRDSSU
//TAPE1 DD UNIT=XXX,VOL=SER=XXXXXX,
// LABEL=(XX,SL),DSNAME=XXXXXXXX.XXXXXX,
// DISP=OLD
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
REST DS(INCLUDE(XXXX.XXX.XXX.XXXXXX)) -
INDD(TAPE1) ODY(XXXXXX) ADMIN RENAMEU(XXXXXXXX)
/*
error: ADR415W (001)-TDDS (01), NO DATA SETS WERE COPIED,
ADR415W (001)-TDDS (02), NO DATA SETS WERE COPIED,
maxx cc 008
Please don't mistake me for my first post
Thanks & Regards,
lemon123 |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| Can you verify from the sysout of the backup job or by other means that the desired data set is in fact on that tape? (The backup was successful, yes?) Are there additional messages showing that the data set failed serialization or authorization? Are you authorized to act as administrator? |
|
| Back to top |
|
|
lemon123
New User
Joined: 12 Feb 2013
Posts: 10
Location: India
|
|
|
|
Hi,
Thank you for your response .....
Yes... the backup was successful.This backup is our daily eod backup we are taking on tape.
DATA SET XXXX.XXX.XXX.XXX IN CATALOG CATALOG.APPL.XXXXX.XXXX ON VOLUME XXXXXX WAS NOT SERIALIZED ON
REQUEST
CLUSTER XXXX.XXX.XXX.XXX IN CATALOG CATALOG.APPL.XXXXX.XXXX ON VOLUME XXXXXX WAS NOT SERIALIZED ON
DOES NOT SUPPORT RENAME OF VSAM DATA SETS
THE FOLLOWING DATA SETS WERE NOT PROCESSED FROM VOLUME XXXXX DUE TO ERRORS
YES ,,am having the Administrator access..
Thanks & Regards,
lemon123 |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
So, then, does this help? From z/OS MVS System Messages, Vol. 1:
| Quote: |
ADR332E(ttt)-mmmmm(yy), CLUSTER cluster_name (IN CATALOG catalog_name) NOT RESTORED. PHYSICAL DATA SET OPERATION DOES NOT SUPPORT RENAME OF VSAM DATA SETS
Explanation:
During a physical data set copy or restore, RENAME, or RENAMEUNCONDITIONAL is specified, and the named VSAM data set met the RENAME filtering criteria. DFSMSdss does not support RENAME processing for VSAM data sets during physical data set copy and restore.
System action:
The data set is not processed, and processing continues with the next data set. The return code is 8.
Operator response:
None.
Application Programmer Response:
Specify RENAME or RENAMEUNCONDITIONAL old name filtering criteria that do not select VSAM data set names, and rerun the job.
Source:
DFSMSdss
|
|
|
| Back to top |
|
|
lemon123
New User
Joined: 12 Feb 2013
Posts: 10
Location: India
|
|
|
|
Hi,
Please correct me if am wrong...
it means .. without renaming the existing dataset ,the restoration is not possible?
also we can't rename the existing dataset though we are in production...
is there any other option to restore..
Thanks in advance
Thanks & Regards,
lemon123 |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
The advantage of doing a logical dump in ADRDSSU is that you can then rename all data sets when you restore them. Physical dumps are more restricted in that VSAM data sets cannot be renamed during a restore operation.
Your best bet is to restore the data set in another LPAR other than production, then rename it in that LPAR -- or restore it and do an ADRDSSU logical dump, then restore from the logical dump using the appropriate rename parameter (hint: RENAMEUNCONDITIONAL is something to look at). |
|
| Back to top |
|
|
lemon123
New User
Joined: 12 Feb 2013
Posts: 10
Location: India
|
|
|
|
Thank you very much for your effort!!!!
I will try in another lpar.. |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 580
Location: London
|
|
|
|
If it's a physical DUMP, then you have to do a physical RESTORE. If it is a VSAM fle it will be restored uncataloged onto the volume you have specified (which may have to be a spare NONSMS volume), and you'll have to do an IDCAMS DEFINE RECATALOG to get it cataloged. If there is already a file of the same name cataloged then you may have to rename that temporarily until you have done your physical restore, define recatalog, and then renamed your restore file to something else. After that you can rename the original one back to its proper name.
PS: Do not use Physical backups. RTFM to understand the difference |
|
| Back to top |
|
|
|
|
