View previous topic :: View next topic
|
Author |
Message |
Praveen Kumar Kolar
New User
Joined: 18 Mar 2021 Posts: 31 Location: India
|
|
|
|
Hi Team,
Recently I have encountered the below error while checking the failed ADRDSSU Dump job.
DUMP DATASET ( INCLUDE (**) , -
EXCLUDE (SYS1.VTOCIX.HSM009 , -
SYS1.VVDS.VHSM009 ) ) -
INDDNAME ( HSM009 ) -
OUTDDNAME ( TAPE ) -
TOL ( ENQF ) -
WAIT ( 0,0 )
ADR049E (001)-STEND(01), 2021.136 00:41:13 DFSMSDSS FUNCTION TASK ABEND RECOVERY ROUTINE WAS ENTERED. SYSTEM ABEND CODE=0837 REASON CODE=0008
ADR324E (001)-DTDS (01), THE VOLUME/DATA SET SPECIFIED BY DDNAME TAPE HAS BECOME UNUSABLE
ADR013I (001)-CLTSK(01), 2021.136 00:41:13 TASK COMPLETED WITH RETURN CODE 0016
The datasets in this volume seems to be uncataloged.
The just found the below information but didn't get the clear idea about it.
www.ibm.com/docs/en/zos/2.2.0?topic=explanations-adr324e
Explanation
A RESTORE, COPY, DUMP or COPYDUMP has not completed successfully, consequently leaving the output volume or data set in questionable condition. For a COPY or RESTORE, the volume serial number defines the device that has become unusable. For a DUMP or COPYDUMP, the DD statement ddname defines the tape or DASD data set that has become unusable. The data set has become unusable because either data set control information was written to the data set and no valid data sets were copied or an error condition left the data set unusable for performing any restores from it. Other messages indicating the cause of the error precede this message.
Please help me to resolve this issue. |
|
Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015 Posts: 1255 Location: Bamberg, Germany
|
|
|
|
First of all, remember to use code tags when presenting code/data!
Second, specify sth. like:
on DD:TAPE and retry the job. |
|
Back to top |
|
|
Praveen Kumar Kolar
New User
Joined: 18 Mar 2021 Posts: 31 Location: India
|
|
|
|
Hi Joerg,
Thank you for educating me. I have tried with volume count 20 and still failed. Later I tried with volume count of 40 and it completed successfully.
Could you please tell me based on which message ID you decided that the failed due to insufficient volume count. |
|
Back to top |
|
|
Willy Jensen
Active Member
Joined: 01 Sep 2015 Posts: 712 Location: Denmark
|
|
|
|
The description of System abend 837 points to message IEC028I, which for reason code 8 says:
The volume whose serial number is ser was not found in the JFCB and no address was found for the JFCBextension in the SWA. Specify more volume serial numbers, or a larger volume count in the VOL parameter ofthe DD statement.
System codes are documented in z/OS Version 2 Release 4 MVS System Codes
Message IEC* are documented in z/OS Version 2 Release 4 MVS System Messages Volume 7 (IEB -IEE) |
|
Back to top |
|
|
Praveen Kumar Kolar
New User
Joined: 18 Mar 2021 Posts: 31 Location: India
|
|
|
|
Hi WJ,
Thank you for the explanation. |
|
Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015 Posts: 1255 Location: Bamberg, Germany
|
|
|
|
Also take note how the VolCount parameter is calculated:
Code: |
VOL=({PRIVATE}{,RETAIN}{,vol seq #}{,vol count}
{,}{SER=volser
or
SER=(volser1,volser2,volser3,...)
or
REF=dsname
or
REF=*.ddname
or
REF=*.stepname.ddname
or
REF=*.stepname.procstepname.ddname)}
vol count
Specifies the maximum number of volumes that an OUTPUT data
set requires. This is a decimal number in the range 1
through 255, inclusive - the total number of output volumes
for a DD statement may not exceed 4,096 volumes, however.
You should code this parameter when an output data set will
require more than 6 volumes. If the volume count is omitted
or 1 through 5 is specified, the maximum allowed is 5
volumes. If 6 through 20 is specified, the maximum allowed
is 20 volumes. If the specified is greater than 20, the
maximum allowed is a multiple of 15 plus 5, up to 255. |
|
|
Back to top |
|
|
Praveen Kumar Kolar
New User
Joined: 18 Mar 2021 Posts: 31 Location: India
|
|
|
|
Hi Joerg,
Thank you for the detailed explanation. |
|
Back to top |
|
|
|