gtpa1m08ACF/SNA Network Generation

SNA Network Definition

This publication describes how you define the SNA network to which the TPF system will connect. To define the SNA network, do the following:

  1. Update and assemble the SNA keypoint (CTK2), which uses the SNAKEY macro to describe the SNA network.
  2. Define the appropriate SNA resources to the TPF system by preparing the input definition statements and running the offline ACF/SNA table generation (OSTG) program to create the SNA pilot tape or general data set (GDS).

The process for each of these steps is described in this publication.

In general, the SNA keypoint (CTK2, data macro CK2SN) contains global information that is used by the TPF system to set up the operating environment. This information is defined using the SNAKEY macro, and includes such things as:

For more information about the SNAKEY macro, see Updating and Assembling the SNA Keypoint.

You can use the OSTG program to define the SNA resources to the TPF system. These resources include:

Note:
You can also use dynamic LU support and the ZNDYN ADD command to define ALS, CDRM, CTC, NCP, and remote LU resources to the TPF system. See TPF ACF/SNA Data Communications Reference for more information about dynamic LU support and defining resources to the TPF system.

The SNA network is typically owned and managed by VTAM, which is an IBM program product. The TPF system, therefore, has no need to know about the network topology. The TPF system does, however, need to know (through the OSTG program, ZNDYN ADD command, or dynamic LU support) about channel-attached NCP resources and the LU resources that will be in session with TPF applications. This means that you do not need to define the physical network (LINEs or PUs) to the TPF system.

Process selection vectors (PSVs) can be associated for some LUs using the OSTG program. Additional information about PSVs can be found in the TPF ACF/SNA Data Communications Reference. PSVs are defined in segment COBU using the IPSVE and IPSVT macros. For more information about the IPSVE and IPSVT macros, see TPF General Macros.

If you are running TPF Advanced Program-to-Program Communications (TPF/APPC) support, you must define the local TPF transaction programs that are activated by either the remote transaction programs, the TPF/APPC ACTIVATE_ON_CONFIRMATION verb, or the TPF/APPC ACTIVATE_ON_RECEIPT verb to the TPF system in the transaction program name table (TPNT). The TPNT resides in a user-replaceable program segment (CHQ0), and contains the following:

  1. The transaction program name carried in the ATTACH message received from a remote LU 6.2 node, or issued on the TPF/APPC ACTIVATE_ON_CONFIRMATION verb or the TPF/APPC ACTIVATE_ON_RECEIPT verb.
  2. The associated TPF E-type program segment that provides the application function.

To define the TPNT tables, use the ITPNT macro as described in TPF General Macros.

Note:
To use TPF/APPC in a loosely coupled complex, you may need to add 2 entries to the TPNT for the service transaction program. See the progam considerations for the ITPNT macro for more information about these entries.

Any TPF program defined in the TPNT that is activated by a remote transaction program must be designed and implemented to accept the ATTACH interface. For more information about this interface, see TPF ACF/SNA Data Communications Reference.