SNAX/APC Configuration and Management Manual

Planning for SNAX/APC

SNAX/APC Configuration and Management Manual—138787

2-5

Tandem Access Method Configuration

Three SNA access methods may be used on the Tandem system:

•

SNAX/XF

•

SNAX/APN

•

SNAX/CDF

Your choice of method(s) will be largely determined by the existing SNA network with

which you want to connect. However, support for parallel sessions and full support for

dynamic partner LU/mode configuration is limited to SNAX/APN configurations.

SNAX/XF

SNAX/XF is configured using the Subsystem Control Facility (SCF). SNAX/XF does

not support parallel sessions. SNAX/XF supports dynamic configuration of the partner

LU and partner mode, but a line must be pre-defined to the remote PU.

Refer to the SNAX/XF Configuration and Control Manual (K-Series), or SNAX/XF and

SNAX/APN Configuration Manual (S-Series) for further details.

SNAX/APN

SNAX/APN allows LUs on a Tandem system to communicate with LUs in adjacent type

2.1 nodes, advanced peer-to-peer networking (APPN) nodes, and subarea networks.

SNAX/APN, unlike SNAX/XF, offers negotiable link stations: that is, the

primary/secondary relationship may be dynamically configured at connect time, based

on data swapped in the XID exchange. This feature can only be used on a point-to-point

line where there is only one PU added. In a multipoint connection, the Tandem node

must be explicitly configured as a primary or secondary link station.

For a more detailed discussion of LENs and end nodes, refer to SNAX/XF Configuration

and Control Manual (K-Series), or SNAX/XF and SNAX/APN Configuration Manual (S-

Series) for further details.

Type 2.1 node operations require that you configure:

•

Local LU objects. These LUs provide 6.2 resources for the local TPs, typically

running on the local Tandem system.

•

Remote LU objects. These LUs provide 6.2 resources for the remote TPs, the

transaction programs elsewhere in the network—typically running on IBM systems

(although Tandem-to-Tandem LU 6.2 traffic is allowed). If you have enabled

dynamic support in the local LU, the remote LUs do not have to be pre-defined,

neither do the corresponding modes.

Note. The SNAX/XF lines and LUs used by SNAX/APC sessions must be configured with

CHARACTERSET ASCII. LU 6.2 protocols require the use of bit-oriented data for FM headers,

logical record lengths, and GDS variables. If these messages are translated into EBCDIC

(using the EBCDIC option), they will produce incorrect results.