Program module map

A map of the program module is generated if the MAP option was specified for the run. Figure 1 and Figure 3 contain sample program module maps (one for a simple module and one for an overlay module). Each text class is mapped showing each section or external label on a separate line and INCLUDING information about the source of the section. A "SOURCE" column indicates the data set (by ddname and concatenation sequence number) and member from which each section was included. Map entries are sequenced by module location within class or overlay segment.

The following describes the detailed line information included in the module map:

SECTION OFFSET - The location of the section or label relative to the start of the element (class section) in which it is defined. Section offset is printed only for labels, not sections.
CLASS OFFSET/MODULE OFFSET - The location of the section or label relative to the start of the class or overlay segment.
NAME - The name of the entity being mapped. An asterisk preceding the name indicates that the section was included during the autocall phase.
Some section types do not have external names and are displayed as follows:
- $SEGTAB - Overlay segment table
- $ENTAB - Overlay segment entry table
- $PRIVxxxxxx - Private code where xxxxxx is a unique hexadecimal value starting at X'000001'
- $BLANKCOM - Blank (unnamed) common
TYPE - The label type of the entity being mapped:
- CSECT - Control section
- LABEL - External label
- COMMON - Named or unnamed common
- SEGTAB - Overlay segment table
- ENTAB - Overlay segment entry table
LENGTH - The length in hexadecimal bytes of the section or segment. If TYPE is LABEL, this field is blank.
SOURCE - The ddname, concatenation sequence number, and optionally the member name from which this section is included.

When reporting the source of a Section brought in from an archive file, the Binder Map will be changed to list the name of the archive file member from which the Section was included (in the column headed MEMBER). For symbols resolved via the C370LIB directories, the member name listed will be the PDS/PDSE member name, not the name of the symbol.

The last item in the module map is usually the data set summary. It contains one entry for each combination of ddname and concatenation sequence number referenced in the module map and displays the corresponding data set name. These 8-byte pseudo ddnames are used in the module map and other reports in order to improve the reports' readability. The data set summary cross-references the pseudo ddnames to their corresponding z/OS UNIX file names. A pseudo ddname is of the form '/000000n', where 'n' is a number that increases as new z/OS UNIX files are processed by the binder.

Data sets and libraries from which no members were included do not appear in the data set summary.

If any symbols appear as references in the symbol table (ESD) of one or more input modules, but are not the target of any references in the code, an unreferenced symbol table will be printed. The symbols in this table will not appear in the cross-reference listing but if they are unresolved, may result in error messages being issued by the binder.