Recovering from IMS application failure
You can recover from a situation in which an IMS application abnormally terminates in a Db2 environment.
Symptoms
The following messages are issued at the IMS master terminal and at the LTERM that entered the transaction that is involved:DFS555 - TRAN tttttttt ABEND (SYSIDssss);
MSG IN PROCESS: xxxx (up to 78 bytes of data) timestamp
DFS555A - SUBSYSTEM xxxx OASN yyyyyyyyyyyyyyyy STATUS COMMIT|ABORT
Causes
The problem might be caused by a usage error in the application or by a Db2 problem.Environment
- The failing unit of recovery is backed out by both DL/I and Db2.
- The connection between IMS and Db2 remains active.
Resolving the problem
Operator response:
- If you think that the problem was caused by a usage error, investigate and resolve the error.
- If you think that the problem is a Db2 problem, rather than a usage error, try to diagnose the problem using standard diagnostic procedures. You might need to contact IBM® Support if you cannot resolve the problem yourself.