Warm start

With this type of start, DBCTL is brought up in the environment it was in when it terminated normally using a /CHECKPOINT FREEZE or /CHECKPOINT PURGE command.

This is described in Stopping DBCTL normally. After a warm start, resources are in the same state they were in at the time the system was shut down.

The difference between the FREEZE and PURGE keywords applies to BMPs. FREEZE stops them after the next checkpoint, or at program completion, whichever is the sooner, and PURGE allows them to complete. See Operations and automation in IMS product documentation for a list giving guidance on the differences between these options.

To request a warm start of DBCTL, use the /NRESTART command without CHECKPOINT 0.

Any indoubt UOWs are re-created for this type of start. (An indoubt UOW is a piece of work that is pending during commit processing. If commit processing fails between DBCTL’s response to CICS’s request to prepare for commit and CICS’s decision to execute the commit, recovery processing must resolve the status of any work that is indoubt.) See Resolving indoubt CICS DBCTL units of work manually for information on using operator commands to resolve indoubt UOWs.