APN Configuration and Management Manual

Expand over SNAX/APN Lines

SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006

8-3

Configuring Expand

You must configure Expand to point to the SNAX/APN LINE and local LU object; for

example, by the SCF command:

ALTER LINE $LHDEV, ASSOCIATEDEV $SNAPA, ASSOCIATESUBDEV #LLUA

For details of the SCF attributes for Expand, see the SCF Reference Manual for

Expand.

Configuring the SNA Network

Certain parameters in the SNA network must be configured compatibly with the

SNAX/APN parameters. Table 8-1 shows the correspondences between the NCP and

VTAM parameters in the SNA subarea attaching system \A

Notes. The following apply to local LU object attributes:

1. PROTOCOL NAM is required.

2. The local LU SNANAME on system \A must match the remote LU SNANAME on system

\B (and vice versa).

3. If the local LU is to initiate sessions, DLUNAME must be defined (matching the last part of

the remote LU object name). If the remote PU has DYNAMIC ON, remote LUs will always

be able to initiate sessions. However, DLUNAME must be specified in one of the two

systems for the connection to become active.

4. POLLINT should be set to the minimum value on SDLC lines for best performance.

5. For details of the SCF attributes for SNAX/APN, see the SCF Reference Manual for

SNAX/XF and SNAX/APN.

Table 8-1. Correspondences Between SNA Subarea Network and

SNAX/APN (page 1 of 2)

SNA Network Value SNAX/APN Value

LU name in NCP major node defining

system \A

Local LU SNANAME on system \A

CDRSC name in VTAM CDRSC major node

defining system \B

Remote LU SNANAME on system \A