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 STORE (ESA/XC)<br />

Usage Notes<br />

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

decimal digits. The access list entry token within the access register is used in<br />

conjunction with the host-access register translation tables to locate the address<br />

space to be traced.<br />

ASITasit<br />

restricts tracing to events in the address space identified by the address space<br />

identification token, asit.<br />

PRI<br />

restricts tracing to the current primary address space.<br />

SPACEowner:space_name<br />

limits tracing to the address space identified by owner:space_name, where<br />

owner: specifies the user ID that owns the address space <strong>and</strong> space_name is<br />

the name of the address space—the owner’s user ID can be omitted if the<br />

owner is the user issuing the comm<strong>and</strong>. The space name is a string of<br />

alphanumeric <strong>and</strong> national characters, 1 to 24 characters long.<br />

range<br />

limits tracing to changes to at location within the specified range.<br />

The range can be a single address or a pair of addresses separated by a<br />

period (.) or a hyphen (-). A hyphen denotes a starting <strong>and</strong> ending range. A<br />

period denotes a starting address <strong>and</strong> a byte count. A data location is<br />

considered to be within the range if the first byte is within the range.<br />

hexloc<br />

limits tracing to a specific location for the conditions set by the DATA <strong>and</strong> MASK<br />

oper<strong>and</strong>s. The oper<strong>and</strong> hexloc can be any valid address. It cannot be a range<br />

of addresses.<br />

DATA hexstring<br />

specifies a hexadecimal data string to be matched when a store occurs into the<br />

specified hexloc. The length of the data string determines the bounds of the<br />

test. If the MASK option is also specified, the mask is logically applied to both<br />

storage <strong>and</strong> the DATA string before the comparison is made. The DATA<br />

oper<strong>and</strong> requires the INTO hexloc oper<strong>and</strong>.<br />

MASK hexstring<br />

specifies a hexadecimal string that forms a mask for data comparison when a<br />

store occurs in the specified hexloc. When you specify the MASK option, the<br />

mask is logically applied to both storage <strong>and</strong> the DATA string before the<br />

comparison is made. Only those bits <strong>and</strong> bytes that are binary ones are<br />

checked. The MASK oper<strong>and</strong> requires the INTO hexloc oper<strong>and</strong> <strong>and</strong> the DATA<br />

option. The length of the MASK string must be the same as the length of the<br />

string you specified for the DATA option.<br />

options<br />

For an explanation of the options, see “TRACE: Options” on page 1604.<br />

1. TRACE STORE does not trace storage alterations caused by the following<br />

instructions:<br />

All DIAGNOSE instructions<br />

All Cryptographic facility instructions<br />

All VECTOR instructions<br />

Asynchronous I/O instructions<br />

IUCV/<strong>VM</strong>CF/APPC<br />

COMPRESSION CALL (CMPSC)<br />

CONVERT UNICODE to UTF-8 (CUUTF)

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

Saved successfully!

Ooh no, something went wrong!