View previous topic :: View next topic
|
Author |
Message |
SVazifdar
New User
Joined: 21 Apr 2006 Posts: 14
|
|
|
|
I have run the following JCL to restore 21 files from the backup. However, I am receiving an error message:
'ADR337E (001)-TDDS (01), THE DUMP DATA SET IS EMPTY
ADR415W (001)-TDDS (02), NO DATA SETS WERE COPIED, DUMPED, OR RESTORED FROM ANY VOLUME
ADR006I (001)-STEND(02), 2007.214 11:36:27 EXECUTION ENDS
ADR013I (001)-CLTSK(01), 2007.214 11:36:28 TASK COMPLETED WITH RETURN CODE 0008'
I have referneced the IBM manual but have been unable to resolve the issue.
Any assitance will be greatly appreciated.
Thanks,
//RESTORE EXEC PGM=ADRDSSU,REGION=0M
//RESTORE DD DSN=QASP.ACCDELXT.BACKUP(+0),
// DISP=SHR
//SYSIN DD *
RESTORE -
INDDNAME(RESTORE) -
DATASET(INCL(**)) -
RENUNC(QAST) -
SPHERE -
FREESPACE(0,0) -
PCTU(100) -
REPLACE -
CATALOG
/*
//SYSOUT DD SYSOUT=* |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
What are you trying to rename ??? |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Is there some reason you posted the same question twice - in separate forums? That is not acceptable here. . . . It just adds clutter and confusion.
I'll delete the "other" post. Following is my reply from that topic.
Quote: |
Hello,
If the posted messages are from the intended file, there was no backup created. Changing your jcl/control statements cannot get around an empty dump dataset.
Can you find the output of the execution of the job that created the backup? Can you find the jcl of the job that created the backup?
If you can find the original backup jcl, i'd suggest you change the name of the output dataset and run the job. Look at the sysout info to see what file(s) were backed up, if any. If the files backed up are not the ones intended, fix the job for subsequent backups.
For you, this is a bit late, but a backup created and not test-restored successfully, is not a backup - it is merely a dataset of questionable content. |
|
|
Back to top |
|
|
Douglas Wilder
Active User
Joined: 28 Nov 2006 Posts: 305 Location: Deerfield IL
|
|
|
|
I got this error when I tried to restore datasets (for disaster recovery testing) using relative generation numbers for GDGs. I had to use the absolute generation number instead. I think this may be your problem.
Note: When I did get them restored they were not part of the GDG. By that I mean that relative generation number would not work. I had to gener them to a +1 and then it worked. |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
Douglas,
GDG's can be a bit funny when restoring them, especially as the default status of the GDG is DEFERRED. This is why you had to copy them to get them usable by RGN.
Using the following parameter will resolve that problem
TGTGDS(ACTIVE)
As for the OP ..........
Follow Dicks advice, check out the dump job very carefully |
|
Back to top |
|
|
Douglas Wilder
Active User
Joined: 28 Nov 2006 Posts: 305 Location: Deerfield IL
|
|
|
|
Expat,
Thank You!!! Our disaster recovery test run much smother and quicker now that we used ADRDSSU TGTGDS(ACTIVE) in restoring our GDGs. Thank You! Thank You! Thank You! |
|
Back to top |
|
|
|