CICS recovery manager

The recovery manager ensures the integrity and consistency of resources (such as files and databases) both within a single CICS® region and distributed over interconnected systems in a network.

 Figure 1 shows the resource managers and their resources with which the CICS recovery manager works.

The main functions of the CICS recovery manager are:
  • Managing the state, and controlling the execution, of each UOW
  • Coordinating UOW-related changes during syncpoint processing for recoverable resources
  • Coordinating UOW-related changes during restart processing for recoverable resources
  • Coordinating recoverable conversations to remote nodes
  • Temporarily suspending completion (shunting), and later resuming completion (unshunting), of UOWs that cannot immediately complete commit or backout processing because the required resources are unavailable, because of system, communication, or media failure
Figure 1. CICS recovery manager and resources it works with
This figure illustrates, in the form of a wheel, the resource managers with which the CICS recovery manager works. At the hub of the wheel is the system log. Circling the log is the recovery manager, which provides the recovery interface between the log and resource managers that are positioned around the outer rim. The resource managers are shown in three groups: local resources managers; the resource manager interface (RMI); and the communications managers. The local resource managers are, in clockwise order, RDO, temporary storage, transient data, file control, and VSAM RLS. The RMI managers are DB2, DBCTL, and MQ. The communications managers are MRO, LU6.1, and LU6.2.


dfht25q.html | Timestamp icon Last updated: Sunday, 4 June 2017