HP-UX SNAplus2 R7 NOF Programmer's Guide
NOF API Verbs
DEFINE_INTERNAL_PU
A null-terminated text string (0–31 characters followed by a null character) describing the internal PU.
This string is for information only; it is stored in the node’s configuration file and returned on the
QUERY_DLUR_PU and QUERY_PU verbs, but SNAplus2 does not make any other use of it.
def_data.initially_active
Specifies whether this internal PU is automatically started when the node is started. Possible values are:
AP_YES
The PU is automatically started when the node is started.
AP_NO
The PU is not automatically started; it must be started manually.
def_data.dlus_name
Name of DLUS node which DLUR will use when it initiates SSCP-PU activation. The name is a 17-byte
EBCDIC string, right-padded with EBCDIC spaces. It consists of a network ID of up to 8 A-string characters,
an EBCDIC dot (period) character, and a network name of up to 8 A-string characters.
To indicate that DLUR should use the global default DLUS, set this parameter to 17 binary zeros. In this
case, you must also use DEFINE_DLUR_DEFAULTS to define the global default DLUS.
def_data.bkup_dlus_name
Name of DLUS node which will serve as the backup DLUS for this PU. The name is a 17-byte EBCDIC
string, right-padded with EBCDIC spaces. It consists of a network ID of up to 8 A-string characters, an
EBCDIC dot (period) character, and a network name of up to 8 A-string characters.
To indicate that DLUR should use the global backup default DLUS, set this parameter to 17 binary zeros. In
this case, you must also use DEFINE_DLUR_DEFAULTS to define the global backup default DLUS.
def_data.pu_id
PU identifier. This is a 4-byte hexadecimal string, consisting of a block number (3 hexadecimal digits) and a
node number (5 hexadecimal digits). The PU ID should match the
pu_id configured at the host. (SNAplus2
sends both the PU name and PU ID to the host to identify the PU. The host normally identifies the PU by its
PU name, or by the PU ID if it cannot find a matching PU name.)
def_data.dlus_retry_timeout
Reactivation timer for contacting a DLUS. If SNAplus2 fails to contact the DLUS, this parameter specifies
the time in seconds between retries. The interval between the first and second attempts is always 1 second.
Specify a value in the range
0x0001–0xFFFF. If zero is specified, then the defaults specified using the
DEFINE_DLUR_DEFAULTS verb are used.
def_data.dlus_retry_limit
Retry count for contacting a DLUS. This parameter is used to specify the number of times SNAplus2 should
retry if it fails to contact the DLUS on the first attempt.
Specify a value in the range 0x0001–0xFFFE, or specify 0xFFFF to indicate that SNAplus2 should retry
indefinitely until it contacts the DLUS.
def_data.pu_can_send_dddlu_offline
Specifies whether the local PU should send NMVT (power off) messages to the host. If the host system
supports DDDLU (Dynamic Definition of Dependent LUs), SNAplus2 sends NMVT (power off) to the host
when it has finished using a dynamically defined LU. This allows the host to save resources by removing the
definition when it is no longer required.
Possible values are:
AP_YES
The local PU sends NMVT (power off) messages to the host.
160