High Availability Monitors Version A.03.02 Release Notes

NOF API Verbs (ACTIVATE_SESSION to OPEN_FILE)
DEFINE_DIRECTORY_ENTRY
Chapter 3 195
DEFINE_DIRECTORY_ENTRY
DEFINE_DIRECTORY_ENTRY defines a new entry in the node
directory database. This verb cannot be used to modify existing entries.
The verb provides a network qualified resource name along with a
resource type (network node, end node, LU or Wildcard).
When defining an adjacent node and its LUs, you are recommended to
use DEFINE_ADJACENT_LEN_NODE instead of
DEFINE_DIRECTORY_ENTRY. This allows you to define the node and
its LUs with a single verb. (DEFINE_DIRECTORY_ENTRY defines only
a single entry, so you need to use multiple verbs to define entries for the
adjacent node and for its LUs.)
Because the database is hierarchical, each entry includes the name of
the parent resource; for an LU the parent resource is the owning Control
Point, and for an end node or LEN node it is the network node server.
However, when DEFINE_DIRECTORY_ENTRY is used on an end node
or LEN node to define an adjacent LEN node resource with which it
communicates directly, the entry does not include a parent resource
name.
You can specify a “wildcard” LU name to match multiple LU names, by
specifying only the initial characters of the name. For example, the
wildcard LU name APPN.LU will match APPN.LUNAME or
APPN.LU01 (but will not match APPN.NAMELU).
VCB Structure
typedef struct define_directory_entry
{
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 */
unsigned char resource_name[17]; /* network qualified resource name */
unsigned char reserv1a; /* reserved */
AP_UINT16 resource_type; /* resource type */
unsigned char description[32]; /* resource description */
unsigned char reserv3[16]; /* reserved */
unsigned char parent_name[17]; /* fully qualified parent name */
unsigned char reserv1b; /* reserved */