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

Static LU names
We simplified our configuration by using static definitions. With this method the
LU names are pre-set and not generated dynamically. This is useful if you only
have a few Client workstations or in situations where you might want to match the
LU name (NETNAME) with a specific connection in CICS, for security, audit, or
other reasons.
Dynamic LU name generation
It is also possible to use dynamic LU name generation with TCP62 connections.
This reduces the amount of configuration required and has the added benefit of
allowing the same CTG.INI configuration file to be used on all the workstations in
your TCP/IP subnet. For more details refer to “TCP62 dynamic LU names” on
page 48.
In Figure 3-2, we illustrate an overview of our TCP62 environment that shows
how we configured in this chapter.
Windows 2000
CICS TG
TCP62
TCP/IP
Figure 3-2 CICS TG TCP62 configuration
IP network
LU6.2/IP
z/OS
CICS TS
(SCSCPJA1)
VTAM
AnyNet
TCP/IP
volga.almaden.ibm.com wtsc66.itso.ibm.com
9.1.38.39
9.12.6.6
Tip: We also found it was possible to move the CTG.INI file to the AIX platform
without making any modifications, and use our TCP62 configuration to
connect our CICS TG for AIX to CICS. However, on some platforms the
protocol drivers have different names (for more information see 9.3, “Testing
the configuration” on page 224). To avoid this, the ctgcfg command can be
run with the -plat option, specifying the particular platform required. The list
of possible platforms can be queried using the command ctgcfg -?.
Chapter 3. TCP62 connections to CICS 41