HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
QUERY_TN_SERVER_TRACE
def_data.keepalive_interval
Interval (in seconds) between consecutive keep-alive messages. The interval should be long enough to
minimize network traffic, especially if there are typically many idle client connections. The shorter the keep-
alive interval, the quicker failures are detected, but the more network traffic is generated. If the keep-alive
interval is too short and there are many clients, this traffic can be significant.
Because of the way TCP/IP operates, the keepalive interval that you configure is not the exact time that it
will take for the server to recognize that a client has disappeared. The exact time depends on various factors,
but will be no more than twice the configured timeout plus a few extra minutes (the exact number depends
on how TCP/IP is configured).
3.162.4 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.163 QUERY_TN_SERVER_TRACE
This verb returns information about the current tracing options for the SNAplus2 TN server feature.
This verb must be issued to a running node.
3.163.1 VCB Structure
typedef struct query_tn_server_trace
{
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 */
AP_UINT16 trace_flags; /* trace flags */
unsigned char reserv3[6]; /* Reserved */
} QUERY_TN_SERVER_TRACE;
3.163.2 Supplied Parameters
The application supplies the following parameter:
opcode
AP_QUERY_TN_SERVER_TRACE
3.163.3 Returned Parameters: Successful Execution
If the verb executes successfully, SNAplus2 returns the following parameters:
primary_rc
AP_OK
secondary_rc
Not used.
678