HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_ALLOCATE and ALLOCATE
• Special characters $, #, and @
The first character in the string must be an uppercase letter, or can be # for one of the SNA-defined modes
such as #INTER. For information about SNA-defined modes, see the HP-UX SNAplus2 Administration Guide.
If the mode name is fewer than eight characters long, pad it on the right with EBCDIC blanks (
0x40).
A mode name can also be all EBCDIC blanks (0x40).
In a mapped conversation, the name cannot be SNASVCMG (a reserved mode name used internally by
APPC). Using this name in a basic conversation is not recommended.
If the specified mode name does not match either an SNA-defined mode or a mode defined in the SNAplus2
configuration, SNAplus2 creates a new mode based on the default specified in the configuration (or on the
SNA-defined mode with a blank mode name, if no default mode is defined).
tp_name
Name of the invoked TP.
The value of tp_name specified by the [MC_]ALLOCATE verb in the invoking TP must match the value of
tp_name specified by the RECEIVE_ALLOCATE verb in the invoked TP.
This parameter is a 64-byte EBCDIC character string; it is case-sensitive. The tp_name parameter normally
consists of characters from the type-AE EBCDIC character set (except when naming a service TP). These
characters are as follows:
• Uppercase and lowercase letters
• Numerals 0–9
• Special characters $, #, @, and period (.)
If the TP name is fewer than 64 bytes, use EBCDIC blanks (0x40) to pad it on the right.
The SNA convention for naming a service TP is an exception to the above; the name consists of up to four
characters, of which the first character is a hexadecimal byte between 0x00 and 0x3F. The other characters
are from the EBCDIC AE character set.
security
Specifies the information the partner LU requires in order to validate access to the invoked TP.
Based on the conversation security established for the invoked TP during configuration, use one of the
following values:
AP_NONE
The invoked TP does not use conversation security. (If you use this value, the invoked TP must be
configured not to use conversation security.)
AP_PGM
The invoked TP uses conversation security and thus requires a user ID and password. Supply this
information through the user_id and pwd parameters.
AP_PGM_STRONG
The invoked TP uses conversation security and thus requires a user ID and password. In addition,
setting AP_PGM_STRONG stipulates that SNAplus2 encrypts the password when sending it across the
network. Supply the user ID and password through the user_id and pwd parameters.
AP_SAME
Use this value when your TP was invoked by another TP, using a valid user ID and password, and is
now invoking a third TP that also requires conversation security. (The situation in which one TP invokes
a second TP which then invokes a third TP is illustrated in Section 1.1.9, Multiple Conversations.) This
value tells the third TP (the invoked TP) that conversation security has already been verified for the
first invoking TP.
113