Recovering from IMS control region failure
You can recover from a problem in which the IMS control region fails.
Symptoms
- IMS waits, loops, or abends.
- Db2 attempts
to send the following message to the IMS master
terminal during an abend:
DSNM002 IMS/TM xxxx DISCONNECTED FROM SUBSYSTEM yyyy RC=RC
This message cannot be sent if the failure prevents messages from being displayed.
- Db2 does not send any messages for this problem to the z/OS® console.
Environment
- Db2 detects that IMS has failed.
- Db2 either backs out or commits work that is in process.
- Db2 saves indoubt units of recovery, which need to be resolved at reconnection time.
Resolving the problem
Operator response: Use normal IMS restart
procedures, which include starting IMS by issuing
the z/OS START
IMS command. The following results occur:
- All DL/I and Db2 updates that have not been committed are backed out.
- IMS is automatically reconnected to Db2.
- IMS passes the recovery information for each entry to Db2 through the IMS attachment facility. (IMS indicates whether to commit or roll back.)
- Db2 resolves the entries according to IMS instructions.