High Availability Monitors Version A.03.02 Release Notes

NOF API Verbs (QUERY Verbs)
QUERY_PARTNER_LU
Chapter 4 853
conversation. The specific types of conversation
security support are described by the following values.
AP_ALREADY_VERIFIED
Both the local and partner LU agree to accept Already
Verified requests to allocate a conversation. An Already
Verified request needs to carry only a user ID. It does
not need to carry a password.
AP_PERSISTENT_VERIFICATION
Persistent Verification is supported on the session
between the local and partner LUs. Once the initial
request (carrying a user ID and usually a password) for
a conversation has been verified, subsequent requests
for a conversation need to carry only the user ID.
AP_PASSWORD_SUBSTITUTION
The local and partner LU support Password
Substitution conversation security. When a request to
allocate a conversation is issued, the request carries an
encrypted form of the password. If Password
Substitution is not supported, the password is carried
in clear text (nonencrypted) format. If the session does
not support Password Substitution, an Allocate or
Send_Conversation with security type set to
AP_PGM_STRONG will fail.
plu_detail.duplex_support
Returns the conversation duplex support as negotiated
on the BIND. Possible values are:
AP_HALF_DUPLEX
Only half-duplex conversations are supported.
AP_FULL_DUPLEX
Both full-duplex and half-duplex sessions are
supported. Expedited data is also supported.
AP_UNKNOWN
The conversation duplex support is not known because
no sessions are active with the partner LU.
preference