DFS629I IMS ttt TCB <action> IMS|SYS sss|uuuuvvvv
Explanation
or
or
or
or
IMS DBC REGION ABEND
Explanation
For IMS online, the first form of the message is issued; the third and fourth form might be issued. For IMS batch, the second form is issued; the third form might be issued.
For a Database Control (DBCTL) subsystem, the fifth form is issued when the DBCTL or z/OS operator issues a MODIFY command to stop the DBCTL region.
In the message text, the variables
have the following meanings:
- ttt
- IMS TCB type name
- action
- The action is ABEND if the IMS control region is terminating or DUMP if a memory dump is being produced for a dependent region.
- sss
- The system abend code, if available
- uuuu
- The user abend code (if available) or the system abend code
- vvvv
- The failing IMS address space or external subsystem
- DLS
- The failure was for a TCB in the DL/I address space.
- IES
- The failure was in the IMS support code of an external subsystem.
- ESC
- The failure was not in the IMS support code for the failing external subsystem.
- U0027
- Original abend code
- No value
- The failure was in the IMS CTL address space.
- hh..hh
- Hexadecimal PSW contents
- cccccccc
- Module executing at time of the error
- aaaaaaaa
- Hexadecimal address of module entry point
System action
For some IMS TCB failures, the IMS system terminates. For other IMS TCB failures, (such as dynamic allocation, Fast Path-dependent region, storage compression, and some DBRC failures) IMS continues processing. For IMS external subsystem failures, the external subsystem task terminates.
Operator response
If an external subsystem task terminates, restart the task with the /START SUBSYS command.
Programmer response
To determine the cause of the problem,
examine the diagnostic output, which can include:
- Spin-off dumps created by IMS external subsystems or DBRC.
- Software LOGREC entries created by dynamic allocation.
- Fast Path-dependent region dumps created by Fast Path-dependent regions.