High Availability Monitors Version A.03.02 Release Notes

NOF API Verbs (ACTIVATE_SESSION to OPEN_FILE)
APING
Chapter 3136
The user ID or password specified was not accepted by
the partner LU.
AP_TP_NAME_NOT_RECOGNIZED
The partner LU does not recognize the specified TP
name.
AP_TRANS_PGM_NOT_AVAIL_NO_RETRY
The remote LU rejected the allocation request because
it was unable to start the requested partner TP. The
condition is permanent. The reason for the error may
be logged on the remote node. Do not retry the APING
verb until the cause of the error has been corrected.
AP_TRANS_PGM_NOT_AVAIL_RETRY
The remote LU rejected the allocation request because
it was unable to start the requested partner TP. The
condition may be temporary, such as a timeout. The
reason for the error may be logged on the remote node.
Retry the APING verb, preferably after a timeout to
allow the condition to clear.
sense_data If the secondary_rc parameter is
AP_ALLOCATION_FAILURE_NO_RETRY, this parameter
contains the SNA sense data associated with the error.
For all other secondary_rc values, this parameter is
reserved.
Returned Parameters: Conversation Failure
If the verb does not execute because the APPC conversation with the
partner TP failed, SNAplus2 returns the following parameters:
primary_rc AP_CONV_FAILURE_NO_RETRY
The conversation was terminated because of a
permanent condition, such as a session protocol error.
Check the error log file to determine the cause of the
error. Do not retry the APING verb until the error has
been corrected.
primary_rc AP_CONV_FAILURE_RETRY
The conversation was terminated because of a
temporary error. Retry the APING verb. If the problem