Binder Manual (G06.24+, H06.03+)

Using Binder
Binder Manual—528613-003
2-23
Load Maps
Location Entry Point Load Maps
If you specify a command to display entry point maps by location, Binder outputs an
itemized listing following each map. The listing contains:
•
Code size in words
•
Procedure entry point (PEP) length in words
•
Global P-relative length in words
•
Procedure length in words
•
Gap length at 32K boundary in words
•
External entry point (XEP) size
•
Code area size in pages
•
Resident code size in pages
Figure 2-4 shows the location load map for an object file with multiple code segments.
DATE/TIME Timestamp for compilation of the block
LANGUAGE Source language of the block: TAL, FORTRAN, COBOL85, C,
or Pascal
SOURCE FILE Disk file name of source code for the block
Figure 2-4. Entry Point Map by Location for Multiple Code Segments
TIMESTAMP 1994-03-04 15:18:34
ENTRY POINT MAP BY LOCATION FOR FILE: \NORTH.$USERS.QA.SAMPLE
CODE SEGMENT 00
SP PEP BASE LIMIT ENTRY ATTRS NAME DATE TIME LANGUAGE SOURCE FILE
00 002 000006 000065 000006 SUB1 1994-10-24 11:51 FORTRAN $BUG.QATACL.FORTSUBS
CODE SEGMENT 01
SP PEP BASE LIMIT ENTRY ATTRS NAME DATE TIME LANGUAGE SOURCE FILE
01 002 000006 000067 000006 SUB2 1994-10-24 11:51 FORTRAN $BUG.QATACL.FORTSUBS
CODE SEGMENT 2
SP PEP BASE LIMIT ENTRY ATTRS NAME DATE TIME LANGUAGE SOURCE FILE
02 002 000006 000100 000006 SUB3 1994-10-24 11:51 FORTRAN $BUG.QATACL.FORTSUBS
CODE SEGMENT 03
SP PEP BASE LIMIT ENTRY ATTRS NAME DATE TIME LANGUAGE SOURCE FILE
03 002 000006 000117 000006 CHARASSIGN^ 1994-10-24 11:51 TAL $EM1.T9262C20.FTNLIB2
Table 2-6. Information Included in Load Maps for Entry Points (page2of2)
Label Description