High Availability Monitors Version A.03.02 Release Notes

NOF API Verbs (ACTIVATE_SESSION to OPEN_FILE)
DEFINE_LOCAL_LU
Chapter 3 253
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_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 A, “Common Return Codes,” lists further secondary return
codes associated with AP_STATE_CHECK, which are common to all NOF
verbs.
Returned Parameters: Other Conditions
Appendix A, “Common Return Codes,” lists further combinations of
primary and secondary return codes that are common to all NOF verbs.
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