II07284: OAM RETURN AND REASON CODES - CONTINUATION OF II05257 STARTING WITH RSN7CXXXXXX 566528481 AND 5695DF180

APAR status

• Closed as canceled.

Error description

• This APAR is to record additional information concerning
  OAM (COMPID 566528481 5695DF180 ) return and reason codes.
   This information has been gathered from problems encountered
   by customers.  This APAR is a continuation of II05257.
   -
   The OAM return an reason codes are reported in IODM message
   EKC0703E and EKC0703A as XRCnn and XRSNnnnnnnnn.
   -
  NOTE:  In all cases "PISA' refers to the OAM Planning,
         Installation and Storage Administration Guide, manual
         number SC35-0120 (DFP 3.x) or SC26-4918 (DFSMS 1.1.0).
   ************************************************************
   RC20   RSN02   XRC12   XRSN7C0CFC78     7C0CFC78  RSN7C0CFC78
   OSR attempted a DB2 operation.  The operation failed with
   an SQL error -904 (FC78) indicating a resource is unavailable.
   This error usually occurs when the data base table or index
   is out of space. This can also occur if one or more of the
   of the DB2 tables used by OAM are in DB2 utility mode.
  ************************************************************
  RC20   RSN02   XRC12   XRSN9402FCCE     9402FCCE  RSN9402FCCE
  OTIS address space detected error while attempting to add
  a new collection to the collection table.  The FCCE is the
  DB2 SQL error.  Converted to decimal, it is -818 which
  indicates a problem with the bind.  Rerun CBRHBIND.  If
  problem persists, verify JCL points to correct libraries.
   ***************************************************************
   RC20   RSN02   XRC12   XRSNA00203E9    A00203E9  RSNA00203E9
   OAM executed the SMS ACS routines, and during an ACS routine
   a non-zero exit code was set.  In DFP331 we have also
   seen a case where failure to run CBRHBIND and CBRHGRNT has
   cause OTIS to fail the connection to DB2, and OAM returns
   external reason code XRSNA00203E9 to IODM.  This only
   occurs on the first store to a new collection.
  ***************************************************************
  RC20   RSN02   XRC12   XRSNA0020400     A0020400  RSNA0020400
  XRSNA0020400 Bytes indicate the following:
      A0       Indicates an SMS error during SMS review.
        02     Indicates the error occurred during an
               OSREQ "STORE" attempt.
          0400 is the SMS reason code in hexadecimal.
               This value must be converted to decimal.
               X'0400' is 1024 decimal.  An SMS reason
               code of 1024 indicates the storage group
               routine assigned an object to a storage
               group which is not of type OBJECT or
               OBJECT BACKUP.
  Use the ISMF ACS routine test panel to verify that
  your object is assigned to a storage group of
  type OBJECT or OBJECT BACKUP.
  This error code will also be returned if the &ACSENVIR
  is "STOR" instead of "STORE".
  ************************************************************
  RCnn   RSNnn   XRC12   XRSNA402FCD5    A402FCD5  RSNA402FCD5
  The FCD5 converts to a SQL error code of -811.  This
  reason code may be seen when duplicate names are manually
  entered into the OAMADMIN management class and storage
  class tables.  The condition is corrected by removing the
  duplicate entry.
  ************************************************************
  RCnn   RSNnn   XRC12   XRSNA0021389    A0021389  RSNA0021389
  The last 2 bytes must be convert from hex to decimal.  This
  gives you the SMS reason code 5001.  Search on RSN5001 for
  any known problems.  UY99676 and UY99358 are PTF's that
  compensate for differences in parameter list size between
  DFP releases.
  ************************************************************
  RCnn   RSNnn   XRC12   XRSNA402FCDB    A402FCDB  RSNA402FCDB
  See APAR OY56983.
  ************************************************************
  RC20   RSNnn   XRC12   XRSNA8020800    A8020800  RSNA8020800
  Storage group is not connected to SMS.  The status field on
  the ISMF storage group definition panel must be set to
  ENABLE.  If it is not, the object will not be stored.
  A storage group may only be enabled on 1 system.
  *******************************************************
  RC20   RSNnn   XRC12   XRSNB4020300     B4020300  RSNB4020300
  This error occurs when a store is done to a collection that
  has a collection name that was defined using VSAM DEFINE
  COLLECTION. This catalog entry is not complete and OAM attempts
  to get information from the DB2 Collection Name table. If no
  collection exists in this table the above reason code is
  returned. If this is a new collection the problem can be
  corrected by deleting the catalog entry and then do an OSREQ
  STORE to the new collection. OAM automatically creates the
  catalog and collection table entries.
  **************************************************************
  RC20   RSNnn   XRC16   XRSNCA020D00    CA020D00  RSNCA020D00
  An ABEND has occurred.
  -
  Received when the first store is attempted to a new collection.
  You may experience an ABEND0C4 at +7BE in CBRIPCQE.  See APAR
  OY47974.
  -
  You may see this XRC and XRSN in MSGENT2267I.
   "OAM STORAGE MESSAGE FOLLOWS:
     00000001   00000016  CA020D00"
  ******************************************************
   RC20   RSNnn   XRC16   XRSNCC000100   CC000100  RSNCC000100
  This error indicates an invalid data base name was
  requested.  This occurs because the storage group name
  is not associated with qualifer of GROUP00-GROUP99.
  Correct the storage group definition and reactivate the
  configuration.
  **********************************************************
   RC20   RSNnn   XRC16   XRSND402FC66    D402FC66  RSND402FC66
   RC20   RSNnn   XRC16   XRSND404FC66    D404FC66  RSND404FC66
  A DB2 SQL error code of -922 was recieved indicating the
  CAF connection to DB2 was not authorized.  Use a
  DSNTRACE or AUX trace to find the DB2 reason code.  For an
  AUX trace, see the entry for 7418FCCE.  The plan name will
  appear in the resource field.
    If the reason code is 00F30034, the program attempting to
  execute the plan is not authorized to use the plan.  GRANT
  authority to the auth id specified in the RCT entry for
  CBRIDBS.
  ******************************************************
   RC20   RSNnn   XRC16   XRSNCC010600    CC010600  RSNCC010600
  This reason code may indicate that an ABEND has occured
  or a cancel has been issued for the address space that
  issues OSREQ.  See II06288 for one example.
  *******************************************************
   RC20   RSNnn   XRC16   XRSNDCC10823     DCC10823  RSNDCC10823
  The C10823 is a DB2 reason code indicating a level mismatch
  between the Call Attach Facility and DB2.  This problem can
  occur when a STEPLIB to DB2 is added to the batch job.  If the
  STEPLIB includes data sets that are non-APF authorized, the
  DB2 module will be considered non-authorized.  MVS continues
  looking for an authorized version, and finds it in LNKLST,
  but the version in LNKLST is for the old level of DB2.
  Solution: Make sure all data sets in STEPLIB are authorized.
  *******************************************************
   RC20   RSNnn   XRC16   XRSNE0020100     E0020100  RSNE0020100
  May occur when an error is detected on a SUPERLOCATE request
  for a collection.  This can occur because the ALIAS and the
  collection name are the same.  This can be corrected by giving
  the collection name a second level qualifier.
     It can also occur if the collection exit
  has not been installed correctly under ODM 2.
  Running a GTF trace for SUPERLOCATE SVC 26 will
  show the name of the collection passed to
  OAM in the DSN/CI field. The collection name
  default in the ODM 2 collection exit, EKCCCLLX,
  is CBR.CLLCT000.P10.  The job that installs the
  collection exit is EKCCLXLK.
   Check for damage to the catalog by issuing a LISTCAT for
  the collection entry.
  *************************************************************
   RC20   RSNnn   XRC16   XRSNE0020200     E0020200 RSNE0020200
  Catalog error detected on DEFINE request for a collection.
  Make sure that a user catalog has been set up and that there
  is an ALIAS name for the collection in the master catalog
  pointing to the user catalog. This problem could be a RACF
  authorization problem because an attempt is being made to
  store the collection name into the master catalog.
  ***********************************************************
   RC20   RSNXX   XRC16   XRSNE0020400     E0020400 RSNE0020400
  Received when DB2 is unable to access OAM'S DB2 tables.
  Typically, this is an authority problem. Verify that the DB2
  GRANTs for OAM and ODM (if applicable) have been done.  Check
  for any required authorization by your security package. If
  you cannot find the error, run a CICS AUX trace.  The error
  a non-zero value in FIELD B. The value in FIELD B is the DB2
  reason code.  The meaning of the DB2 reason code is described
  in the DB2 Messages and Codes manual.
  - This error has also been reported as a result of having
  down level copies of CBRICONN and CBRHTRAN in the DFHRPL
  concatenation.
  - Another condition that may cause this failure on a DFP3.2 or
  DFP3.3.0 system is no RCT entry for the OSMC transaction.
  *************************************************************
   RC20   RSNnn   XRC16   XRSNE0020900    E0020900  RSNE0020900
  occurs when OAM encounters a CAF error.  To find the CAF
  reason code, start a DSNTRACE and recreate the error.  The
  DSNTRACE is documented in the DB2 Application Programmer's
  Guide.
   This error has occurred when a user submitted a batch
   application and the user was not authorized.
  ************************************************************
   RC20   RSNnn   XRC16   XRSNE0020B00     E0020B00  RSNE0020B00
   There is an error in the OSMC PCT entry for the OSMC
   transaction or there is no RCT.  Check the CICS installation
   parameters section of the OAM PISA.
   NOTE: This error should only occur on the first store to
   a new collection.  (DFP330 and earlier only).
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• This is an Informational apar for OAM to document the
  return reason codes
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels