Technical data

speciﬁes that only trace records with event code RX (receive) are to be

displayed. See Section 3.8 for more information about the /FILTER qualiﬁer.

• You can use the /NAME qualiﬁer to specify that only trace records from

certain tracepoints are to be displayed; for example:

CTF> ANALYZE/NAME="SYN-0"

speciﬁes that only trace records from tracepoints with the instance name

SYN-0 are to be displayed.

• You can use the /BEFORE and /SINCE qualiﬁers to specify that only trace

records collected before or after a speciﬁed time are to be displayed.

If your process holds identiﬁer NET$TraceAll for tracing local data or

NET$TraceAllRemote for tracing remote data, the information in a trace record

will consist of a protocol header and user data. For any particular tracepoint,

the user data in the trace record will include the protocol headers from higher

protocol levels. For example, the user data in a trace record collected from

a DDCMP LINK tracepoint will include the protocol information from the

appropriate ROUTING CIRCUIT tracepoint.

If your process does not hold NET$TraceAll or NET$TraceAllRemote, the user

data portion is neither collected nor displayed.

By default, the analysis of a trace record will not include protocol information

within the user data part of the trace record. For example, the default analysis

of a trace record from a ROUTING CIRCUIT tracepoint would analyze only the

routing packet header, and the protocol information for the higher levels would be

displayed as user data.

You can use the /PROTOCOL qualiﬁer to specify that protocol information in the

user data part of the trace record is also to be analyzed. For example:

CTF> ANALYZE/PROTOCOL=(DDCMP,ROUTING)

would analyze both the routing and DDCMP protocol information in each trace

record. Note that you must take care to specify the protocols in the correct order,

from the lowest protocol level upwards. If, for example, you were to specify:

CTF> ANALYZE/PROTOCOL=(ROUTING,DDCMP)

the effect would be to analyze the routing packet header as though it were a

DDCMP packet header and the DDCMP packet header as though it were a

routing packet header. The analysis would be performed as speciﬁed, but the

results would, of course, be nonsense.

The /SELECT qualiﬁer is usually used only in connection with the /PROTOCOL

qualiﬁer. If you use the /PROTOCOL qualiﬁer to select multiple protocol analysis

of a trace record, you can use the /SELECT qualiﬁer to specify that only some of

these protocols should be displayed. For example, if you use:

CTF> ANALYZE/PROTOCOL=(MODEM_CONNECT,DDCMP,ROUTING)

to display the analyses of these three protocols, you could subsequently use:

CTF> ANALYZE/SELECT=(DDCMP)

to display only the DDCMP protocol analysis, or:

CTF> ANALYZE/SELECT=(MODEM_CONNECT,ROUTING)

to display only the analyses of the modem connect and routing protocols.

Using CTF 3–9