SNAX Creator-2 Configuration and Control Manual

Configuring SNAX Creator-2 With SNAX/APN
D–2 117143 SNAX Creator-2 Configuration and Control Manual
Table D-1 shows configuration details in the SNA subarea network. Naming
correspondences are indicated by highlighting.
Table D-1. Configuration Details in the SNA Subarea Network
Description VTAM List ILOGMGR Control File NCP Definition
ILOGMGR ibm1 APPL ACBNAME=ibm1
,AUTH=(ACQ)
ILOGMGR=ibm1
Line to Tandem node ln1 LINE …
Tandem node pu1 PU
PUTYPE=2
,XID=YES …
SNAX/APN logon manager TLOGMGR=tn tn LU
LOCADDR=0
Pathway application; user types
LOGON APPLID(mypath) mypath APPL ACBNAME=mypath TDMAPPLS=(mypath)
TACL application; user types
LOGON APPLID(mytacl) mytacl APPL ACBNAME=mytacl TDMAPPLS=(mytacl)
Server application; user types
LOGON APPLID(myprog) myprog APPL ACBNAME=myprog TDMAPPLS=(myprog)
At the Tandem system, the SNAX/APN logon manager forwards the request to the
associated SNAX Creator-2 subsystem. Table D-1 shows configuration details on the
Tandem system. Naming correspondences are again indicated by highlighting.
Notes for Table D-2:
1. $CREA is the manager name of the SNAX Creator-2 subsystem through which the
commands are issued.
2. $SSCP is the name of the SNAX/APN service manager, and \node is the system
on which it is running.
3. On the SU attribute:
NAMERULE is omitted, defaulting to PLUNAMEONLY (FIRSTWORD adds
complexity to no advantage) and PLUNAME is omitted (simplifying the
configuration).
As a result, APPL objects are named C- pluname , where pluname is the PLU
name in the logon request forwarded by SNAX/APN.
PASSWORD is optional, but, if used, it must match the value for the SNAX/APN
APPL.
4. The server message typically includes the logon terminal name (in the example,
provided by the [#OPENNAME] built-in function) and the application object file
(in the example, $disk.subvol.obj).