HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs

CONNECT_NODE

3.6.3 Returned Parameters: Successful Execution

If the verb executes successfully, SNAplus2 returns the following parameters:

primary_rc

AP_OK

secondary_rc

Not used.

3.6.4 Returned Parameters: State Check

If the verb does not execute because of a state check, SNAplus2 returns the following parameters:

primary_rc

AP_STATE_CHECK

secondary_rc

AP_VERB_IN_PROGRESS

The speciﬁed ﬁle cannot be released because a previous verb issued for this target handle is still

outstanding. All verbs for the target ﬁle must be completed before attempting to close the ﬁle.

Appendix B, Common Return Codes lists further secondary return codes associated with

AP_STATE_CHECK

, which

are common to all NOF verbs.

3.6.5 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.7 CONNECT_NODE

An application uses this verb in order to establish communications with a SNAplus2 node (active or inactive). The

verb returns a target handle identifying the node, which the application can then use on other NOF verbs to indicate

the target for the verb.

3.7.1 VCB Structure

typedef struct connect_node

{

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 node_type; /* which node to connect to */

unsigned char node_name[128]; /* name of Node */

AP_UINT32 target_handle; /* handle for subsequent verbs */

unsigned char node_status; /* node status */

unsigned char reserv3[12]; /* reserved */

} CONNECT_NODE;