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

Object File Structure
Binder Manual—528613-004
4-11
Data Region
The XEP table is in the last page of each code segment and contains an entry for each
unresolved external reference. The operating system fills in this table at run time.
These unresolved references can refer to entry points in the code or system library, the
FORTRAN or COBOL85 run-time libraries, or to entry points in user library segments.
Data Region
Binder determines the minimum number of pages to allocate for the data area and
reports the number in the output statistics. The data area starts on a page boundary.
Binder also determines the order for data blocks so you need not specify their order
when you define a target file.
Accelerator Region
After you have run a run a file through the Accelerator, the Accelerator region contains
the TNS/R version of the original TNS instructions. If you do not use the Accelerator,
this region is a zero-length record. See the Accelerator Manual for information on the
Accelerator.
OCA Region
After you run a file through the Object Code Accelerator (the OCA), the OCA region
contains the TNS/E version of the original TNS instructions. If you do not use OCA, this
region is a zero-length record. See the Object Code Accelerator Manual for information
on OCA.
Inspect Region
Symbol tables in the Inspect region contain information on all symbols in blocks that
were compiled with the SYMBOLS directive. Because you can turn SYMBOLS on and
off for each procedure, an object file can contain symbol tables for some of the blocks
and not for others.
The space required for symbol tables depends on program characteristics. Space
requirements for the object file can increase significantly when data requirements are
complex. During an interactive Binder session, you can specify whether to retain the
symbol tables in the target file. You should retain symbol tables for blocks that are still
in the development cycle if you plan to use Inspect high-level commands. See the
STRIP Command on page 3-75
Once you delete the symbol tables, you can still use the LMAP command to display the
load map of the stripped file. You can also use low-level Inspect commands and Debug
commands whether symbol tables exist or not. If you need the symbol tables, you must
recompile the file. For information on debugging programs, see the Inspect Manual and
the Debug Manual. For information on LMAP, see LMAP Command on page 3-32