is successful, but CICS abnormally terminates before the catalog can be updated,
CICS recovers the information from the forward recovery records on the system
log.
If the installation or deletion of installable sets or individual resources is
unsuccessful, or has not reached commit point when CICS abnormally terminates,
CICS does not recover the changes.
In this way, CICS ensures that the terminal entries recovered at emergency restart
consist of complete logical sets of resources (for connections, sessions, and
pipelines), and complete terminal resources and autoinstall models, and that the
catalog reflects the real state of the system accurately.
TCAM and sequential (BSAM) devices
CICS installs TCAM and sequential terminal resource definitions from the TCT.
Because there is no warm keypoint if the previous run terminated abnormally, the
TCT cannot be modified as on a warm start. Whatever is defined in the TCT is
installed, and the effect is the same whether or not it is a different TCT from the
last run.
Note: CICS TS for z/OS, Version 4.1 supports only remote TCAM terminals. That
is, the only TCAM terminals you can define are those attached to a remote,
pre-CICS TS 3.1, terminal-owning region by TCAM/DCB.
Distributed transaction resources
CICS retrieves its logname from the recovery manager control record in the global
catalog for use in the “exchange lognames” process with remote systems.
Resynchronization of indoubt units of work takes place when CICS completes
reconnection to remote systems.
See the CICS Installation Guide for information about recovery of distributed units
of work.
Chapter 6. CICS emergency restart 65
To Next Page
Loading...
Need help?
General