Service flow recovery on a CICS restart

If you restart the CICS Service Flow Runtime region, the DFHMAINS PLT program can ensure that any deployed service flows are available at the end of the system initialization process.

If you have specified 'NO_SFR_INST' on the INITPARM parameter for the region, no service flows install when you restart CICS. If you do specify a deployment directory on the INITPARM parameter, the processing that takes place depends on how the CICS region starts up.

Cold or initial start

If you perform a cold or initial start of the CICS region, the DFHMAINS program acts as follows:

  1. Deletes all of the records in the service flow repository file DFHMAASF.
  2. Reads the service flow files in the zFS deployment directory and defines them in DFHMAASF. You specify this directory on the INITPARM statement for the DFHMAINS program. The service flow files are identified by the file extension .sfp.
  3. Installs the service flow files that are contained in the zFS deployment directory.
  4. Creates the resource definitions for the service flows. This resource definition occurs only if selected during the deployment of the service flow in IBM Developer for z System z®.

When DFHMAINS finishes, the message DFHMA00002I is issued to the CICS console and log.

Warm start

If you perform a warm start of the CICS region, the DFHMAINS program acts as follows:

  1. Checks the zFS deployment directory for any new or updated service flow files.
  2. Installs the new or updated service flow files in CICS and updates the service flow repository file DFHMAASF.
  3. Creates the resource definitions required by the service flows. This resource definition occurs only if selected during the deployment of the service flow in IBM Developer for z Systems.

When DFHMAINS finishes, the message DFHMA00002I is issued to the CICS console and log.

Emergency start

If you cancel the CICS region to perform an emergency restart or if the CICS region abends, the DFHMAINS program does not check the zFS deployment directory for new or updated service flow files. All previously installed service flows are made available, but new service flows are not installed.

To install new service flows and optionally create the resource definitions, use the flow management transaction CMAN.



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