High Availability Monitors Version A.03.02 Release Notes

NOF API Verbs (ACTIVATE_SESSION to OPEN_FILE)
DEFINE_PARTNER_LU
Chapter 3 329
DEFINE_PARTNER_LU
The DEFINE_PARTNER_LU verb defines the parameters of a partner
LU for LU-LU sessions between a local LU and the partner LU, or
modifies an existing partner LU. You cannot change the partner LU alias
of an existing partner LU.
There is normally no requirement to define partner LUs, because
SNAplus2 will set up an implicit definition when the session to the
partner LU is established; you should only need to define the LU if you
need to enforce non-default values for logical record size, conversation
security support, or parallel session support. You may also have an
APPC application that uses a partner LU alias when allocating a
session, therefore you need to define a partner LU in order to map the
alias to a fully-qualified partner LU name.
If the local node or the remote node (where the partner LU is located) is a
LEN node, note that you need to define a directory entry for the partner
LU to allow SNAplus2 to access it. This can be done using either
DEFINE_ADJACENT_LEN_NODE or DEFINE_DIRECTORY_ENTRY.
If each of the two nodes is either an end node or network node, the
directory entry is not required, because SNAplus2 can locate the LU
dynamically.
VCB Structure
typedef struct define_partner_lu
{
AP_UINT16 opcode; /* verb operation code */
unsigned char reserv2; /* reserved */
unsigned char format; /* reserved */
AP_UINT16 primary_rc; /* primary return code */
AP_UINT32 secondary_rc; /* secondary return code */
PLU_CHARS plu_chars; /* partner LU characteristics */
} DEFINE_PARTNER_LU;
typedef struct plu_chars
{
unsigned char fqplu_name[17]; /* fully qualified partner LU name */
unsigned char plu_alias[8]; /* partner LU alias */
unsigned char description[32]; /* resource description */
unsigned char reserv2[16]; /* reserved */