gtpa1m08 | ACF/SNA Network Generation |
This publication describes how you define the SNA network to which the TPF system will connect. To define the SNA network, do the following:
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:
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:
To define the TPNT tables, use the ITPNT macro as described in TPF General Macros.
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.