End of CICS startup

Whichever type of startup is performed, when the DFHSI1517 message is displayed on the operating system console, CICS is ready to process terminal requests.

When the startup process is completed, users are able to enter transactions from any terminals that are connected to CICS. For information about the CICS-supplied transactions, see CICS supplied transactions descriptions.

Even though DFHSI1517 signals the end of system initialization, the region might not be fully ready to receive 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.

You can allow CICS® to have a warm-up process by setting the WLMHEALTH system initialization parameter. If the z/OS® Workload Manager health service is active in the region, when the message DFHSI1517 is returned, the warm-up process is started. Then CICS adjusts the region's z/OS WLM health value to control flow of work into the region until the region is fully capable to process work. For more information about the CICS warm-up process, see CICS warm-up and cool-down by use of z/OS Workload Manager health service.