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.

DUMP Host Storage<br />

Usage Notes<br />

Responses<br />

of the storage size specified at system generation <strong>and</strong> the real storage size).<br />

The address hexloc2 may be from one to sixteen hexadecimal digits; leading<br />

zeros are optional.<br />

Specify END if you want to dump the remaining contents of storage. END is the<br />

default.<br />

A colon (:) means the same as a dash (-) when specifying a range of<br />

addresses.<br />

END<br />

. bytecount<br />

is a hexadecimal integer designating the number of bytes of storage (starting<br />

with the byte at hexloc1) to be dumped to your virtual printer. The sum of<br />

hexloc1 <strong>and</strong> bytecount must be an address that does not exceed the bounds of<br />

addressable storage (the lesser of the storage size specified at system<br />

generation <strong>and</strong> the real storage size). The specified byte count must have a<br />

value of at least one <strong>and</strong> may be from one to sixteen hexadecimal digits.<br />

Leading zeros are optional.<br />

Specify END if you want to dump the remaining contents of storage. END is the<br />

default.<br />

*dumpid<br />

is an asterisk followed by a 1-character to 97-character identifier (truncated to<br />

80 characters for a z/Architecture guest), that is to be assigned to the dump. If<br />

specified, dumpid must be the last oper<strong>and</strong> you enter on the comm<strong>and</strong> line.<br />

1. While dumping host storage, the running of a virtual machine or someone using<br />

the STORE HOST comm<strong>and</strong> could cause data to be changed. This could create<br />

an inconsistency in the data that is viewed.<br />

2. In a multiprocessor environment, each processor has a prefix register that it<br />

uses to relocate addresses between 0 <strong>and</strong> X'1FFF' to another page frame in<br />

storage. The prefix register enables each processor to use a different page<br />

frame to avoid conflict with other processors for such activity as interrupt code<br />

recording. Thus, the range 0 through X'1FFF' refers to different areas of<br />

storage, depending on which processor generates the address. All references to<br />

first-level storage are h<strong>and</strong>led as if they were made on the IPL processor.<br />

3. For more information, see “Usage Notes” on page 351.<br />

Response 1:<br />

Hhexloc word1 word2 ... word8 [key ] [*TRANSLATION*]<br />

is the response you receive with the T or N option. The translation is dumped only if<br />

you have also entered the T option <strong>and</strong> is in either EBCDIC or (if the TX option is<br />

specified) ASCII. The storage key is dumped on the first line, <strong>and</strong> at every page<br />

boundary.<br />

Response 2:<br />

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

Xhexlochi_ Storage Key - [Key]<br />

hexloclo word1 word2 word3 word4 [*TRANSLATION*] [Lhexloc]<br />

is the response you receive with the M option. The translation is displayed in either<br />

EBCDIC or (if the MX option is specified) ASCII. The storage key is displayed on<br />

the first line, <strong>and</strong> at every page boundary.

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

Saved successfully!

Ooh no, something went wrong!