|
|
|
|
This verb specifies tracing on SNA messages sent on a DLC. It can be used to activate tracing on a particular DLC, port, LS, or HPR RTP connection, or on a particular session on a specified LS, and to specify which types of messages are to be traced. It can also be used to activate tracing on all DLCs, ports, link stations, and HPR RTP connections. For more information about how to use SNAP-IX tracing, see the SNAP-IX Administration Guide.
If multiple ADD_DLC_TRACE verbs relating to the same resource are issued, a message will be traced if it matches any of the verbs currently active. For example:
If you issue a verb to trace all messages for a port and its LSs, and then issue a second verb to trace only messages with a specified LFSID for one of the LSs owned by the port, all messages for the LS will continue to be traced (because they match the first verb). If you then use REMOVE_DLC_TRACE to remove tracing for the port, messages on the LS with the specified LFSID will continue to be traced (because they match the second verb which is still active), but other messages on this LS will not be traced.
If you issue a verb to trace XID messages on all resources, and then issue a second verb to trace SC and DFC messages on a particular LS, all three message types will be traced for this LS.
If you are tracing an SDLC line and would like more detailed trace information, you can get this by using internal tracing on SDLC as well as line tracing. The additional detail is formatted as part of the output for line tracing, so that you will see all of the SDLC tracing in one file. For more information, see SET_TRACE_TYPE.
typedef struct add_dlc_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 */
DLC_TRACE_FILTER filter; /* resource to be traced */
} ADD_DLC_TRACE;
typedef struct dlc_trace_filter
{
unsigned char resource_type; /* type of resource */
unsigned char resource_name[8]; /* name of resource */
SNA_LFSID lfsid; /* session identifier */
unsigned char message_type; /* type of messages */
} DLC_TRACE_FILTER;
typedef struct sna_lfsid
{
union
{
AP_UINT16 session_id;
struct
{
unsigned char sidh;
unsigned char sidl;
} s;
} uu;
AP_UINT16 odai;
} SNA_LFSID;
The application supplies the following parameters:
Specifies the resource to be traced, and optionally the specific message types to be traced for this resource. Possible values are:
Set up tracing options for all DLCs, ports, link stations, and HPR RTP connections.
Set up tracing options for the DLC named in resource_name , and for all ports and LSs that use this DLC.
Set up tracing options for the port named in resource_name , and for all LSs that use this port.
Set up tracing options for the LS named in resource_name .
Specify tracing options for the RTP connection named in resource_name.
Set up tracing options for the port named in resource_name , and for all defined LSs (but not implicit LSs) that use this port.
Set up tracing options for the port named in resource_name , and for all implicit LSs (but not defined LSs) that use this port.
The name of the DLC, port, LS, or
RTP connection for which tracing is being activated. This parameter is
reserved if resource_type is set to
If resource_type is set to
The Local Form Session Identifier for a session on the specified LS.
This is only valid for resource_type
Session ID high byte.
Session ID low byte.
Origin Destination Assignor Indicator.
The type of messages to trace for the specified resource or session.
Set this parameter to
XID messages
Session Control RUs
Data Flow Control RUs
FMD messages
Non-BBIU segments that do not contain an RH
Messages other then MUs and XIDs
Trace Network-Layer Protocol messages
Trace Network Control messages
For tracing on an RTP connection, the values
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
Possible values are:
The resource_type parameter specified a value that was not valid.
The message_type parameter specified a value that was not valid.
The resource_name parameter does not match any RTP connection.
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.
|
|
|
 |
|