HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
DISCONNECT_NODE
3.82 DISCONNECT_NODE
An application uses this verb to release its handle to a SNAplus2 node when it has finished issuing NOF verbs to
the node. The node from which the application wishes to disconnect is identified by the
target_handle parameter
on the call. After the verb completes successfully, the target handle identifying the node is no longer valid.
The application should always issue DISCONNECT_NODE for any open node handles before it exits, to allow
SNAplus2 to free the resources associated with the application.
This verb may be issued to release a target handle for a running node, or for a server where the node is not running.
3.82.1 VCB Structure
typedef struct disconnect_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 */
} DISCONNECT_NODE;
3.82.2 Supplied Parameters
opcode
AP_DISCONNECT_NODE
3.82.3 Returned Parameters: Successful Execution
If the verb executes successfully, SNAplus2 returns the following parameters:
primary_rc
AP_OK
secondary_rc
Not used.
3.82.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 specified target handle cannot be released because a previous verb issued for this handle is still
outstanding. All verbs for the target handle must be completed before attempting to disconnect from
the node.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_STATE_CHECK, which
are common to all NOF verbs.
320