APN Configuration and Management Manual

SNAX/APN Advanced Program-to-Program

Communication (APPC)

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

6-6

SNAX/APN APPC Using an X.25 PVC

SNAX/APN supports X.25 PVC connections (but not SVCs).

Figure 6-4 on page 6-7 shows an example of a SNAX/APN LEN node using an X.25

PVC. The SCF configuration, shown alongside, configures the X25AM LINE and SU

object (representing a PVC) and the SNAX/XF SUBSYS, LINE, PU, and LU objects.

Notes.

1. The SUBSYS object must be configured with a SNANETID value, identifying the SNA

network that the NonStop node is in.

2. The LINE object always represents a connection between the NonStop node and adjacent

2.1 nodes.

3. SDLC lines can be configured with STATION PRIMARY, SECONDARY, or NEGOTIABLE

(allowing the LUs to negotiate which is the primary link station at session establishment).

NEGOTIABLE requires MAXPUS be set to 1.

4. Remote PU objects represent adjacent 2.1 nodes (one per line for point-to-point lines,

more for multipoint lines) for LEN. For end node, the remote PU is the Network Node

Server.

5. Remote PU objects can be configured with DYNAMIC ON or OFF, determining whether

SNAX/APN can dynamically add remote LU objects when LUs in that node send a BIND

request. DYNAMIC ON simplifies the SNAX/APN configuration for LU accept.

6. Remote PU objects can be configured with CPNAME and SNANETID values if XID

validation is required (see XID Validation

on page 6-2). This example assumes the partner

node parameters RMTCPNAME and RMTNETID have the value NONE so that both nodes

will accept each others XID3 frames.

7. Remote LU objects represent either LUs in adjacent 2.1 nodes or LUs accessible through

an adjacent network node server (whether in the network node’s APPN network or a

connected APPN network). These definitions are optional with end node.

8. A local PU object named #ZNT21 (representing the NonStop node) is not configured

through SCF but is created automatically (provided the LINE object has MAXLOCALLUS

non-zero).

9. Local LU objects represent the LUs on the HP NonStop system. If using SNAX/APC, these

are also configured as SNAX/APC LU objects and opened by SNAX/APC.

10. Local LU objects must have PUNAME #ZNT21 (the default, identifying the unconfigured

local PU).

11. The local LU (LLU1) can engage in parallel sessions but can initiate sessions with only

with one remote LU (RLU1).