CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

7.4.2 Tracing
170 CICS Transaction Gateway V5
While it is possible to share a pipe, it’s best to set up a new connection within
CICS. We found it helpful in problem diagnosis to set up a different pipe as
well as a different terminal prefix. Any transactions coming in via the new pipe
are assigned the new terminal ID.
5. Create a new STDENV member
a. Change the default CICS TG and TCP/IP ports
Depending on your implementation, you might want to change the default
ports. If you do this, be sure to also change the applications connecting to
the new CICS TG.
If you are cloning your CICS TG to support workload balancing, you may
want to keep the same ports and use the SHAREPORT parameter of
TCP/IP.
b. Change pipe name, if necessary
Changing the pipe name when cloning a CICS TG may be a good idea,
because it can help with diagnostics. Doing this will also require a new
CICS CONNECTION definition and changes to the RACF profiles that
control MRO link security.
c. Change the location of the CTG.INI if necessary
We used the CICSCLI variable to set the location of our CTG.INI to our
own /ctg/scsctg4 HFS directory. If you run multiple Gateway daemons, we
suggest you set up a new CTG.INI file for each Gateway, unless you wish
to clone address spaces when using TCP/IP port sharing.
d. Change the CICS TG starting location if necessary
If cloning the same release and maintenance level, you do not have to
update the stating location of the CICS TG in the CICS TG JCL. However,
if you are testing new maintenance or a different release, you will have to
change the starting locations using the environment variable
CTGSTART_HOME. For details on how we set our environment variables,
refer to 7.2.1, “Defining CICS TG environmental variables” on page 148.
You may make references to the starting location in your ctgenvvar and
STDENV DD members, so you should check these as well.
e. Change the CTG_RRMNAME if necessary
If using RRS, you will need to set up a unique CTG_RRMNAME for each
CICS TG address space.
To demonstrate the types of traces available, we show you how to diagnose an
error using EXCI, CICS TG and JNI traces. We created an error by specifying an