HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
START_LS
3.186.7 Returned Parameters: Function Not Supported
If the verb does not execute because the node’s configuration does not support it, SNAplus2 returns the following
parameter:
primary_rc
AP_FUNCTION_NOT_SUPPORTED
The node does not support DLUR; this is defined by the dlur_supported parameter on DEFINE_NODE.
3.186.8 Returned Parameters: Other Conditions
Appendix B, Common Return Codes lists further combinations of primary and secondary return codes that are
common to all NOF verbs.
3.187 START_LS
START_LS normally starts an inactive LS. Alternatively, it can be used to leave the LS inactive but specify that it
can be activated automatically by SNAplus2 when required or activated by the remote system.
Note
If the LS is a leased SDLC link or a QLLC PVC link, it must be activated by the remote
system as well as by SNAplus2. You are recommended to define the LS to be activated
when the node is started and to be reactivated automatically after failures, to ensure that
the link is always available; see Section 3.29, DEFINE_LS for more information.
This verb must be issued to a running node.
3.187.1 VCB Structure
typedef struct start_ls
{
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 ls_name[8]; /* name of link station */
unsigned char enable; /* start ls or enable auto-activation? */
unsigned char react_kicked; /* retry in progress? */
unsigned char reserv3[2]; /* reserved */
} START_LS;
3.187.2 Supplied Parameters
The application supplies the following parameters:
opcode
AP_START_LS
ls_name
737