HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
INITIALIZE_SESSION_LIMIT
secondary_rc
Possible values are:
AP_EXCEEDS_MAX_ALLOWED
The plu_mode_session_limit, min_conwinners_source, min_conwinners_target,orauto_act parameter
was set to a value outside the valid range.
AP_CANT_CHANGE_TO_ZERO
The plu_mode_session_limit parameter cannot be set to zero using this verb; use RE-
SET_SESSION_LIMIT instead.
AP_INVALID_LU_ALIAS
The lu_alias parameter did not match any defined local LU alias.
AP_INVALID_LU_NAME
The lu_name parameter did not match any defined local LU name.
AP_INVALID_MODE_NAME
The mode_name parameter did not match any defined mode name.
AP_INVALID_PLU_NAME
The fqplu_name parameter did not match any defined partner LU name.
AP_INVALID_SET_NEGOTIABLE
The set_negotiable parameter was not set to a valid value.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_PARAMETER_CHECK,
which are common to all NOF verbs.
3.84.5 Returned Parameters: State Check
If the verb does not execute because of a state error, SNAplus2 returns the following parameters.
primary_rc
AP_STATE_CHECK
secondary_rc
AP_MODE_NOT_RESET
One or more sessions are currently active for this LU-LU-mode combination. Use
CHANGE_SESSION_LIMIT instead of INITIALIZE_SESSION_LIMIT to specify the lim-
its.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_STATE_CHECK, which
are common to all NOF verbs.
3.84.6 Returned Parameters: Session Allocation Error
If the verb does not execute because of a session allocation error, SNAplus2 returns the following parameters:
primary_rc
AP_ALLOCATION_ERROR
secondary_rc
AP_ALLOCATION_FAILURE_NO_RETRY
A session could not be allocated because of a condition that requires corrective action. Check the
sense_data parameter and any logged messages to determine the reason for the failure, and take any
action required. Do not attempt to retry the verb until the condition has been corrected.
325