SYSABEND or SYSUDUMP
When a Db2 or IRLM abend occurred, a SYSABEND or SYSUDUMP dump might occur.
Procedure
To locate the abend completion code and the abend reason code, if there is one, and use the code in a set of keywords:
- Determine whether there is also an SVC dump for this abend.
- Issue the z/OS® DISPLAY DUMP command. Refer to the z/OS system commands publication, if necessary.
- Verify that the SVC dump has the same date, time stamp, and program name as those in the SYSABEND or SYSUDUMP. For information about printing the summary dump, see Printing dumps.
- If there is a corresponding SVC dump, continue with the
steps below. Otherwise, go to Step 3.
- Review the dump title and verify that COMP=XYR00 or COMP=XYR01. If it does not, the problem might not be Db2. Consult the z/OS diagnostic techniques publication to determine the failing product.
- Locate the three-character completion code that follows
the word
ABND.- If the completion code is X'071' or X'122', the operator pressed the RESTART key or canceled the job, probably to break a loop. Turn to WAIT/LOOP keywords.
- If the completion code is anything except X'04E', build
a keyword similar to ABENDxxx,
replacing xxx with the completion code.
Add this information to the keyword string and turn to CSECT keyword.
5740XYR00 R111 ABEND0C4 (free format) PIDS/5740XYR00 LVLS/111 AB/S00C4 (structured format) - If the completion code is X'04E', find the 4-byte reason code follows it. For an example, see SVC dump titles that are issued by Db2.
- Review the diagnostic information for this reason code, and follow any recommended procedures.
- Build a keyword similar to ABEND04E RCxxxxxxxx,
replacing xxxxxxxx with the reason code.
Add this information to the keyword string and turn to CSECT keyword.
5740XYR00 R111 ABEND04E RC00E20015 (free format) PIDS/5740XYR00 LVLS/111 AB/S004E PRCS/00E20015 (structured format)
- If there is no corresponding SVC dump, follow
the steps below.
- Locate the three-character completion code. This information
follows the words
COMPLETION CODEon the first page of the SYSABEND or SYSUDUMP. For an example, see Figure 1.- If the completion code is X'071' or X'122', the operator pressed the RESTART key or canceled the job, probably to break a loop. Turn to WAIT/LOOP keywords.
- If the completion code is X'04E', locate the registers
at time of error (identified by
REGS AT TIME OF ERROR). See The RTM2WA summary in a SYSUDUMP for an example.Locate the reason code in register 15, the last register shown. Build a keyword similar to ABEND04E RCxxxxxxxx, replacing xxxxxxxx with the reason code. Add this keyword to the string and turn to CSECT keyword and use Procedure using a SYS1.LOGREC entry.5740XYR00 R111 ABEND04E RC00E50063 (free format) PIDS/5740XYR00 LVLS/111 AB/S004E PRCS/00E50063 (structured format) - If the completion code is not X'071', X'122',
or XX'04E', determine whether the problem occurred in Db2. (SYSUDUMP and SYSABEND dumps
are rarely taken for Db2 internal
errors; invalid user data is usually the cause.)
- Check the failing PSW address in the list of CDE entries for the
task. If the failing address falls within the range of a module name
beginning with
DSN
, the failure occurred in a Db2 attachment module. - If the failing PSW address is outside the normal addressing range
(such as zero), check the address in register 14 at time of failure.
If this address falls within the range of a module name beginning
with
DSN
, the failure occurred in a Db2 attachment module or stored procedure module. - Compare the following items:
- The PASID value in XSB that is associated with the active RB at the time of failure
- The first four digits of the IDSQ field in the ASCB.
- Check register 15 at time of failure. If it contains a reason
code of X'00F300'nn, then one of
the following situations occurred:
- The abend took place in Db2 while processing a parameter supplied by the attachment subcomponent, and the passed parameter is in error.
- The SQLCA address is invalid, and the problem is in the application program.
- An invalid reason code or authorization ID was returned by an authorization exit routine, and the problem is in the application program.
- Check the failing PSW address in the list of CDE entries for the
task. If the failing address falls within the range of a module name
beginning with
- If the problem is not in Db2, check the application program. Often, there is invalid user data and, upon retry, an SQL error code is returned.
- If the problem appears to be in Db2, build a keyword similar to ABENDxxx,
replacing xxx with the completion code.
Add this information to the keyword string and turn to CSECT keyword and use Procedure using a SYS1.LOGREC entry.
5740XYR00 R111 ABEND0C4 (free format) PIDS/5740XYR00 LVLS/111 AB/S00C4 (structured format)
- Locate the three-character completion code. This information
follows the words