There is no output from the job.
The Joblog as below:
ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'RESTORE '
ADR109I (R/I)-RI01 (01), 2008.357 13:40:17 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED.
ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK
ADR006I (001)-STEND(01), 2008.357 13:40:17 EXECUTION BEGINS
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), 2008.357 13:41:09 EXECUTION ENDS
ADR013I (001)-CLTSK(01), 2008.357 13:41:09 TASK COMPLETED WITH RETURN CODE 0008
ADR012I (SCH)-DSSU (01), 2008.357 13:41:09 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS 0008 FROM: TASK 001
did You care to look at the manual to understand the meaning of the
messages You received...
looks like not
the message is clear,
ADR337E (ttt)-mmmmm(yy), THE DUMP DATA SET IS EMPTY
Explanation: An attempt has been made to restore from an empty dump data set.
System Action: The return code is 8.
Operator Response: None.
Application Programmer Response: Rerun the job with a good dump data set.
follow the manual' s advice
Rerun the job with a good dump data set.
Joined: 28 Nov 2006 Posts: 305 Location: Deerfield IL
This is the message you get when the dataset to be restored is not in the backup dataset specified. Is the file name to be restored 'CI27015M.EXTRACT'? Only 2 nodes long? Could you show us the control card used in the backup? If the messages listed above are from the backup, it looks like nothing was backed up. Did you try dumping some of the records from the tape to see if the dataset is actually on the tape?
This will surely catalog a new generation, but does not guarantee that the file you want is on the backup. Look at the output of the execution that created the generation you are trying to use and see if the file was copied to the backup.
You might also run the backup again and ensure the file you want is copied.
An unverified backup is only that - unverified. It is at best a file of questionable content (until it is used and verified - one of the first things that should happen with a newly created backup process is verification that not only did it run to successful eoj, but that it copied everything that it should.
for dfdss dumps the best practice to avoid later troubles is to run a jib with two steps
step 1 - dump
step 2 - restore with the parameter
For copy, dump, restore, compress, and release operations, only input data set selection is done without actually processing data sets. Printed output for the run indicates the data sets selected. For a defragmentation operation, the initial volume statistics are printed without actually relocating any extents. For a CONVERTV operation, a full report is produced, but no volumes or data sets are actually converted. For CGCREATE operation, only control card syntax checking is done. The task is not processed.
it could be worth to automate the checking by writing the dfdss sysouts to two datasets
and run something to compare for mismatches
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
Please review your jcl and control statements. They are completely out of sync. . . If that is the job that was submitted previously to create the backup, none was created.
After you correct the jobstream, run it again. If there are questions or probems, please post the same info as you posted this time using copy/paste and the "Code" tag rather than uploading attahments. Many people are not permitted to download atachments due to security restrictions on their systems.
This step makes absolutely no sense.
1) Why have DDNAME TAPE1 if you're going to do the backup by DATASET?
2) If you decide to do a RESTORE immediately after the DUMP, you need some way to check the DUMP code to ensure it actually worked before doing the restore.
3) You are attempting to RESTORE a dataset name you did not back up. This cannot be done. If you wish to restore ZCLICDU.VALID.TAPE into a new dataset name, you have to restore ZCLICDU.VALID.TAPE and use the RENAMEUNCONDITIONAL option of the restore.
4) If you're going to do a restore, you absolutely cannot use the same name for the DF/DSS backup file as the restored file -- you're not ever going to be able to do that.
Perhaps if you attempt to describe just what it is you're attempting to accomplish with this hodgepodge, we could suggest ways to do it that will actually have a chance of working.
With your help, now, I can dump a DASD file to a TAPE and can resore it successfully, but if I have a TAPE file that processed by a PGM, how should i do can view and edit it? If I don't use IEBGENER, then how should I do can copy it to DASD?
I'm looking forward to your replay.
Thanks in advance.