HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
SET_TRACE_FILE
AP_TN_SERVER_NO_TRACE
No tracing.
AP_TN_SERVER_ALL_TRACE
Tracing of all types.
To activate tracing on specific message types, select one or more values from the list below, combined using
a logical
OR operation.
AP_TN_SERVER_TRC_TCP
TCP/IP interface tracing: messages between TN server and TN3270 clients
AP_TN_SERVER_TRC_FM
Node interface tracing: internal control messages, and messages between TN server and TN3270 clients
(in internal format)
AP_TN_SERVER_TRC_CFG
Configuration message tracing: messages relating to the configuration of TN server
AP_TN_SERVER_TRC_NOF
Internal node operator function (NOF) tracing: trace NOF requests made by TN server.
3.182.3 Returned Parameters: Successful Execution
If the verb executes successfully, SNAplus2 returns the following parameters:
primary_rc
AP_OK
secondary_rc
Not used.
3.182.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.183 SET_TRACE_FILE
This verb specifies the name of a file that SNAplus2 uses to record trace data.
If you issue a second SET_TRACE_FILE verb specifying a new file for the same file type, all subsequent trace
information will be written to the new file; the existing file is not removed, but further information will not be
written to it. If you issue a second SET_TRACE_FILE verb for the same trace file, this resets the file (discarding
trace information that was written to the file before the second verb).
This verb must be issued to a running node.
3.183.1 VCB Structure
typedef struct set_trace_file
{
726