Binder Manual (G06.27+, H06.04+, J06.03+)

Using Binder

Binder Manual—528613-004

2-21

Load Maps

Binder can produce separate load maps for data blocks and entry points. By default,

load maps are alphabetical. You can also produce location load maps for entry points

and data blocks. You use the BUILD LIST, SELECT LIST, or LIST commands to

generate these listings.

Entry Point Maps

Entry point maps are load maps that contain storage addresses of code blocks and

entry points of a program.

A code block contains the executable machine code for a routine that is invoked

through a procedure call (PCAL) or an external call (XCAL) instruction and the

procedure entry point (PEP) table.

An entry point is the address or the label of the first instruction that the program or

process executes on entering a program, routine, or subroutine. A program or a code

block can have many different entry points, each corresponding to a different function

or purpose.

Alphabetic Entry Point Load Maps.

Figure 2-3 shows an alphabetically sequenced load map for code blocks and entry

points. The Binder wraps lines if the output line length of your listing is greater than the

record length of the file.

Heap location The type of memory that the heap area is located in.

This entry appears only for Pascal or C files that have

been bound with the Pascal or C run-time libraries,

respectively. The heap location can be extended data

space or regular data space

Heap size Heap size in pages

Top of stack Location of the top of the stack in words

Number of code segments The number of code segments in the object file

Number of Binder

warnings

The number of warning messages issued

Number of Binder errors The number of error messages issued

Elapsed time The amount of time (hh:mm:ss) spent in building the

object file

Table 2-5. Binder Statistics (page 2 of 2)

Statistic Definition