Joined: 06 Jun 2008 Posts: 8697 Location: Dubuque, Iowa, USA
Quote:
Can someone please advise? There is sufficient space on output volume TSON03 and reason code 4 does not lead me to self-diagnose it any further.
You may believe that there is sufficient space, but the system is telling you otherwise -- that is what the return code 04 means. Either the system is attempting to restore to a volume other than the one you have specified, or the volume does not have enough free space to put the data set on it. As long as you continue to believe what you want, instead of what the system is telling you, there is no way we can help you.
I am not denying this error and resorting to self-belief
However what you said is right - the system is attempting to restore to a different volume and not TSON03 that has been specified - can you help me understand how can I still override this?
Thanks for your suggestions!
IGD103I SMS ALLOCATED TO DDNAME INPUT
IEF237I 2016 ALLOCATED TO OUTPUT
IEF237I JES2 ALLOCATED TO SYSPRINT
IEF237I JES2 ALLOCATED TO SYSIN
Joined: 06 Jun 2008 Posts: 8697 Location: Dubuque, Iowa, USA
Your original post and your title are in conflict -- is volume TSON03 managed by SMS or not? If not, then you probably need NULLSTORCLASS as one of your restore options since it appears that the source was SMS-managed.
Yes, it is non-SMS managed. Sorry about the the title mismatch.
D SMS,VOL(TSON03)
CBR1910I DISPLAY rejected. OAM address space not started.
IGD005I COMMAND REJECTED 923
VOLUME TSON03 IS NOT AN SMS MANAGED DASD VOLUME
The source (SAJNA02.DE03.DUMP) is on SMS managed volume.
1PAGE 0001 5695-DF175 DFSMSDSS V2R01.0 DATA SET SERVICES 2013.244 10:20
- RESTORE -
DATASET(INCLUDE(**) -
) -
INDDNAME(INPUT) -
OUTDDNAME(OUTPUT) -
RENAMEUNCONDITIONAL( -
(SAJNA02.DE03.V251.CETJXML,SAJNA02.DE03.V251.CETJXML.RSTR)-
) -
WRITECHECK -
CANCELERROR -
WAIT(2,2)
ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'RESTORE '
ADR109I (R/I)-RI01 (01), 2013.244 10:20:20 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED
ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK
0ADR006I (001)-STEND(01), 2013.244 10:20:20 EXECUTION BEGINS
0ADR916W (001)-OPNCL(01), FOR VOLUME TSON03 THE DEVICE SIZE IN THE VTOC, 000032760, IS LARGER THAN THE DEVICE SIZE FROM RDC,
000010017. THE DEVICE SIZE FROM RDC WILL BE USED
0ADR780I (001)-TDDS (01), THE INPUT DUMP DATA SET BEING PROCESSED IS IN LOGICAL DATA SET FORMAT AND WAS CREATED BY Z/OS DFSMSDSS
VERSION 2 RELEASE 1 MODIFICATION LEVEL 0 ON 2013.244 10:18:54
0ADR472E (001)-NEWDS(06), UNABLE TO SELECT A TARGET VOLUME FOR DATA SET SAJNA02.DE03.V251.CETJXML, 04
0ADR415W (001)-TDLOG(01), NO DATA SETS WERE COPIED, DUMPED, OR RESTORED FROM ANY VOLUME
0ADR480W (001)-TDLOG(01), THE FOLLOWING DATA SETS WERE NOT PROCESSED FROM THE LOGICALLY FORMATTED DUMP TAPE DUE TO ERRORS:
0 SAJNA02.DE03.V251.CETJXML
0ADR006I (001)-STEND(02), 2013.244 10:20:20 EXECUTION ENDS
0ADR013I (001)-CLTSK(01), 2013.244 10:20:20 TASK COMPLETED WITH RETURN CODE 0008
0ADR012I (SCH)-DSSU (01), 2013.244 10:20:20 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS 0008 FROM:
TASK 001
Joined: 06 Jun 2008 Posts: 8697 Location: Dubuque, Iowa, USA
The last output you posted and the original post output have the same date and time stamp. Hence, either you ran a job with NULLSTORCLAS but did not post that job's output, or you did NOT run a job with NULLSTORCLAS but want us to think you did. At best, you show incompetence in posting and at worst you may be lying to us.
I am not sure there is any reason for us to continue to try to help you since you are not paying attention to the messages the system gives you, your posts are contradictory and misleading at best, and the indications are your competence level could keep you from implementing our suggestions, any way.
It's not about competence or intent - everyone sometimes have a rough day and am going through that .
Nevertheless, I had the SYSPRINT xdc'ed into a member but realized that I did not download it correctly and instead provided the earlier one only. Apologies for the same. Here is the updated SYSPRINT that I intended to send earlier.
1PAGE 0001 5695-DF175 DFSMSDSS V2R01.0 DATA SET SERVICES 2013.244 13:00
- RESTORE -
DATASET(INCLUDE(**) -
) -
INDDNAME(INPUT) -
OUTDDNAME(OUTPUT) -
RENAMEUNCONDITIONAL( -
(*******.DE03.V251.CETJXML,*******.DE03.V251.CETJXML.RSTR)-
) -
WRITECHECK -
CANCELERROR -
NULLSTORCLAS -
WAIT(2,2)
ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'RESTORE '
ADR109I (R/I)-RI01 (01), 2013.244 13:00:03 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED
ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK
0ADR006I (001)-STEND(01), 2013.244 13:00:03 EXECUTION BEGINS
0ADR916W (001)-OPNCL(01), FOR VOLUME TSON03 THE DEVICE SIZE IN THE VTOC, 000032760, IS LARGER THAN THE DEVICE SIZE FROM RDC,
000010017. THE DEVICE SIZE FROM RDC WILL BE USED
0ADR780I (001)-TDDS (01), THE INPUT DUMP DATA SET BEING PROCESSED IS IN LOGICAL DATA SET FORMAT AND WAS CREATED BY Z/OS DFSMSDSS
VERSION 2 RELEASE 1 MODIFICATION LEVEL 0 ON 2013.244 10:18:54
0ADR472E (001)-NEWDS(06), UNABLE TO SELECT A TARGET VOLUME FOR DATA SET *******.DE03.V251.CETJXML, 04
0ADR415W (001)-TDLOG(01), NO DATA SETS WERE COPIED, DUMPED, OR RESTORED FROM ANY VOLUME
0ADR480W (001)-TDLOG(01), THE FOLLOWING DATA SETS WERE NOT PROCESSED FROM THE LOGICALLY FORMATTED DUMP TAPE DUE TO ERRORS:
0 SAJNA02.DE03.V251.CETJXML
0ADR006I (001)-STEND(02), 2013.244 13:00:03 EXECUTION ENDS
0ADR013I (001)-CLTSK(01), 2013.244 13:00:03 TASK COMPLETED WITH RETURN CODE 0008
0ADR012I (SCH)-DSSU (01), 2013.244 13:00:03 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS 0008 FROM:
TASK 001
Today, I tried using a different volume for OUTPUT DD (TSOA03 instead of TSON03) and it worked using with the NOSTORCLAS keyword for this non-SMS managed volume. Thanks for the suggestion.
I looked at the VTOC for TSON03 and it had sufficient free cylinders to restore the above dataset however it was failing - so now looking into this. Anyways thanks for the advice.
Data Set Information
Command ===>
More: +
Data Set Name . . . : ****.DE03.V251.CETJXML
General Data Current Allocation
Management class . . : STANDARD Allocated tracks . : 2
Storage class . . . : DEMO Allocated extents . : 1
Volume serial . . . : TSOH03 Maximum dir. blocks : NOLIMIT
Device type . . . . : 3390
Data class . . . . . : DEFAULT
Organization . . . : PO Current Utilization
Record format . . . : VB Used pages . . . . : 24
Record length . . . : 512 % Utilized . . . . : 100
Block size . . . . : 6233 Number of members . : 6
1st extent tracks . : 2
Secondary tracks . : 2
Data set name type : LIBRARY Dates
Data set version . : 1 Creation date . . . : 2013/09/01
Referenced date . . : 2013/09/02
Expiration date . . : ***None***
Have a look at TSON03 from ISMF option 2.1 and see if SMS status is 'CONVERT'. The volume may have been initialised in SMS format but has not been defined to SMS, in which case you won't be able to allocate anything on it.
That display only shows you if the volume is defined in the SMS SCDS or active configuration or not.
Just because it's not in the active configuration doesn't mean that it isn't 'initialised' (via ICKDSF) in SMS format, but not defined in the SMS SCDS. In that case you can't allocate on the volume. Look at the volume in ISMF;2.1 and see if it shows CONVERT status.
It indicates that LIST HAS NO ENTRIES when specifying VOLSER as TSON03 - so could it be that it isn't initialized in the SMS format. I shall check ICKDSF documentation to see how volumes can be defined, otherwise.
Panel Defaults Utilities Scroll Help
------------------------------------------------------------------------------
VOLUME SELECTION ENTRY PANEL LIST HAS NO ENTRIES
Command ===>
Select Source to Generate Volume List . . 2 (1 - Saved list, 2 - New list)
1 Generate from a Saved List Query Name To
List Name . . Save or Retrieve
2 Generate a New List from Criteria Below
Specify Source of the New List . . 1 (1 - Physical, 2 - SMS)
Optionally Specify One or More:
Enter "/" to select option Generate Exclusive list
Type of Volume List . . . 1 (1-Online,2-Not Online,3-Either)
Volume Serial Number . . TSON03 (fully or partially specified)
Device Type . . . . . . . (fully or partially specified)
Device Number . . . . . . (fully specified)
To Device Number . . . (for range of devices)
Acquire Physical Data . . Y (Y or N)
Acquire Space Data . . . Y (Y or N)
Storage Group Name . . . * (fully or partially specified)
CDS Name . . . . . . . 'ACTIVE'
(fully specified or 'Active')
Select Source to Generate Volume List . . 2 (1 - Saved list, 2 - New list)
1 Generate from a Saved List Query Name To
List Name . . Save or Retrieve
2 Generate a New List from Criteria Below
Specify Source of the New List . . 1 (1 - Physical, 2 - SMS)
Optionally Specify One or More:
Enter "/" to select option Generate Exclusive list
Type of Volume List . . . 1 (1-Online,2-Not Online,3-Either)
Volume Serial Number . . TSON03 (fully or partially specified)
Device Type . . . . . . . (fully or partially specified)
Device Number . . . . . . (fully specified)
To Device Number . . . (for range of devices)
Acquire Physical Data . . Y (Y or N)
Acquire Space Data . . . Y (Y or N)
Storage Group Name . . . (fully or partially specified)
CDS Name . . . . . . .
.
