HP-UX SNAplus2 NOF Programmer's Guide

NOF API Verbs (ACTIVATE_SESSION to OPEN_FILE)
DISCONNECT_NODE
Chapter 3 481
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 either to a running node or to a server where the
node is not running. It may also be issued to the local HP-UX client
computer, if the application has used CONNECT_NODE to access the
local client computer in order to control client-server tracing. For more
information, see “CONNECT_NODE”.
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;
Supplied Parameters
opcode AP_DISCONNECT_NODE
Returned Parameters: Successful Execution
If the verb executes successfully, SNAplus2 returns the following
parameters:
primary_rc AP_OK
secondary_rc Not used.