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

Example 3-1 Content of ESA.SYS1.VTAMLST(APTCP01)
APTCP01 VBUILD TYPE=TCP,
CONTIMER=25,
DGTIMER=40,
DNSUFX=ITSO.IBM.COM,
EXTIMER=5,
IATIMER=60,
PORT=397,
TCB=10,
TCPIPJOB=TCPIPMVS
TCP01GRP GROUP ISTATUS=ACTIVE
TCP01LNE LINE ISTATUS=ACTIVE
TCP01PU PU ISTATUS=ACTIVE
Tip: The DNSUFX is the domain name suffix used by VTAM when sending
outbound allocates. This does not need to match the AnyNet domain name
suffix used in the CICS TG Configuration Tool (Figure 3-4 on page 47), but we
set it to the same value for simplicity. In practice, we found this value is only
required by VTAM if the CICS region is initiating binds (starting the
connection), which is not the case with a TCP62 configuration.
Dynamic LU name generation
We also configured dynamic creation of partner LUs in VTAM. This simplifies the
administration required in VTAM. To enable dynamic LUs, we specified
DYNLU=YES as a startup option for VTAM. A CDRSC definition is in effect a
partner LU 6.2 definition in VTAM for the LU on the workstation. Using dynamic
LUs meant that VTAM would create these definitions as required.
Tip: If you do not have DYNLU=YES as a startup option for VTAM, then you
will have to statically define cross-domain resource (CDRSC) definitions to
VTAM for all your CICS TG TCP62 LUs. This also means you cannot use the
dynamic LU name generation function in the CICS TG, since you will be
unable to know the names of your LUs in VTAM. In our example the following
definitions would suffice:
APTCP0C VBUILD TYPE=CDRSC
CCLI62LU CDRSC ALSLIST=TCP01PU
For further details on configuring CDRSC definitions for LU 6.2, refer to
AnyNet SNA over TCP/IP, SC31-8578.
Chapter 3. TCP62 connections to CICS 45