CICS and VTAM Configuration

In this section:

These topics provide the setup and communications configuration information the adapter requires to communicate with NATURAL CICS Transactions.

After you configure any VTAM definitions, the major nodes they describe need to be started in the VTAM system. If you are using AnyNET, it should be tested from the Adapter for NATURAL CICS Transactions platform.


Top of page

x
AnyNET VTAM Definitions

The AnyNET product requires three major VTAM nodes for its operation. The main node for AnyNET identifies the port. The following are examples of the three nodes. Replace relevant parameters with your site specific values.



Example: Setting Up the Major Node for the AnyNET Listener
**********  TCP62 MAJOR NODE DEFINITION FOR ANYNET
TCP62   VBUILD TYPE=TCP,DNSUFX=IBI.COM,PORT=397
TCP62G  GROUP  ISTATUS=ACTIVE
TCP62L  LINE   ISTATUS=ACTIVE
TCP62P  PU     ISTATUS=ACTIVE,NETID=MYNET

Note: Port 397 is used in this example. On UNIX, using a port number above 1000 is recommended due to the root privileges associated with using a port number under 1000. On z/OS, 397 is the default port; it is well established and frequently used.

Keep in mind, however, that the port you use must be the same on UNIX and z/OS. For example, if 1000 is specified on one platform, it must also be specified on the other.



Example: Setting Up the Major Node for Cross Domain Resources

If CDRDYN=YES is not specified in the ATCSTR00 VTAM startup parameter file, then the name of the machine that the Transaction Adapter is running on needs to be coded in the follow node:

        VBUILD TYPE=CDRSC
CDRSC62 NETWORK NETID=MYNET
CDRSC62 GROUP
EDABGR2 CDRSC ALSLIST=TCP62P

Note: EDABGR2 is the machine name on which the server is running. The machine name must be limited to eight bytes.



Example: Setting Up the Standard VTAM LU Definitions
        VBUILD TYPE=SWNET
MYNAMEPU  PU   ADDR=01,IDBLK=05D,IDNUM=10101,                 X
               MAXPATH=3,                                     X
               PUTYPE=2,                                      X
               MODETAB=MTOS2EE,                               X
               DLOGMOD=PARALLEL,                              X
               ISTATUS=ACTIVE
MYLUNAME  LU   LOCADDR=2

Top of page

x
LU6.2 VTAM Definitions

LU6.2 requires two major VTAM nodes for its operation. The main node for AnyNET identifies the port. The following are examples of these two nodes. Replace relevant parameters with your site specific values.



Example: Setting Up the Major Node for the AnyNET Listener
**********  TCP62 MAJOR NODE DEFINITION FOR ANYNET
TCP62   VBUILD TYPE=TCP,DNSUFX=IBI.COM,PORT=397
TCP62G  GROUP  ISTATUS=ACTIVE
TCP62L  LINE   ISTATUS=ACTIVE
TCP62P  PU     ISTATUS=ACTIVE,NETID=MYNET

Note: Port 397 is used in this example. On UNIX, using a port number above 1000 is recommended due to the root privileges associated with using a port number under 1000. On z/OS, 397 is the default port; it is well established and frequently used.

Keep in mind, however, that the port you use must be the same on UNIX and z/OS. For example, if 1000 is specified on one platform, it must also be specified on the other.



Example: Setting Up the Standard VTAM LU Definitions
        VBUILD TYPE=SWNET
MYNAMEPU  PU   ADDR=01,IDBLK=05D,IDNUM=10101,                 X
               MAXPATH=3,                                     X
               PUTYPE=2,                                      X
               MODETAB=MTOS2EE,                               X
               DLOGMOD=PARALLEL,                              X
               ISTATUS=ACTIVE
MYLUNAME  LU   LOCADDR=2

Top of page

x
CICS Connection and Sessions for Microsoft Windows and UNIX

For the Adapter for NATURAL CICS Transactions to be able to connect to NATURAL CICS Transactions (for both TCP62 and LU6.2 where supported), Connection and Session definitions are required. The definitions are dependent on the platform on which the adapter is running.

If you deploy the adapter on Microsoft Windows or UNIX, the connection and sessions definitions described in Using the CEDA View Connection Command and Using the CEDA View Sessions Command are required.

Note: For DPL program execution, all users must be able to access and run transaction CPMI (the mirror transaction).



Example: Using the CEDA View Connection Command

The following is an example of a CEDA view connection command that illustrates what is required:

CEDA  View Connection(  MYLU )
   Connection    :  MYLU
   Netname       :  MYLUNAME
   ACcessmethod  :  Vtam           Vtam | IRc | INdirect | Xm
   PRotocol      :  Appc           Appc | Lu61 | Exci
   SInglesess    :  No             No | Yes
   DAtastream    :  User           User | 3270 | SCs | STrfield | Lms
   INService     :  Yes            Yes | No
   ATtachsec     :  Verify         Local | Identify | Verify | Persistent


Example: Using the CEDA View Sessions Command

The following is an example of a CEDA view sessions command that illustrates what is required:

CEDA View Sessions(  MYLUNAME )
   Sessions      :  MYLUNAME
   Connection    :  MYLU
   MOdename      :  PARALLEL
   Protocol      :  Appc                Appc | Lu61 |
   MAximum       :  008 , 000           0-999

The MAximum parameter determines the number of concurrent sessions available to process requests. Its first value should be in the range of 4 - 255, and the second one should always be set to zero.

Note: Log mode must support parallel sessions.


iWay Software