|
|
|
|
This verb specifies tracing options for SNAP-IX kernel components. You can use this verb 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, see the SNAP-IX Administration Guide.
This verb does not control DLC line tracing. To do this, use the ADD_DLC_TRACE verb.
This verb must be issued to a running node.
typedef struct set_trace_type
{
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 */
AP_UINT32 truncation_length; /* truncate each msg to this size */
unsigned char init_flags; /* TRUE if initializing flags */
unsigned char set_flags; /* TRUE if setting flags */
/* FALSE if unsetting flags */
unsigned char set_internal; /* reserved */
AP_UINT16 internal_level; /* reserved */
AP_UINT32 api_flags; /* reserved */
} SET_TRACE_TYPE;
The application supplies the following parameters:
The types of tracing required. To turn off all tracing, or to turn on tracing of all types, specify one of the following values:
No tracing.
Tracing of all types.
To control tracing on specific interfaces, select one or more values from the list below, combined using a logical OR operation. For more information about these trace types, see Trace Types.
If init_flags is set to
APPC messages
FM messages
LUA messages
NOF messages
MS messages
LLC2 messages
LLI messages
MAC messages
SDLC messages (note that this option also provides additional detail in SDLC line tracing)
NLI messages
Enterprise Extender (HPR/IP) messages
Node to DLC messages
Node messages
Messages sent between master and backup servers
Datagram messages
Specify the maximum length, in bytes, of the information to be written to the trace file for each message. This value must be at least 256.
If a trace message is longer than the length specified in this parameter, SNAP-IX 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.
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:
Tracing is being initialized. The trace_flags parameter defines the required state of tracing at all interfaces.
Tracing is being changed. The trace_flags parameter defines the interfaces where tracing is being activated or deactivated; other interfaces will not be affected.
If init_flags is set to
Tracing is to be activated at the interfaces specified by the trace_flags parameter.
Tracing is to be deactivated at the interfaces specified by the trace_flags parameter.
If init_flags is set to
If the verb executes successfully, SNAP-IX returns the following parameters:
AP_OK
Not used.
If the verb does not execute because of a parameter error, SNAP-IX returns the following parameters:
AP_PARAMETER_CHECK
The truncation_length parameter specified a length of less than 256 bytes.
Common Return Codes lists further secondary return codes associated with AP_PARAMETER_CHECK, which are common to all NOF verbs.
Common Return Codes lists further combinations of primary and secondary return codes that are common to all NOF verbs.
Overall Structure of SNAP-IX, shows the overall structure of SNAP-IX. Each kernel-space trace type, relating to data transferred across a particular interface between SNAP-IX components, is shown in the diagram at the interface where it is traced.
Overall Structure of SNAP-IX shows the following types of tracing, each of which can be controlled separately:
Messages between the APPC library and the node
Messages between a 3270 emulation program, LU0 application, or RJE workstation and the node
Messages between the LUA library and the node
Messages between the NOF library and the node
Messages between the MS library and the node
SNA data sent on a DLC (tracing on these messages is controlled by the ADD_DLC_TRACE verb, not by SET_TRACE_TYPE)
Messages between the APPN node and the DLC component
In addition, the following message types (internal to SNAP-IX) can be traced:
Messages between components within the APPN protocol code
Messages sent between master and backup servers in a client-server system
Internal control messages between system components
|
|
|
 |
|