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.

<strong>VM</strong>DUMP<br />

Usage Notes<br />

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

XA<br />

has no effect. XA is retained only for compatibility with previous releases. All<br />

dumps are in z/<strong>VM</strong> format.<br />

*dumpid<br />

is a 1- to 100-character (including any imbedded blanks <strong>and</strong> special characters)<br />

identifier that is associated with the storage dumped for each address space for<br />

which the oper<strong>and</strong> is specified. When specifying dumpid, you must precede it<br />

with an asterisk (*). The system eliminates any blanks between the asterisk <strong>and</strong><br />

the first nonblank character of the dump ID. If you specify a dump ID that is<br />

more than 100 characters in length after the blanks following the asterisk are<br />

eliminated, the system truncates it on the right to a length of 100 characters. If<br />

specified, the dump ID must be the last oper<strong>and</strong> on the comm<strong>and</strong> line.<br />

CLOSE<br />

specifies that <strong>CP</strong> should close the <strong>VM</strong>DUMP system data file currently open for<br />

the issuing user, if one has been created by a previous request in continuous<br />

output mode.<br />

CANCEL<br />

specifies that <strong>CP</strong> should close <strong>and</strong> purge the <strong>VM</strong>DUMP system data file<br />

currently open for the issuing user, if one exists.<br />

CONt<br />

specifies that <strong>VM</strong>DUMP is to operate in continuous output mode, leaving the<br />

output file open after each request, until explicitly closed or canceled, or until a<br />

request is processed after continuous output mode has been reset.<br />

NOCont<br />

specifies that at the completion of subsequent <strong>VM</strong>DUMP requests, the output<br />

file is to be closed.<br />

Combining oper<strong>and</strong>s on the <strong>VM</strong>DUMP comm<strong>and</strong><br />

1. The CONT, NOCONT, CLOSE, <strong>and</strong> CANCEL oper<strong>and</strong>s are not valid in<br />

conjunction with any other <strong>VM</strong>DUMP oper<strong>and</strong>s.<br />

2. When invoking <strong>VM</strong>DUMP to dump guest storage in continuous output mode,<br />

certain restrictions apply to the use of other comm<strong>and</strong> oper<strong>and</strong>s:<br />

v The SYSTEM <strong>and</strong> TO oper<strong>and</strong>s, which pertain to ownership of the file <strong>and</strong><br />

its structure, can be specified only when the file is opened, that is, on the<br />

first request not counting any requests specifying CONT, NOCONT, CLOSE,<br />

or CANCEL. Subsequent requests that merely repeat the current setting of<br />

the oper<strong>and</strong> are ignored, but requests that attempt to change the setting of<br />

the oper<strong>and</strong> (whether it was set explicitly or by default) are rejected with an<br />

error message.<br />

v Oper<strong>and</strong>s used to designate which areas of guest storage to dump are valid<br />

on any of the series of requests in continuous output mode. These oper<strong>and</strong>s<br />

are:<br />

PRIMARY<br />

SPACE userid:space_name<br />

ALET alet<br />

ASIT asit<br />

AREG areg<br />

address-range<br />

DCSS

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

Saved successfully!

Ooh no, something went wrong!