z/VM: CP Commands and Utilities Reference - z/VM - IBM

Usage Notes
THEN DL datalinks
identifies the data to be traced if the result of the preceding IF statement is true.
A THEN statement may be followed by any number of datalinks, all of which are
executed only if the result of the preceding IF statement is true.
A subsequent IF statement (not preceded by an ELSE statement or ENDIF
statement; that is, a nested IF statement) would be executed only if the result of
the preceding IF statement is true.
THEN IF
identifies a nested IF statement. Such an IF statement would be executed only
if the result of the preceding IF statement is true.
Up to 16 nested IF statements are allowed. Each IF statement must be paired
with an ENDIF statement.
ELSE DL datalinks
identifies the data to be traced if the result of the preceding IF statement is
false. An ELSE statement may be followed by any number of datalinks all of
which are executed only if the result of the preceding IF statement is false.
A subsequent IF statement (not preceded by an ENDIF statement, thus a
nested IF statement) would be executed only if the result of the preceding IF
statement is false.
ELSE IF
identifies a nested IF statement. Such an IF statement would be executed only
if the result of the preceding IF statement is false.
Up to 16 nested IF statements are allowed. Each IF statement must be paired
with an ENDIF statement.
ENDIF
identifies the end of conditional datalinks associated with the last unclosed IF
statement.
Each IF statement must be closed with an ENDIF statement before the traceid
can be enabled.
(General for TRSOURCE ID)
1. If you use the ID operand to define a trace ID, ID must be the first operand on
the command line.
2. While specific type-dependent operands are optional on the TRSOURCE
command, certain type-dependent operands may be required for a trace ID
before it can be enabled. Refer to the description of the specific trace types to
determine which operands are required before a trace ID of that trace type can
be enabled.
3. The TYPE operand, if used, must directly precede any type-dependent
operands.
4. All type-dependent operands must be contiguous. The order depends on the
requirements of the trace type.
Type I/O Usage Notes
1. You can define an I/O trace for a nonexistent device—that is, a device that has
no RDEVICE definition. If a trace with only such devices is enabled, message
HCP477E is issued:
Traceid (TRACEid) not enabled; incomplete definition
TRSOURCE ID (Definition Operands)
Chapter 2. CP Commands 1689