Recovering Db2 when CICS is not operational
You can recover Db2 from a situation in which CICS® is not operational.
Symptoms
Any of the following symptoms might occur:
- CICS waits or loops.
- CICS abends, as indicated by messages or dump output.
Environment
Db2 performs each of the following actions:
- Detects the CICS failure.
- Backs out inflight work.
- Saves indoubt units of recovery that need to be resolved when CICS is reconnected.
Diagnosing the problem
If you think that CICS is in a wait or loop situation, find the origin of the wait or loop. The origin might be in CICS, in CICS applications, or in the CICS attachment facility.
If you receive messages that indicate a CICS abend, examine the messages and dump output for more information.
If threads are connected to Db2 when CICS terminates, Db2 issues message DSN3201I. The message indicates that Db2 end-of-task (EOT) routines have cleaned up and disconnected any connected threads.
Resolving the problem
Operator response:
- Correct the problem that caused CICS to terminate abnormally.
- Do an emergency restart of CICS.
The emergency restart performs each of the following actions:
- Backs out inflight transactions that changed CICS resources
- Remembers the transactions with access to Db2 that might be indoubt
- Start the CICS attachment
facility by entering the appropriate command for your release of CICS.
The CICS attachment facility
performs the following actions:
- Initializes and reconnects to Db2
- Requests information from Db2 about the indoubt units of recovery and passes the information to CICS
- Allows CICS to resolve the indoubt units of recovery