Technical data

Table 3–2 Default CTF Keys

Key CTF Function

HELP HELP

PF2 HELP KEYPAD DEFAULT

PF3 SHOW KEY/ALL

KP0 NEXT

KP2 START

KP3 STOP

KP4 ANALYZE/DATA=ASCII/NOSELECT

/NODISPLAY/NOTRUNCATE

KP6 ANALYZE/DISP=ALL/WIDTH=132

KP7 ANALYZE/DATA=ASCII

KP8 ANALYZE/DATA=HEXADECIMAL

KP9 ANALYZE/DATA=OCTAL

MINUS ANALYZE/DATA=DECIMAL

COMMA ANALYZE/TRUNCATE

PERIOD BACK

NEXT_SCREEN NEXT

PREV_SCREEN BACK

CTRL/L CLEAR

CTRL/W REFRESH

GOLD COMMA ANALYZE/NOTRUNCATE

GOLD KP0 ANALYZE/SCROLL

GOLD KP2 START/LIVE

GOLD KP6 ANALYZE/NODISPLAY

GOLD NEXT_SCREEN ANALYZE/SCROLL

3.8 Filtering

Filtering reduces the impact of tracing on system performance by reducing the

number of trace records collected. This, in turn, reduces, the number of trace

records that have to be written to trace ﬁles or displayed on a terminal.

Each trace record includes an event code that indicates the type of event that

caused the trace record to be generated. You can use the /FILTER qualiﬁer in

the START command to specify that only trace records with speciﬁed event codes

should be collected. For example, most tracepoints generate trace records for

the Receive and Transmit events; you can use /FILTER to specify that only trace

records generated for Transmit events are to be collected.

For example:

CTF> START/FILTER=TX "ROUTING CIRCUIT UNA-0"

starts tracing at the speciﬁed tracepoint, but indicates that only trace records

with event code TX (transmit) are to be collected.

3–12 Using CTF