LAN Configuration and Management Manual

SCF Commands for the SLSA Subsystem
LAN Configuration and Management Manual—520469-012
4-141
TRACE PIF Command
Considerations

You cannot execute a trace on a PIF until its parent SAC is in the STARTED state.
The trace on the PIF terminates automatically when:

The parent SAC is no longer in the STARTED state.

The data path to the SAC switched to a different processor; that is, an
ownership change occurs.

The trace file becomes full, and you did not specify the WRAP option when the
trace was initiated.

You can have a maximum of 64 open traces for SAC, PIF, and LIF objects in a
single processor.

If TO file-spec is specified, a new trace is initiated unless the file-spec is invalid,
the file cannot be opened, or a trace is already active for the PIF.

If TO file-spec and STOP are both omitted, the TRACE command modifies the
trace currently in progress, if any.

If TO file-spec is omitted and STOP is specified, the TRACE command stops the
trace currently in progress, if any.
Table 4-5. select-spec for a PIF object
Keyword Number Meaning
ALL -1 Trace all items
CALLIN 8 Trace call in from external components for
PIF object in DIH
CALLOUT 9 Trace call out to external components for PIF
object in DIH
CALLLOCAL 10 Trace local call for PIF object in DIH
PING 11 Trace PIF object ping related action in DIH
SMACH 12 Trace PIF state machine operations for PIF
object
SNET 13 Trace PIF object ServerNet events
SNETINT 14 Trace PIF object ServerNet interrupt events
QSERV 15 Trace PIF object queue service
TXDATA 16 Trace PIF object outbound data
RXDATA 17 Trace PIF object inbound data
LMOMSG 18 Trace messages between LANMON and DIH
for PIF objects
ERROR 19 Trace DIH errors for PIF object