z/OS MVS Programming: Writing Transaction Programs for APPC/MVS
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Diagnosing Product-Specific Errors

z/OS MVS Programming: Writing Transaction Programs for APPC/MVS
SA23-1397-00

If your TP receives a decimal return code 20 from a call, either:
  • APPC/MVS is not active, or
  • A product-specific error occurred.

This return code often has an accompanying symptom record in the logrec data set. If APPC/MVS is not active, however, a symptom record is not produced. In this case, your TP can call the Error_Extract service, which returns decimal code 64 when APPC/MVS is not active. No further diagnostic information is available when APPC/MVS is not active.

When a symptom record is recorded in the logrec data set, section 3 of the record contains the primary symptom string for the product-specific errors:
 Symptom                        Description
 -------                        -----------
 PIDS/5752SCACB                 Product identifier
 RIDS/ATBxxxxx                  CSECT name
 RIDS/ATBxxxxx#L                Load module name
 LVLS/ddd                       Product level
 PCSS/ATBxxxx or CMxxxx         Statement that caused the error
 PRCS/dddddddd                  Return code returned to the caller
 FLDS/REASON VALU/Hdddddddd     Unique reason code identifying the
                                product-specific error
Section 5 of the symptom record contains the following information for the product-specific error:
  • The job or user name (in EBCDIC) for the home address space of the caller
  • An EBCDIC description of the error (up to 80 characters)

Symptom FLDS/REASON VALU/Hdddddddd in section 3 of the symptom record contains one of the reason codes described in Table 1:

Table 1. Reason Codes for Product-Specific Errors
Reason Code Message Text Explanation
00000001 APPC SERVICE REQUESTED WHILE SYSTEM LOCK HELD. A user requested an APPC/MVS service while a system lock was held.
00000002 UNRECOGNIZED REQUEST. The system request from the caller is not one of the APPC CPI-C or APPC LU 6.2 calls. The program might be using an incorrect level of the stub routine.
All other reason code values Matches associated ATB8xxxxI message text. All product-specific error reason codes, except X'00000001' and X'00000002', are associated with a specific ATB8xxxxI message. You can use either the API trace facility or the Error_Extract service to obtain the message text, or:
  1. Convert the product-specific error reason code to decimal
  2. Use the decimal reason code value to find the associated ATB8xxxxI message through the table in Summary of Error_Extract Reason Codes.
  3. Refer to the appropriate ATB8xxxxI message description in Error_Extract (ATB8) Messages for an explanation, system action, and suggested response for the error.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014