HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
QUERY_DIRECTORY_LU
The resource is not within the domain of the local node.
directory_lu_detail.entry_type
Specifies the type of the resource. This is one of the following:
AP_HOME
Local resource.
AP_CACHE
Cached entry.
AP_REGISTER
Registered resource (NN only).
directory_lu_detail.wild_card
Specifies whether the LU entry is for an explicit name, or for a wildcard value that will match a range of
names. This is one of the following:
AP_EXPLICIT
The entry is an explicit LU name.
AP_FULL_WILDCARD
The entry is a full wildcard value that will match any LU name.
AP_PARTIAL_WILDCARD
The entry is a partial wildcard; the nonblank characters in the name will be used to match against an
LU name.
AP_OTHER
Unknown type of LU entry.
directory_lu_detail.apparent_lu_owner_name
This parameter applies only if the local node is a Network Node or a Branch Network Node; it is reserved
otherwise.
If the apparent owning CP of this LU is not the real owning CP, this parameter specifies the fully qualified
name of the apparent owning CP; otherwise it is reserved. For example, if the resource is owned by an End
Node in the domain of a Branch Network Node (BrNN), the directory of this BrNN’s Network Node Server
includes the BrNN as the apparent owner, but the real owning CP is the End Node.
The name is a 17-byte EBCDIC string, padded on the right with EBCDIC spaces. It consists of a network ID
of 1–8 A-string characters, an EBCDIC dot (period) character, and a network name of 1–8 A-string characters.
3.108.4 Returned Parameters: Parameter Check
If the verb does not execute because of a parameter error, SNAplus2 returns the following parameters:
primary_rc
AP_PARAMETER_CHECK
secondary_rc
Possible values are:
AP_INVALID_LU_NAME
The list_options parameter was set to AP_LIST_INCLUSIVE, to list all entries starting from the
supplied name, but the lu_name parameter was not valid.
AP_INVALID_LIST_OPTION
401