CICS Transaction Gateway can be started
either as a batch job (the recommended option) or from the command
line.
- Submit JCL to start CICS® Transaction
Gateway as a batch job if you want to register with the ARM (Automatic
Restart Manager) component of MVS™. For
more information see Automatic restart management. ARM is the
recommended option.
- Alternatively you can start CICS Transaction
Gateway from the z/OS UNIX System Services command
line.
When you start the CICS Transaction Gateway, it reads
configuration information from ctg.ini, ctgenvvar, and stdenv. When
you issue the ctgstart command,
you can specify startup options to override this configuration information.
These options and their values are described in Options on the ctgstart command.
If XA support is enabled, the recoverable resource
management services (RRMS) of the z/OS® sync
point manager are required.
CICS Transaction Gateway accesses
RRMS through CTGRRMS services which run in a separate address space.
This address space is started in these circumstances:
The CTGRRMS address space remains for the life of the z/OS image. See
Enabling CTGRRMS services for information
about CTGRRMS services. See
Starting, stopping or refreshing the CTGRRMS services for
information about how to start, stop and restart CTGRRMS services.
A
Gateway daemon cold start option startup is provided. Cold start is
for use with XA transactions and ensures residual records in RRS are
cleaned up after failure of a transactional component, or by manual
intervention by an operator through the RRS panels. For more information
see Cold start.