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

► You are upgrading to a new version
► You need more than 100 simultaneous pipes to CICS regions
► You need to workload manage incoming EXCI requests
The following areas need to be considered when cloning a CICS TG started task:
► Set RACF permissions on the CICS TG started task
► Clone started task JCL
► Create a new logging directory in UNIX System Services
► Create a new CONNECTION definition in CICS
► Create new STDENV member
– Change the default CICS TG and TCP/IP ports
– Change pipe name, if necessary
– Change the location of the CTG.INI if necessary
– Change the CICS TG starting location if necessary
– Change the RRMNAME if necessary
We detail each step in this process. However, we assume you have previously
performed these tasks to set up the gateway. We do not go into as much detail as
we have in previous sections.
1. RACF permissions on the CICS TG started task
If you have set up RACF definitions based on your CICS TG started task
name, you will need to issue these commands again with your new CICS TG
started task name. This could include creating a new user default user ID for
your CICS TG started task.
If you allow MRO link access on the CICS TG started task user ID, you will
have to update this as well.
2. Clone started task JCL in your proclib
This involves creating a new started task and pointing it to a new STDENV
file. You will also want to point your STDOUT and STDERR to different
locations.
3. Create a new logging directory in UNIX System Services
The default is to send logs and traces to the same directory as the CICS TG
executables. We found that turning traces on could consume a great deal of
space.
In our CICS TG JCL, we point our traces to a different directory, which is more
of a good administration practice than a requirement. We mounted a different
HFS data set as this directory, so our logging directory could fill up without
causing problems for the CICS TG.
4. New connection on CICS
Chapter 7. TCP connections to the Gateway daemon on z/OS 169