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.

1. Enter keyword parameters (if any).<br />

2. Enter the ENDPARM keyword parameter.<br />

3. Enter control statements (if any).<br />

A comment card (*) may appear anywhere in the sequence above. The<br />

TERMINAL oper<strong>and</strong> is ignored if you enter it while using the prompting method.<br />

v When you specify a keyword whose allowed values are Y <strong>and</strong> N, <strong>and</strong> you select<br />

the value Y, you may enter the keyword parameter without specifying a value.<br />

This form of the keyword parameter is always interpreted as a Y specification,<br />

regardless of the normal default value.<br />

v To begin <strong>CP</strong>EREPXA with system default values, respond to the first ENTER:<br />

prompt message with the ENDPARM keyword parameter. When the second<br />

ENTER: prompt message appears, respond to it by pressing the ENTER key<br />

without any input; the null line signals to the system that there is no more input.<br />

File Entry Method<br />

The <strong>CP</strong>EREPXA comm<strong>and</strong> is entered followed by the file name, file type, <strong>and</strong> file<br />

mode of a file that contains a “package” of EREP keyword parameters <strong>and</strong> control<br />

statements arranged in the format as described in “Prompting Method” above. The<br />

same rules regarding blanks, commas, <strong>and</strong> parentheses apply; in addition, card<br />

images are truncated at column 71.<br />

In practice, an installation probably has multiple files containing various oper<strong>and</strong><br />

mixes to satisfy the installation <strong>CP</strong>EREPXA report needs. To create <strong>and</strong> generate<br />

the necessary <strong>CP</strong>EREPXA files for this method of entry, use the CMS XEDIT<br />

comm<strong>and</strong>. File generation using the CMS XEDIT comm<strong>and</strong> is described in z/<strong>VM</strong>:<br />

XEDIT User’s Guide.<br />

Mixed Method:<br />

The <strong>CP</strong>EREPXA comm<strong>and</strong> is entered followed by the file name, file type, <strong>and</strong> file<br />

mode of a file that contains EREP keyword parameters <strong>and</strong> control statements, one<br />

of which is the TERMINAL oper<strong>and</strong> of <strong>CP</strong>EREPXA. This oper<strong>and</strong> may appear<br />

anywhere in the file, <strong>and</strong> keyword parameters (if any) <strong>and</strong> control statements (if<br />

any) are read until it is encountered. At this point, no further input is read from the<br />

file. Prompting begins at the display station, where additional EREP keyword<br />

parameters <strong>and</strong> control statements may be entered. When the system responds to<br />

the TERMINAL oper<strong>and</strong> by transferring control from the control file to the display<br />

station, it expects input to proceed from the beginning of the sequence as it is<br />

described in “Prompting Method” above.<br />

<strong>CP</strong>EREPXA FILEDEFs<br />

<strong>CP</strong>EREPXA<br />

<strong>CP</strong>EREPXA issues the FILEDEFs listed below before invoking EREP. These allow<br />

CMS to simulate the corresponding EREP files.<br />

Where a mode letter of x is shown, x represents the read/write disk that has the<br />

most free space when <strong>CP</strong>EREPXA is invoked. At the end of the run, the FILEDEFs<br />

listed below are cleared with the exception of:<br />

v EREPPT<br />

v ACCIN<br />

v ACCDEV.<br />

These FILEDEFs are left intact because you can sometimes supply them yourself.<br />

Chapter 3. <strong>CP</strong> <strong>Utilities</strong> 1777

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

Saved successfully!

Ooh no, something went wrong!