Resolving indoubt CICS DBCTL units of work manually

However, you may sometimes need to do this yourself. For example, if a CICS system using DBCTL disconnects abnormally from DBCTL (for instance, if CICS or DBCTL abends, or CDBC DISCONNECT IMMEDIATE is issued), there may be some incomplete updates about which DBCTL is in doubt. Even if CICS then needs to perform a cold start for some reason, it normally recovers enough information to resolve indoubts automatically. However, if CICS is started with the START=INITIAL system initialization parameter, it loses its record of the indoubt updates and they must be resolved manually. You are strongly advised not to start CICS with START=INITIAL specified when there are indoubt units of work outstanding.

The DFS2283I message, issued during the resynchronization process, indicates that there are UOWs that have not received a COMMIT or ABORT request, and are therefore indoubt.

In this situation you must use DBCTL operator commands (described in Using DBCTL operator commands to resolve in-doubts) to resolve the in-doubts.