Error conditions

VSAM R/M returns to its caller return codes in register 15 and feedback words set in the request parameter list (RPL + X'0C'). See the chapter on macro instruction return codes and reason codes in z/OS DFSMS Macro Instructions for Data Sets, for a description of all such codes.

When diagnosing a problem, record the 4-byte RPL feedback word on the keyword worksheet in Keyword worksheet. Append the 4-byte field to the keyword prefix RC.

Example: The RPL feedback word is 2D08009C; specify this modifier keyword as shown:

     RC2D08009C

The IBM® Support Center can use these codes to determine which module is in control and the reason the error occurred. You can use the codes in the RPL feedback word with other portions of the VSAM record management diagnostic aids to obtain additional failure-related information. The IBM Support Center may request an additional dump using the VDUMPON command or the SLIP service aid to trap the error code when it is being set by a module.

The RPL feedback word is located at offset 12 (X'0C') in the RPL and contains the following information.

RPL	Length	Description
12(X'0C')	1	Problem determination function (PDF) code. This helps identify the module that detected the error.
13(X'0D')	1	RPL return code. This code is returned in register 15.
14(X'0E')	1	Component code. This code identifies the component being processed when the error occurred.
15(X'0F')	1	Reason code. This code, when paired with the return code in the second byte, identifies the reason for an error.

RPL Condition Code (2 bytes) consists of component code (RPLCMPON) and reason code (RPLERRCD). RPL Feedback Area (3 bytes) also includes return code (RPLRTNCD). RPL Feedback Word - RPLFDBWD (4 bytes) also includes PDF code (RPLFUCD).

When analyzing a problem involving record management, consider the following items:

What kind of application program was running when the error was encountered?
- User application
- IMS™ application
- CICS® application
- CICS running under IMS.
- System function (SMF/catalog)
- Other application
What was the application program attempting to do when the error occurred?
What were the request options? (Get/Put, Dir/Seq, Syn/Asy, and so forth).
Where, within record management, was the error encountered?
- Abend type-of-failure: use failing PSW instruction address.
- Wait type-of-failure: use information from the RB that issued the Wait SVC.
- RPL feedback error (RPL +X'0C'): See the chapter describing VSAM macro instruction return codes and reason codes in z/OS DFSMS Macro Instructions for Data Sets.
What was record management attempting to do when the error occurred?
- If the failure-related documentation is produced while record management is processing, you can use the PLH R14 push-down stack to identify the function being performed when the failure occurred.
Is the data set damaged?
- You may use the EXAMINE command to analyze a data set's integrity (whether it is damaged or not). If a data set is damaged, EXAMINE provides details about the nature of the damage. See the chapter describing functional command format in z/OS DFSMS Access Method Services Commands for details about the EXAMINE command.