HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
DEFINE_DLC
} VDL_DLC_CFG;
For all DLC types:
typedef struct v0_mux_info
{
AP_UINT16 dlc_type; /* DLC implementation type */
unsigned char need_vrfy_fixup; /* reserved */
unsigned char num_mux_ids; /* reserved */
AP_UINT32 card_type; /* type of adapter card */
AP_UINT32 adapter_number; /* DLC adapter number */
AP_UINT32 oem_data_length; /* reserved */
AP_INT32 mux_ids[5]; /* reserved */
} V0_MUX_INFO;
3.19.2 Supplied Parameters
The application supplies the following parameters:
opcode
AP_DEFINE_DLC
dlc_name
Name of the DLC. This is an 8-byte ASCII string, using any locally displayable characters, padded on the
right with spaces if the name is shorter than 8 bytes.
def_data.description
A null-terminated text string (0–31 characters followed by a null character) describing the DLC. This string
is for information only; it is stored in the node’s configuration file and returned on the QUERY_DLC verb,
but SNAplus2 does not make any other use of it.
def_data.initially_active
Specifies whether this DLC is automatically started when the node is started. Possible values are:
AP_YES
The DLC is automatically started when the node is started.
AP_NO
The DLC is automatically started only if a port or LS that uses it is defined to be initially active;
otherwise it must be started manually.
def_data.dlc_type
Type of the DLC. You cannot change this parameter for an existing DLC; this parameter can be specified
only when creating a new DLC. Possible values are:
AP_SDLC
SDLC
AP_X25
QLLC
AP_TR
Token Ring
AP_ETHERNET
131