27.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

TRSOURCE ID (Definition Oper<strong>and</strong>s)<br />

EVENT<br />

specifies the recording mode for tracing. This mode must match the capabilities<br />

of the guest virtual machine.<br />

If you specify BLOCK, the guest virtual machine passes blocks of trace data to<br />

the control program. These blocks are written to a system trace file.<br />

If you specify EVENT, the virtual machine passes individual records directly to<br />

the control program. Each trace record is written to a system trace file.<br />

The DATA Trace<br />

Trace type DATA allows the user to dynamically define trace entries to record<br />

execution of most code paths in <strong>CP</strong>. The LOC parameter specifies which instruction,<br />

when executed, triggers recording of information. Data link parameters define what<br />

information is collected when the trace springs.<br />

Note: Any or none of the following DATA parameters may be specified on a<br />

TRSOURCE comm<strong>and</strong>. Specification of a given parameter must be<br />

consistent with the state of the traceid as defined by previously entered<br />

parameters, including parameters entered via previous invocations of the<br />

TRSOURCE comm<strong>and</strong>.<br />

LOC { address instruction }<br />

{ modname + disp instruction }<br />

DL datalinks<br />

IF datalink { EQ } { datalink }<br />

{ NE } { constant }<br />

{ GT }<br />

{ GE }<br />

{ LT }<br />

{ LE }<br />

THEN { DL datalinks }<br />

{ }<br />

{ IF ... ENDIF }<br />

ELSE { DL datalinks }<br />

{ }<br />

{ IF ... ENDIF }<br />

ENDIF<br />

1686 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

LOC address<br />

specifies the address in the <strong>CP</strong> nucleus that identifies the trace point at which<br />

the data is to be collected.<br />

LOC modname + disp<br />

specifies the <strong>CP</strong> module name <strong>and</strong> displacement into that module that identifies<br />

the trace point at which the data is to be collected. If the module is written in a<br />

higher-level language, an 8-character module name must be supplied.<br />

See Type Data Usage Note 6 on page 1691 for a list of restricted locations.<br />

instruction<br />

identifies in hexadecimal characters the contents of storage at the specified<br />

trace point. Matching the specified instruction with the contents of storage<br />

verifies that the trace point is at the intended location in the <strong>CP</strong> nucleus. The<br />

instruction supplied must be at least as long as the instruction to be verified.<br />

Only that instruction is verified, <strong>and</strong> any extraneous hexadecimal data is

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!