SNAX/XF and SNAX/APN Configuration and Management Manual

Configuring for Token-Ring Support
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
9-27
Notes
Step Four: Start the MSAP Object
When PAM is started, the MSAP.#SNATR object is added automatically. By default
(MSAPSTARTUP) the object is also brought up in a STARTED state. If you specified
MSAPSTARTDOWN in the RUN command you must start the MSAP object.
START MSAP $PAM1.#SNATR
Notes
1. The PAM process must run in the same CPUs as the SLSA subsystem because
both are clients of the QIO subsystem that controls access to ServerNet.
2. The example does not show the configuration of a PORT object because SNAX
doesn’t use the port interface.
Step Three: SNAX Configuration
Background
At the SNAX level you choose SNAX/XF for legacy-style, sub-area communications or
SNAX/APN for peer-to-peer communication.
This example uses SNAX/APN. The product allows parallel sessions within a single
LU-LU connection and dynamic configuration of the remote LU.
The example shows the configuration of the following SNAX SCF objects; LINE, PU
and LU.
Related Manuals

None. All the information you need should be in this manual.
Example Configuration
Step One: Add the SNAX Profiles
Your first command sends all subsequent commands to the WAN subsystem. The file
PSX1SVM is the service manager profile, PSX1TS is the line handler profile.
ASSUME SUBSYS $ZZWAN
ADD PROFILE $ZZWAN.#SMPROF, FILE $SYSTEM.[sysnn].PSX1SVM
ADD PROFILE $ZZWAN.#TSPROF, FILE $SYSTEM.[sysnn].PSX1TS