CICS actions on a cold start

In a cold start, initialization of CICS occurs with limited reference to any system activity recorded in the CICS catalogs. With the exception of resynchronization information for remote systems noted below, no system log or warm keypoint information is used from any previous run of CICS. Dump table entries from a previous run are also deleted in a cold start.

In a cold start:
  • TERMINAL definitions are purged from the recovery file and from the catalog.
  • Existing TYPETERM and MODEL definitions are purged from the catalog.
  • PROGRAM definitions are purged from the recovery file and from the catalog.
  • TRANSACTION and PROFILE definitions are purged from the global catalog.
  • Transient data queue (TDQUEUE) definitions are purged from the catalog.
  • File control records are purged from the catalog.
  • Any program LIBRARY definitions that had been dynamically defined will be lost. Only the static DFHRPL concatenation will remain, together with any LIBRARY definitions in the grouplist specified at startup or installed via BAS at startup.
  • Resource definition information is obtained as follows:
    • Tables specified by system initialization parameters, such as MCT=xx, are obtained from the program library.
    • Information in the groups in the list named by the GRPLIST system initialization parameter for this initialization is taken from the CICS system definition (CSD) file and merged with information from the program library.
    • Information in groups that have been defined or added to group lists is taken from the CSD.
  • Resynchronization information relating to remote systems or to RMI-connected resource managers is preserved. The CICS system log is scanned during startup, and information regarding unit of work obligations to remote systems, or to non-CICS resource managers (such as DB2®) connected through the RMI, is preserved. (That is, any decisions about the outcome of local UOWs, needed to allow remote systems or RMI resource managers to resynchronize their resources, are preserved.)

    However, note that recovery information for remote systems connected by LU6.1 links, or for earlier releases of CICS systems connected by MRO is not preserved.

  • The journal DFHLOG and DFHSHUNT entries in the catalog are used, and all other journals and journal models are purged.


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