HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
DEFINE_LOCAL_LU
3.28.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
Possible values are:
AP_INVALID_LU_NAME
The lu_name or lu_alias parameter contained a character that was not valid.
AP_LU_ALREADY_DEFINED
An LU with this name has already been defined. You cannot use this verb to modify any parameters
of an existing LU except the attach routing data.
AP_PU_NOT_DEFINED
The pu_name parameter did not match any defined PU name.
AP_SECURITY_LIST_NOT_DEFINED
The security_list_name parameter did not match any defined security access list name.
AP_LU_ALIAS_ALREADY_USED
An LU with this alias has already been defined. You cannot use this verb to modify any parameters of
an existing LU except the attach routing data.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_STATE_CHECK, which
are common to all NOF verbs.
3.28.6 Returned Parameters: Other Conditions
Appendix B, Common Return Codes lists further combinations of primary and secondary return codes that are
common to all NOF verbs.
3.28.7 Default LUs
You can set up the configuration of local LUs so that applications do not have to specify an LU name explicitly
when starting a conversation; the node will select a suitable default LU for the application to use. The method
for doing this depends on whether the applications require dependent or independent LUs, as follows. You cannot
provide this facility for both dependent and independent LUs.
• If the applications require dependent LUs, use the default_pool parameter on DEFINE_LOCAL_LU for one or
more dependent LUs, to specify that they can be used as default LUs. When an application attempts to start a
conversation without specifying a local LU name, SNAplus2 will select an unused LU from the pool of LUs
defined as default LUs.
• You can define LUs on more than one node as default LUs. An application requesting a default LU may be
assigned to any of these LUs as available; there is no requirement for the LU to be on the same computer as
the application. However, if you are defining partner LUs for the applications, these must be defined on all
nodes where default LUs are defined (so that the application can contact the correct partner LU using any of
the default local LUs).
• If the applications require independent LUs, do not use the default_pool parameter to define any local LUs as
default LUs. In this case, an application requesting a default LU will be assigned to the LU associated with a
local node’s CP (this is an independent LU automatically defined by SNAplus2 for each node).
166