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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

TRACE<br />

Authorization<br />

Purpose<br />

Usage Notes<br />

Privilege Class: G<br />

Use the TRACE comm<strong>and</strong> to monitor events that occur in your virtual machine.<br />

z/<strong>VM</strong> lets you trace a number of events, including:<br />

v Instruction execution<br />

v Storage alteration<br />

v Register alteration<br />

v I/O activity.<br />

Each traced event results in a trace entry, a comm<strong>and</strong> response that you can have<br />

sent to your virtual console, to a virtual printer, or to both. The trace entry is made<br />

up of significant information about the event. You can use trace entries to analyze<br />

the operation of your virtual machine <strong>and</strong> to debug problems.<br />

Note that in this manual the TRACE documentation is primarily for reference.<br />

For a full explanation of how to use the trace facility, along with examples, see<br />

z/<strong>VM</strong>: Virtual Machine Operation.<br />

(General for TRACE)<br />

1. All of the primary TRACE oper<strong>and</strong>s establish trace traps. A trace trap is a<br />

programming function that, as its name implies, captures information about an<br />

event in your virtual machine.<br />

When you establish a trap, you can assign it any unique 1-character to<br />

4-character name (with the exception of the name ALL). If you do not assign a<br />

name, the system assigns the trap a unique number from 1 to 9999. You use<br />

this unique identifier (name or number) to alter a trap with the TRACE TRAP<br />

comm<strong>and</strong> or to delete a trap with the TRACE DELETE comm<strong>and</strong>.<br />

The options (unique <strong>and</strong> common) available with each primary oper<strong>and</strong> <strong>and</strong><br />

with the TRAP oper<strong>and</strong> allow you to specify exactly how you want the trap to<br />

process. For example, you may want the trap to function only when an event<br />

occurs within a particular address range. In this case, you specify the common<br />

option FROM with the address range you choose. At the same time, you may<br />

want to trace events only when your virtual machine is running in supervisor<br />

state. In this case, you also specify the common option SUPERVISOR.<br />

2. All trace traps must be contained in units of control called sets. A “trace set” is<br />

a collection of one or more traps that run together.<br />

You create a set using the TRACE GOTO comm<strong>and</strong>. When you create the set,<br />

you assign it a unique 1-character to 8-character name. If you do not assign<br />

the set a name, the system assigns a unique name for you.<br />

If you do not create a set before you establish a trap, z/<strong>VM</strong> creates a set for<br />

you named INITIAL.<br />

Only one set may be active at any given time.<br />

The following comm<strong>and</strong>s exist for manipulating sets:<br />

v TRACE GOTO<br />

v TRACE CALL<br />

v TRACE RETURN<br />

TRACE<br />

Chapter 2. <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> 1601

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

Saved successfully!

Ooh no, something went wrong!