00E50013
Explanation
A DB2® execution unit has been abended. This abend code must ultimately be issued by resource managers when the CANCEL exit is driven as a result of a suspend request.
System action
The agent cancel processing continues.
Normally, this situation does not result in a dump. However, a dump might result if the situation is encountered by other resource managers, outside of DB2. When that happens, the dump can be ignored or suppressed.
Operator response
Notify the system programmer only if the abend results in the termination of the DB2 subsystem.
System programmer response
This reason code may be issued as a result of any connected TCB abend, or operator -STOP DB2 MODE(FORCE) command. No further action is required.
The recovery routine for the CSECT issuing this reason code records information in the variable recording area (VRA). If you suspect an error in DB2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.
Problem determination
If DB2 abends, examine the SVC dump to determine the suspended resource manager and the state of the failing subcomponent. For example, the ACEMC (must complete) bit should be off.
In some cases, this problem might occur because DB2 encountered unexpected user-created catalog index definitions that interfere with the migration process. See the information about migration job DSNTIJPM and the information about creating indexes on catalog tables in the description of CREATE INDEX.
- Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
- Dynamic dump, taken to SYS1.DUMPxx data set, by DB2 (04E and 04F abends).
- Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.