SNAX/APN Application Programming Manual

The SNALU Interface
SNAX/APN Application Programming Manual—420111-001
4-16
SNALU Application Initiates Session With Remote
PLU
SNAX/APN supports all three formats. For a full description of all three INIT-SELF
formats, see the IBM Systems Network Architecture: Format and Protocol Reference:
Architectural Logic manual. If you want to include structured user data in the INIT-
SELF request, refer to the description of user data subfields in that manual.
Note that the character-coded fields in the INIT-SELF request should be in EBCDIC
code for interpretation by the PLU program.
Character-Coded Logon Requests
The SNAX/APN SNALU interface requires that the LOGON command format shown
below is used for the character-coded logon request to succeed. LOGON requests of
other formats will result in a negative response being returned to the application.
pluname
indicates the name of the PLU you want to logon to
bindname
indicates a BIND table entry
userdata
indicates data supplied by the user
Figure 4-5. Formats for INIT-SELF Requests
LOGON APPLID pluname [ LOGMODE bindname ] [ DATA userdata ]
405CDT .CDD
Supplies the name
of an entry in a
logon mode table
on the host. The
specified entry is
used to select a
BIND image. The
BIND image is then
passed by the host
SSCP to the PLU
in a CINIT request.
Allows the SLU to
specify the following:
o Queuing information
o An initiate origin
o NOTIFY
specifications
o A User Request
Correlation Identifier
Allows the SLU to
specify a class of
service (COS)
identifier
Format 0
Format 1
Format 2
Format Type Parameters for Each Function