Example 1:

SM Error: ASM FAILED TO RETRIEVE OBJECT, RC=2,
Reason=0, File=arssmsms.C, Line=789  
Srvr->www.example.com 192.0.2.0<-

Example 2:

ARS0020E  SM Error: RC=9, REASON=0,
FILE=ARSSMSMS.C, LINE=431

Example 3:

SM Error: ARSMVSDW: 0000000B(0000000C-7404FCDB)
PROD.ONDEMAND.DATA(BAA.R11), RC=11, REASON=0,
FILE=ARSSMSMS.C, LINE=304
SRVR->WWW.EXAMPLE.COM 192.0.2.0<-

When the reason code is 11 in an ARS0020E message, the value in the first parenthetical expression (0000000C-7412FCDB) corresponds to the OAM return code and reason code (return_code-reason_code). In this example, the following list explains the value:

• The OAM return code is 12 (X'C).
• Byte 0 of the OAM reason code is X'74, which indicates a DB2® error.
• Bytes 2 and 3 of the OAM reason code are X'FCDB. Convert it to decimal, which is -805. Look up -805 in the list of DB2 messages and codes, which is message DBRM OR PACKAGE NAME location-name.collection-id.dbrm-name.consistency-token NOT FOUND IN PLAN plan-name. REASON reason-code.

An alternative way to identify the OAM return code and reason code is to issue the following TSO OSREQ command. Specify the collection and object names from the ARS0020E message:

OSREQ QUERY PROD.ONDEMAND.DATA BAA.R11
OSREQ QUERY unsuccessful. Return code = 0000000C, reason code = 7412FCDB.
OSREQ QUERY response time is 53 milliseconds.

When the reason code is 10 in an ARS0020E message, the value in parentheses is an internal diagnostic code used by IBM® Support.

Example 4: In the following example, OAM passes the corresponding DB2 errors to Content Manager OnDemand through the OAM OSREQ MSGAREA:

SM Error: ARSMVSRE: 0000000B(0000000C-8802FC78) PROD.ONDEMAND.
 DATA(BAA.R11) OAM OSREQ MSGAREA:  DSNT408I SQLCODE = 
 -904, ERROR:  UNSUCCESSFUL EXECUTION CAUSED BY AN                             
 UNAVAILABLE RESOURCE. REASON 00C90081, TYPE OF RESOURCE                       
   00000200, AND RESOURCE NAME GROUP00 .OSMOTS04                               
 DSNT418I SQLSTATE   = 57011 SQLSTATE RETURN CODE                              
   DSNT415I SQLERRP    = DSNXRINS SQL PROCEDURE DETECTING ERROR                
     DSNT416I SQLERRD    = -110  13172746  0  13223106  -974970879             
 12714050          SQL DIAGNOSTIC INFORMATION                                  
             DSNT416I SQLERRD    = X'FFFFFF92'  X'00C9000A'  X'00000000'        
 X'00C9C4C2'  X'C5E32001'  X'00C20042' SQL               
 DIAGNOSTIC                    INFORMATION              
, RC=11, REASON=0, FILE=ARSSMSMS.C, LINE=304 SRVR->WWW.EXAMPLE.COM 127.0.0.1<-

As in example 3, the value in the first parenthetical expression corresponds to the OAM return code and reason code. However, the OAM OSREQ MSGAREA displays the corresponding DB2 errors so that you do not need to convert X'0000000C-8802FC78' to decimal and then look up the return codes and reason codes in the OAM or DB2 publications. If you did convert X'0000000C-8802FC78' and look up return codes and reason codes, the following list explains the results:

• The OAM return code is X'C'.
• Byte 0 of the OAM reason code is X'88', which indicates a DB2 error.
• Bytes 2 and 3 of the OAM reason code are X'FC78'. Convert X'FC78' to decimal, which is -904. Look up -904 in the list of DB2 messages and codes, which is UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name.

The OAM OSREQ MSGAREA displays SQLCODE -904 with values for reason-code, resource-type, and resource-name: UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C90081, TYPE OF RESOURCE 00000200, AND RESOURCE NAME GROUP00 .OSMOTS04.

Example 5:

SM Error: ANS0266I (RC2302) The dsmEndTxn is ABORT, so check the reason field., 
RC=2302, Reason=29, File=arssmsms.C, Line=744, Srvr->spnode05<- 
An error occurred. Contact your System Administrator and/or consult the 
System Log. File=arsadmin.c, Line=576
Unable to store the object >2339FAAA<. Object size 239831.
Loaded 0 rows into the database.
ars_load: Thu Oct 28 17:31:04 BST 2003 -- Loading failed