High Availability Monitors Version A.03.02 Release Notes

NOF API Verbs (ACTIVATE_SESSION to OPEN_FILE)
APING
Chapter 3 135
The lu_name parameter did not match any defined LU
name.
AP_BAD_SECURITY
The security parameter was not set to a valid value.
AP_UNKNOWN_PARTNER_MODE
The value specified for plu_alias , fqplu_name , or
mode_name did not match any defined partner LU or
mode.
AP_BAD_PARTNER_LU_ALIAS
The value specified for plu_alias did not match any
defined partner LU.
Appendix A, “Common Return Codes,” lists further secondary return
codes associated with AP_PARAMETER_CHECK, which are common to all
NOF verbs.
Returned Parameters: Allocation Failure
If the verb does not execute because SNAplus2 cannot allocate the APPC
conversation, SNAplus2 returns the following parameters:
primary_rc AP_ALLOCATION_ERROR
secondary_rc Possible values are:
AP_ALLOCATION_FAILURE_NO_RETRY
The conversation cannot be allocated because of a
permanent condition, such as a configuration error or
session protocol error. Check the sense_data
parameter and the error log file for more information.
Do not attempt to retry the APING verb until the error
has been corrected.
AP_ALLOCATION_FAILURE_RETRY
The conversation could not be allocated because of a
temporary condition, such as a link failure. Check the
error log file for more information. Retry the APING
verb, preferably after a timeout to allow the condition
to clear.
AP_SECURITY_NOT_VALID