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.

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

Oper<strong>and</strong>s<br />

H<strong>CP</strong>LDR with the TAPE or PUNCH option to generate <strong>CP</strong>, the loader does not<br />

link-edit object modules <strong>and</strong> does not pass control to H<strong>CP</strong>GEN to write the<br />

system on the system residence device.<br />

Issue the H<strong>CP</strong>LDR comm<strong>and</strong> under CMS.<br />

Attention: You should use the <strong>VM</strong>FBLD EXEC to build nuclei. If you use the<br />

H<strong>CP</strong>LDR comm<strong>and</strong>, it does not load any serviced text decks contained in the<br />

nucleus. The H<strong>CP</strong>LDR comm<strong>and</strong> does not support loading text decks by PTF<br />

number.<br />

loadlist<br />

is the file name of the load list EXEC file. It contains the names of the object<br />

files in the order in which they are to be loaded. The load list may look like this.<br />

&CONTROL OFF<br />

&1 &2 &3 H<strong>CP</strong>LDR LOADER<br />

&1 &2 &3 fn [ft]<br />

&1<br />

.<br />

&2 &3 fn [ft]<br />

.<br />

fn <strong>and</strong> ft are the file name <strong>and</strong> file type of an object file. The ft is optional. If ft is<br />

omitted, H<strong>CP</strong>LDR searches the control file or an explicit list of file types to<br />

determine the file type.<br />

H<strong>CP</strong>LDR LOADER must always be the first file. H<strong>CP</strong>LDR loads each object<br />

module in order from the top of the load list to the bottom.<br />

You can place most loader control statements in the load list EXEC file. You<br />

cannot place VERIFY, REPLACE, or INCLUDE CONTROL SECTION<br />

statements in the EXEC file. A loader control statement begins with a 12-2-9<br />

punch (X'02'). Whenever H<strong>CP</strong>LDR encounters X'02' in the first column of a<br />

record, it interprets that record as a control statement. For more information see<br />

Appendix D in the z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong>.<br />

ctlfile<br />

is the file name of the control file.<br />

H<strong>CP</strong>LDR uses the update level identifiers in the control file to determine the file<br />

type for those object modules listed in the load list without file types. The<br />

comm<strong>and</strong> skips the MACS record in the control file <strong>and</strong> searches for update<br />

level identifiers from the top of the control file down. If H<strong>CP</strong>LDR finds an update<br />

level identifier other than TEXT, the comm<strong>and</strong> appends the identifier to TXT to<br />

create a file type, then searches for the file (fn TXTxxxxx). If H<strong>CP</strong>LDR cannot<br />

find an object file that has the first update level identifier, the comm<strong>and</strong> finds the<br />

next identifier <strong>and</strong> continues the search. As a last resort, when H<strong>CP</strong>LDR cannot<br />

find the object file according to update level identifiers, the comm<strong>and</strong> searches<br />

for fn TEXT. For example, if the control file is:<br />

TEXT MACS H<strong>CP</strong>GPI H<strong>CP</strong>PSI H<strong>CP</strong>OM1 H<strong>CP</strong>OM2 DMSGPI DMSOM OSMACRO<br />

SPEC AUX1111<br />

<strong>IBM</strong>1 AUX<strong>VM</strong><br />

H<strong>CP</strong>LDR follows this search order:<br />

fn TXTSPEC<br />

fn TXT<strong>IBM</strong>1<br />

fn TEXT (last resort)<br />

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

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

Saved successfully!

Ooh no, something went wrong!