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 Control Statements <strong>and</strong> Output<br />

Table 29. Load Map Contents (continued)<br />

Label Contents for Modules (CSECTs) Contents for Entry Points<br />

(Blank) SD A reference code:<br />

–– The entry point is unreferenced.<br />

.. The entry point is referenced by an<br />

EXTRN but not by any address<br />

constant.<br />

(blank) The entry point is referenced by an<br />

EXTRN with an address constant<br />

(most <strong>CP</strong> entry points fall into this<br />

category).<br />

LOAD The load address of the module The load address of the entry point<br />

ASM The offset of the module name within the<br />

module (for <strong>CP</strong>, this is usually 0)<br />

SIZE The size of the module (Blank)<br />

(Blank) Normally blank. ? if an attempt was made to<br />

define the symbol twice.<br />

The offset of the entry point within the module<br />

Normally blank. ? if an attempt was made to<br />

define the symbol twice.<br />

Load Map Sorted by Address<br />

This report contains the same information as the Load Map Sorted by Name, but it<br />

is sorted by the load address of the module or entry point.<br />

You can use this report to check the starting <strong>and</strong> ending addresses of your<br />

generated system <strong>and</strong> verify that modules were loaded in the correct order.<br />

Other Information<br />

Figure 19 shows an example of the last report from a <strong>CP</strong> load map. It shows:<br />

v The number of failures of any VERIFY loader control statements contained in the<br />

system.<br />

Your system should not have any verify failures. Since VERIFY <strong>and</strong> REPLACE<br />

loader control statements are most often used to replace object code in a text<br />

deck, a verify failure probably indicates an error in the resulting code.<br />

v The number of unreferenced CSECTs <strong>and</strong> their names.<br />

v The relocation summary. The relocation summary shows the number of<br />

references by length (1, 2, 3, <strong>and</strong> 4 bytes).<br />

For <strong>CP</strong>, all of the references are 4 bytes long (AL4s).<br />

NO VERIFY FAILURES<br />

12 UNREFERENCED CSECTS: H<strong>CP</strong>ADP H<strong>CP</strong>CCW H<strong>CP</strong>CHS H<strong>CP</strong>CIO H<strong>CP</strong>DCTCT H<strong>CP</strong>DDP H <strong>CP</strong>DD1 H<strong>CP</strong>DUP H<strong>CP</strong>F<strong>CP</strong><br />

H<strong>CP</strong>GCS H<strong>CP</strong>GCSLV H<strong>CP</strong>GIS<br />

RELOCATION SUMMARY: 24,355 AL4’S<br />

Figure 19. VERIFY Failures, Unreferenced CSECTs, <strong>and</strong> Relocation Summary<br />

SMALLMAP File Information<br />

If the SMALLMAP option is used, H<strong>CP</strong>LDR will produce a file with the following<br />

characteristics. The example given is for a <strong>CP</strong> system <strong>and</strong> Figure 20 on page 1913<br />

shows an excerpt of its contents.<br />

1912 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!