
CICS warm-up and cool-down by use of z/OS Workload Manager health service
By use of the z/OS® Workload Manager (z/OS WLM) health service, you can allow CICS® to have a warm-up process after the end of system initialization to control flow of work into the region until the region is fully ready to receive work. You can also allow CICS to have a cool-down process before system shut-down to limit flow of work into the region.
Benefits
Using the z/OS WLM health service to control flow of work into the CICS region after the completion of system initialization and before CICS shutdown has the following benefits:
- A system warm-up process can mitigate problems that can be caused by work flowing into a CICS region just after the completion of system initialization.
- Even though DFHSI1517 signals the end of system initialization, CICS might still not be fully ready to receive and process work. This is because
in some cases initialization continues after this message. For example, some bundle-defined
resources are being installed asynchronously; so resources such as JVMSERVERs required for some
applications have not completed initialization, even though the TCP/IP listener is open and
accepting work. This could cause transactions to abend. For web services, a pipeline scan might not
have completed, so use of the web service before the scan completes will fail.
A system warm-up process can be used to control work flowing into CICS when the region is not yet running at optimum performance.
- You have a lot of flexibility over control of the warm-up or cool-down process.
- How long a CICS region needs to warm up before it is fully healthy depends on the types of applications being processed and the set of resources they employ. You can control the warm-up or cool-down process based on the need of each CICS region.
How to activate and set up the z/OS WLM health service
The z/OS WLM health service is enabled by default. If the service is disabled, to activate this service for a CICS region, you must set the WLMHEALTH system initialization parameter. In WLMHEALTH, you must specify an interval value and a health adjustment value.
When the region is operating, you can change the interval value and health adjustment value by using the SET WLMHEALTH SPI command, CEMT SET WLMHEALTH, the CICSPlex® SM web user interface, or the CICS Explorer®.
What happens during CICS warm-up or cool-down
When the z/OS WLM health service is active in a CICS region, CICS informs the z/OS Workload Manager of the health state of the region. The region's z/OS WLM health indicator is an integer in the range 1 - 100. A value of 100 means that the region is fully capable to do work without any health problems whereas 0 means that it is not able to do any work.
- CICS warm-up process
- During early CICS initialization, the region's health indicator is set to zero. When the DFHSI1517
Control is being given to CICS message is returned, the CICS warm-up process starts. At each interval, CICS calls the z/OS Workload Manager Health (IWM4HLTH) API to increment the region's health indicator from zero, by a specified adjustment value, until the health indicator reaches 100.
If the interval value on the WLMHEALTH parameter is set to zero, the health indicator of the region remains at zero. To initiate a warm-up process for this region, you must change the interval to a non zero value and set WLMHEALTH open by, for example, issuing a SET WLMHEALTH SPI command.
- CICS cool-down process
- A cool-down process can be initiated by issuing a SET WLMHEALTH CLOSE SPI command. At each interval, CICS calls the z/OS Workload Manager Health (IWM4HLTH) API to decrement the region's health indicator from 100, by the adjustment value, until the health indicator is zero.
How use of z/OS WLM health service affects CICS
The health state of a CICS region affects how favorable the region is a target for connections. CICS and CICSPlex SM components such as the CICS-MQ adapter react to the region's health state.
- TCP/IP
- When TCP/IP is configured, the health indicator will feed into the WLM server recommendations to sysplex distributor, affecting when connections are established with a CICS region.
- MQMONITOR
- Changes in the region's health state can have an effect on when MQMONITORs with attribute AUTOSTART(YES) are started or stopped. When the health indicator is less than 100, all started MQMONITORs are subject to a throttle limiting the messages that a single MQMONITOR can process. For details, see Effect of z/OS Workload Manager Health service on MQMONITORs.
- CICSPlex SM
- CICSPlex SM workload distribution takes account of the region's z/OS WLM health state in the routing algorithm. When CICSPlex SM Workload Manager is deciding where to route work, a region with a health indicator of zero is less favorable than a region with a non-zero health indicator. For details, see Effect of the z/OS WLM health service on CPSM workload routing.
How to initiate CICS warm-up or cool-down
If set up correctly, a CICS warm-up process starts automatically at the end of system initialization.
You can also initiate a CICS warm-up or cool-down process using the SET WLMHEALTH SPI command, CEMT SET WLMHEALTH, the CICSPlex SM web user interface, or the CICS Explorer.
