When operating CICS® Transaction
Gateway, it is important to start the product, and the services it
uses, in the correct sequence. It is also important to shut down everything
in the correct sequence, so that inflight transactions can complete.
Startup and shutdown
The preferred order in which to start CICS, CICS Transaction Gateway and certain
services, and optional considerations such as Resource Recovery Services
(RRS).
Gateway daemon administration
Gateway daemon administration tasks include starting and
stopping, tracing, displaying statistics and obtaining JVM dumps.
Administering XA transactions with Resource Recovery Services
If communications
between an application server and the CICS Transaction Gateway are interrupted
and XA transactions
are in progress, some transactions might be left in an indoubt state.
To resolve these issues, restore communication with the application
server, and use the application server system to correct the state
of the transactions.
Administering transactions that use IPIC connections
Support for XA is provided for all transactions that use
IPIC connections. You use the CEMT inquire command to discover the
transactions that use IPIC connections.
Understanding system time
The system time can be changed while CICS Transaction Gateway is running.
If you do this, active processes respond to the changed time and not
to the elapsed time.
Restarting Resource Recovery Services (RRS)
The CICS Transaction Gateway does
not support a restart of the Resource Recovery Services (RRS) while
any instances of the Gateway are running.