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.

Usage Notes<br />

TRACE STORE (ESA/390, z/Architecture)<br />

hexloc<br />

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

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

range 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 may 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)<br />

CONVERT UTF-8 to UNICODE (CUTFU)<br />

MOVE LONG (MVCL)<br />

MOVE LONG EXTENDED (MVCLE)<br />

MOVE LONG UNICODE (MVCLU)<br />

MOVE STRING INSTRUCTION (MVST)<br />

TRANSLATE EXTENDED (TRE)<br />

TRANSLATE ONE TO ONE (TROO)<br />

TRANSLATE ONE TO TWO (TROT)<br />

TRANSLATE TWO TO ONE (TRTO)<br />

TRANSLATE TWO TO TWO (TRTT)<br />

2. If the DATA option is specified, the length of the virtual storage that is monitored<br />

for alteration is defined by the length of the DATA string. If this length added to<br />

the specified hexloc generates a wraparound address range, the ending<br />

address of the storage to be monitored is set to the end of storage as defined<br />

by <strong>CP</strong>’s current architecture.<br />

3. Guest control register values <strong>and</strong> translation table contents define the address<br />

space structure of the virtual machine. Program execution (<strong>and</strong> the STORE<br />

comm<strong>and</strong>) can change that structure over time. The TRACE comm<strong>and</strong><br />

oper<strong>and</strong>s that specify a guest address space to be traced by a trace trap use<br />

the guest control register <strong>and</strong> translation table values to determine the segment<br />

table origin (STO) of the address space to be traced at the time the TRACE<br />

comm<strong>and</strong> is issued. The STO is contained in the trace trap <strong>and</strong> can be<br />

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

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

Saved successfully!

Ooh no, something went wrong!