 |
» |
|
|
|
The set_trace_type command specifies tracing options for SNAplus2 kernel
components. You can use this command to specify the state of tracing
(on or off) at all interfaces or to turn tracing on or off at specific interfaces
(leaving tracing at other interfaces unchanged). For more information
about tracing options, refer to the HP-UX SNAplus2 Diagnostics
Guide. This command does not control DLC line tracing. To control
DLC line tracing use the add_dlc_trace command. This command must be issued to a running node. Supplied Parameters | |
Parameter name Type Length Default
[set_trace_type]
trace_flags constant NONE
truncation_length decimal 1024
init_flags constant YES
set_flags constant YES
|
Supplied parameters are: - trace_flags
The types of tracing required. For more information about
these trace types, refer to HP-UX SNAplus2 Diagnostics
Guide. If init_flags is set to YES, select the
values corresponding to the interfaces where you want tracing to
be active, and do not select the values corresponding to the interfaces
where you want it to be inactive. If init_flags is set to NO, select the values corresponding
to the interfaces where you want to change the state of tracing. To set tracing for all types of messages use one of the following
values: - NONE
Do not activate tracing for any type of messages. - ALL
Activate tracing for all types of messages.
To set tracing for a specific interface, use one or more of the
following values (combined using + characters). - APPC
Trace APPC messages - FM
Trace FM messages - LUA
Trace LUA messages - NOF
Trace NOF messages - MS
Trace MS messages - PV
Trace APPC and CPI-C messages for back-level computers - DLPI
Trace DLPI messages - SDLC
Trace SDLC messages (note that this option also provides
additional detail in SDLC line tracing). - NLI
Trace NLI messages - NDLC
Trace node to DLC messages - NODE
Trace node internal messages - SLIM
Trace messages sent between servers in a client-server system - DGRM
Trace internal control messages between SNAplus2 components
- truncation_length
The maximum length, in bytes, of the information written
to the trace file for each message. If a message is longer than
this value, SNAplus2 writes only the start of the message to the
trace file and discards the data beyond truncation_length. Truncation enables 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 0. - 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: - YES
Initialize tracing. The trace_flags parameter defines the required state of tracing at
all interfaces. - NO
Change the state of tracing. The trace_flags parameter defines the interfaces where tracing is to
be activated or deactivated; other interfaces will not be affected.
- set_flags
If init_flags is set to NO, this parameter
specifies whether to activate or deactivate tracing at the requested
interfaces. Possible values are: - YES
Activate tracing at the interfaces specified by
the trace_flags parameter. - NO
Deactivate tracing at the interfaces specified by
the trace_flags parameter.
If init_flags is set to YES, this parameter
is ignored.
Returned Parameters | |
No parameters are returned by SNAplus2 when this command executes successfully. Error Return Codes | |
If the command cannot be executed, SNAplus2 returns a primary
return code to indicate the type of error and a secondary return
code to provide specific details about the reason for unsuccessful
execution. If the command does not execute because of a parameter error,
SNAplus2 returns the following parameters: - primary_rc
PARAMETER_CHECK - secondary_rc
- INVALID_TRUNC_LEN
The truncation_length parameter specified a length of less than 256 bytes.
|
Printable version
