The preferred order in which to start CICS®, CICS Transaction Gateway and certain services, and optional considerations such as Resource Recovery Services (RRS).
You can create the files by editing copies of the sample configuration files.
Start command options are available to override some ctg.ini configuration file parameters. See Options on the ctgstart command for further details.
Start items in the following order:
If transactional support is required, RRS must be running on the same z/OS image as the one that CICS Transaction Gateway will use. CICS Transaction Gateway does not support a restart of RRS.
TCP/IP needs to be running before CICS Transaction Gateway is started. CICS Transaction Gateway supports a restart of TCP/IP, although no requests can be serviced until the stack is restarted.
Consider running CICS and CICS Transaction Gateway in the same z/OS image, to avoid EXCI pipes using slots in the XCF (cross-system coupling facility) group in the sysplex couple data set.
If transactional support is required, and the EXCI protocol is used to communicate with CICS, CICS and CICS Transaction Gateway must be in the same z/OS image.
CICS Transaction Gateway supports a restart of CICS, but requests fail with an ECI_ERR_NO_CICS error until CICS is available again.
If an automation tool requires the console to listen and write from the same address space as the invoking executable, set environment variable _BPX_SHAREAS to YES. This causes the Gateway daemon to run in the same address space as CTGBATCH.