HP-UX SNAplus2 R7 NOF Programmer's Guide
NOF API Verbs
CHANGE_SESSION_LIMIT
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_RESPONSIBLE
The responsible parameter was not set to a valid value.
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.5.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_RESET
No sessions are currently active for this LU-LU-mode combination. Use INITIAL-
IZE_SESSION_LIMIT instead of CHANGE_SESSION_LIMIT to specify the limits.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_STATE_CHECK, which
are common to all NOF verbs.
3.5.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.
sense_data
The SNA sense data associated with the allocation failure.
3.5.7 Returned Parameters: CNOS Processing Errors
If the verb does not execute because of an error, SNAplus2 returns the following parameters.
96