Show Posts
286
z/OS Server / Re: Loads Failing
« on: March 21, 2020, 04:00:44 PM »
I shamelessly stole this writeup from a colleague on the OAM reason code:
PROBLEM DESCRIPTION:
ARS0020E NDCTALF SM Error: ARSMVSRE:
0000000b(0000000c-6c030910)
The 0000000B indicates that on an attempt to retrieve the document in
question, OAM is returning an error as indicated by the return and
reason codes (0000000C-6C030910).
The meaning of those return and reason code can be found in Chapter 12
OAM Diagnostic Aids, of the DFPSMSdfp Diagnosis guide located in the
z/OS 1.10 Library Center at the following url(this is the older one,
the 1.12 one is not accessible):
http://publibz.boulder.ibm.com/bookmgr_OS390/libraryserver/zosv1r10/
And summarized here:
Section 12.2 OSREQ Return and Reason Codes
Table 89. OSREQ Return and Reason Codes
........................................................................
Return Reason Code Description
Code (Bytes)
0 1 2 3
.......................................................................
12 (X'0C') X'6C' x y z OAM address space detected failure.
yz LCS reason code. See
"OAM Macro Return and Reason Codes"
in topic 12.4 and look for the
associated OAM macro reason code.
The rreturn code 12 is an OSREQ
return code, and may not match the
return code for the OAM macro.
........................................................................
Section 12.4 OAM Macro Return and Reason Codes
Table 93. OAM Macro Reason Codes
........................................................................
Return Reason
Code Error Code Code Description
........................................................................
X'0C' Hardware X'0910' Specific request for unreadable volume.
resource
unavailable
To confirm that the failure can be isolated to what is occurring in OAM,
please issue the following requests in TSO:
TSO OSREQ QUERY <collection name> <object name>
TSO OSREQ RETRIEVE <collection name> <object name>
The collection and object names to specify in the above commands can be
found in the ARS0020E message itself. For example, the following
complete ARS0020E message was issued for another customer's similar
issue:
ARS0020E O09402 SM ERROR: ARSMVSRE: 0000000B(0000000C-6C030910)
IODC.R90D0442.SGROUP10.OD10YEAR(JQA.L53.FAAA), RC=11, REASON=0, FILE
=ARSSMSMS.CPP, LINE=917 SRVR->MY.SRVR.FOO n.n.n.n<-
In that case, IODC.R90D0442.SGROUP10.OD10YEAR was the collection name
and JQA.L53.FAAA was the object name.
I also anticipate that the OSREQ RETRIEVE request will fail with the
same return and reason codes as when the retrieve request is issued
through OnDemand.
This may actually be the result of just one unreadable tape rather than
the backup tapes/volume not being available in general. Here is what the
OAM support team recommended it further diagnose the failure in the
other customer's case:
........................................................................
You can issue the D SMS,VOL(volser) command to check for the volume
status or do a SPUFI on the volume to see if it has been set to readable
= NO. In any case, OAM provides an UPDATE VOLUME command that should be
used to update the VOLUME or TAPEVOL DB2 Tables. Here is an example of
the OAM Update volume command:
F OAM, UPDATE,VOL,volser,READABLE,Y
.
This command can be used to change other setting such as writable,
etc. Please review the OAM PISA for Object support on more information
about the OAM update volume command.
........................................................................
In that case, the customer was able to set the volume to readable, but
found that they actually needed to do a complete volume recovery on the
primary tape volume. When attempting to recover the tape, they further
found that some of the backup tapes were also bad and not readable.
They cleared the errors on the backup tapes and were then able to
restart the volume recovery on the primary volume.
In your case, please issue the indicated OSREQ and D SMS commands and
report the results. If it is the anticipated backup volume that is
triggering the failure, try the F OAM command to set the volume to
readable. If that does not work, the volume may need a
complete recovery.
If you still need help you need to talk to OAM support.
Ed
PROBLEM DESCRIPTION:
ARS0020E NDCTALF SM Error: ARSMVSRE:
0000000b(0000000c-6c030910)
The 0000000B indicates that on an attempt to retrieve the document in
question, OAM is returning an error as indicated by the return and
reason codes (0000000C-6C030910).
The meaning of those return and reason code can be found in Chapter 12
OAM Diagnostic Aids, of the DFPSMSdfp Diagnosis guide located in the
z/OS 1.10 Library Center at the following url(this is the older one,
the 1.12 one is not accessible):
http://publibz.boulder.ibm.com/bookmgr_OS390/libraryserver/zosv1r10/
And summarized here:
Section 12.2 OSREQ Return and Reason Codes
Table 89. OSREQ Return and Reason Codes
........................................................................
Return Reason Code Description
Code (Bytes)
0 1 2 3
.......................................................................
12 (X'0C') X'6C' x y z OAM address space detected failure.
yz LCS reason code. See
"OAM Macro Return and Reason Codes"
in topic 12.4 and look for the
associated OAM macro reason code.
The rreturn code 12 is an OSREQ
return code, and may not match the
return code for the OAM macro.
........................................................................
Section 12.4 OAM Macro Return and Reason Codes
Table 93. OAM Macro Reason Codes
........................................................................
Return Reason
Code Error Code Code Description
........................................................................
X'0C' Hardware X'0910' Specific request for unreadable volume.
resource
unavailable
To confirm that the failure can be isolated to what is occurring in OAM,
please issue the following requests in TSO:
TSO OSREQ QUERY <collection name> <object name>
TSO OSREQ RETRIEVE <collection name> <object name>
The collection and object names to specify in the above commands can be
found in the ARS0020E message itself. For example, the following
complete ARS0020E message was issued for another customer's similar
issue:
ARS0020E O09402 SM ERROR: ARSMVSRE: 0000000B(0000000C-6C030910)
IODC.R90D0442.SGROUP10.OD10YEAR(JQA.L53.FAAA), RC=11, REASON=0, FILE
=ARSSMSMS.CPP, LINE=917 SRVR->MY.SRVR.FOO n.n.n.n<-
In that case, IODC.R90D0442.SGROUP10.OD10YEAR was the collection name
and JQA.L53.FAAA was the object name.
I also anticipate that the OSREQ RETRIEVE request will fail with the
same return and reason codes as when the retrieve request is issued
through OnDemand.
This may actually be the result of just one unreadable tape rather than
the backup tapes/volume not being available in general. Here is what the
OAM support team recommended it further diagnose the failure in the
other customer's case:
........................................................................
You can issue the D SMS,VOL(volser) command to check for the volume
status or do a SPUFI on the volume to see if it has been set to readable
= NO. In any case, OAM provides an UPDATE VOLUME command that should be
used to update the VOLUME or TAPEVOL DB2 Tables. Here is an example of
the OAM Update volume command:
F OAM, UPDATE,VOL,volser,READABLE,Y
.
This command can be used to change other setting such as writable,
etc. Please review the OAM PISA for Object support on more information
about the OAM update volume command.
........................................................................
In that case, the customer was able to set the volume to readable, but
found that they actually needed to do a complete volume recovery on the
primary tape volume. When attempting to recover the tape, they further
found that some of the backup tapes were also bad and not readable.
They cleared the errors on the backup tapes and were then able to
restart the volume recovery on the primary volume.
In your case, please issue the indicated OSREQ and D SMS commands and
report the results. If it is the anticipated backup volume that is
triggering the failure, try the F OAM command to set the volume to
readable. If that does not work, the volume may need a
complete recovery.
If you still need help you need to talk to OAM support.
Ed