HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
SET_TRACE_TYPE
If a trace message is longer than the length specified in this parameter, SNAplus2 writes only the start of the
message to the trace file, and discards the data beyond
truncation_length. This allows you to record the most
important information for each message but avoid filling up the file with long messages.
To specify no truncation (all the data from each message is written to the file), set this parameter to zero.
init_flags
Specifies whether to initialize tracing (define the tracing state at all interfaces), or to change the state of
tracing at one or more interfaces (leaving the others unchanged). Possible values are:
AP_YES
Tracing is being initialized. The trace_flags parameter defines the required state of tracing at all
interfaces.
AP_NO
Tracing is being changed. The trace_flags parameter defines the interfaces where tracing is being
activated or deactivated; other interfaces will not be affected.
set_flags
If init_flags is set to AP_NO, this parameter specifies whether tracing is to be activated or deactivated at the
requested interfaces. Possible values are:
AP_YES
Tracing is to be activated at the interfaces specified by the trace_flags parameter.
AP_NO
Tracing is to be deactivated at the interfaces specified by the trace_flags parameter.
If init_flags is set to AP_YES, this parameter is ignored.
3.184.3 Returned Parameters: Successful Execution
If the verb executes successfully, SNAplus2 returns the following parameters:
primary_rc
AP_OK
secondary_rc
Not used.
3.184.4 Returned Parameters: Parameter Check
If the verb does not execute because of a parameter error, SNAplus2 returns the following parameters:
primary_rc
AP_PARAMETER_CHECK
secondary_rc
AP_INVALID_TRUNC_LEN
The truncation_length parameter specified a length of less than 256 bytes.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_PARAMETER_CHECK,
which are common to all NOF verbs.
731