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.

Options<br />

If an asterisk (*) or a period appears in the first column of a control file record,<br />

H<strong>CP</strong>LDR ignores the record. The comm<strong>and</strong> also ignores update level identifiers<br />

of PTF.<br />

ft [./] [...ft]<br />

is a list of file types (up to 256) that you want H<strong>CP</strong>LDR to use in lieu of a<br />

control file. H<strong>CP</strong>LDR establishes a search order from left to right. The list of file<br />

types can be null, in which case a file type must be specified for each object<br />

module in the load list EXEC.<br />

If you place a slash (/) anywhere in the file type list, H<strong>CP</strong>LDR notifies you when<br />

it loads an object module that has the same file type as the one that is to the<br />

left of the slash.<br />

You must use the NOCTL option if you specify file types directly on the<br />

H<strong>CP</strong>LDR comm<strong>and</strong> line.<br />

For example, assume you want to establish the following search order for<br />

H<strong>CP</strong>LDR:<br />

fn TXT1<br />

fn TXT2<br />

fn TXT3<br />

You also want to be notified when H<strong>CP</strong>LDR uses file type TXT1 or TXT2. You<br />

are using the load list <strong>CP</strong>LOAD EXEC. You would enter the following comm<strong>and</strong>:<br />

hcpldr cpload txt1 txt2 / txt3 (noctl<br />

H<strong>CP</strong>LDR<br />

When you enter a list of file types on the comm<strong>and</strong> line, H<strong>CP</strong>LDR does not<br />

automatically look for fn TEXT.<br />

NOCTL<br />

allows you to specify a list of file types to be used in the search in place of<br />

using a control file.<br />

MODULE<br />

requests that the object files be linked together as a module <strong>and</strong> be written to<br />

disk. The file name of the module will default to the name of the loadlist, the file<br />

type will default to MODULE <strong>and</strong> the file mode will default to A. The default file<br />

name, file type, <strong>and</strong> file mode may be overridden by using the FNAME, FTYPE,<br />

<strong>and</strong> FMODE options.<br />

MAP<br />

requests the production of a load map during the loading process. This map is<br />

written in the file loadlist MAP A1. It is a variable length file with ASA carriage<br />

control <strong>and</strong> a maximum record length of 133 characters.<br />

PAGEB<br />

requests the unconditional page boundary be initialized to 4 KB. The lower<br />

three hexadecimal digits of the address are the same as the assembled<br />

address for any single CSECT assembly. Use PAGEB only for systems that you<br />

are testing.<br />

SMALLMAP<br />

requests the production of a smaller version of the st<strong>and</strong>ard load map (MAP<br />

option) during the loading process. The smallmap is written in the file loadlist<br />

SMALLMAP A1. It is a variable-length file <strong>and</strong> contains one line for each csect<br />

that was included. Both MAP <strong>and</strong> SMALLMAP can be specified at the same<br />

time. SMALLMAP cannot be used with the PUNCH or TAPE option.<br />

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

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

Saved successfully!

Ooh no, something went wrong!