MDBS MLINK Manual Dec1983 pdf

%9:

:"9%4,

"Q6' ,9

qG<C <S,

%q,

:

:>'4·>

MDBS

"S' ,^OG

"O,¿j

MLINK

Reference

Manual

(Version

1.06)

Micro Data Base Systems, Inc. P.O. Box 248

Lafayette, Indiana 47902 USA

December 1983

Copyright Notice

This

entire

manual _{is provided for the use of the customer} and the customer's employees. The _{entire contents have been copyrighted}

by _Micro Data Base Systems, _Inc., and _reproduction by any means is prohibited except _{as permitted in} a written agreement with Eicro Data

Base Systems, _Inc.

Trademarks: PÍDBS _is a registered trademark _{of Micro} Data Base Systems, Inc. CP/M _and F'IP/M _{are trademarks of}

Digital

Research. MSDOS _is a trademark of Microsoft. PCDOS is a trademark of IBM.

NEWS RELEASES, VERSIONS, AND A WARNING

Any programming endeavor _of the magnitude of the MDBS _software

will

necessarily continue to evolve over time. Realizing

this,

Micro Data Base Systems, _Inc., vows to provide

its

users with updates to

this

version

for a nominal handling fee. New versions of biDBS software

will

be _{considered as separate products.}

Our _{products have been produced with a very substantial investment of}

capital and _{labor, to say nothing of} the _{years of prior involvement in} the data base management area by our principals. Accordingly, we _are

seriously concerned about _{any unauthorized} copying _{of our} products and

will

take any and

all

_{available legal action against}

illegal

copying or

distribution

of our products.

(C) COPYRIGHT _{1983 Micro Data Base Systems,}

MDBS MLINK MANUAL MDBS MLINK MANUAL

I. _MLINK DESCRIPTION A. Overview

MLINK _{is a}

utility

program that is executable under the _following

operating systems: CP/M, MP/M, CP/M86, CP/M86, PCDOS, MSDOS. When

MLINK _{is invoked,}

it

links together relocatable object modules. MLINK

accepts REL, ERL, and IRL object

files.

The

result is

_{an executable}

f lle.

Under CP/M _{or ¥P/M, this is a} .COM

file.

It

is a .CMD

file

for CP/M86 _or XP/NJ86. _Under PCDOS _or MSDOS, a .EXE

file

is generated.

B. Using MLINK: Batch Mode

Depending on the operating system environment, MLINK is provided on either _{one or} three

files:

KLINK.COM, MLINKI.OVL, ELINK2.OVL under CP/M and P4P/Ni MLINK.CMD _under CP/M86 _and MP/M86

MLINK.EXE under PCDOS _and MSDOS

The two _overlay

files (if

_present) must be on the default drive or

drive A.* To _{execute MLINK,} a command

line

of the

following

form

is

entered:

MLINK

filel

lfile2 file3 ... filekj

where

filel,

file2,

... and

filek

are names of REL, ERL, ar.d/or IRL

f

lies. These must be

fully

_{qualif led fñ-le names.}

If

an extension is

not _{specified for} a _f

lle,

then the .REL _{extension is} assumed.

NÍLINK _{generates two}

files

_{on the} same drive _as

filel:

f

ilel.COW

(o r filel.CMD or filel.EXE) and filel.SYM. The former contains

executable object code; _the

latter

_contains a symbol table.

If

an

alternative

name or drive

is

desired

for

the COM (or crío or EXE) and

SYM

files,

_the -C) _{option can} be _used: MLINK

-Oaltfile

filel

Ifile2

f ile3

... filekj

where

altfile

is

the

alternative

file

_name.

If

_{no exteRsion}

is

specified

for

altfile,

the .COM (.CMD _{or .EXE) extension}

is

_used

for

the linked output

file.

The .SYM _extension

is

_{used for the symbcl}

table.

The _{ordering of}

files

_{in the} command _{line is important}

if

one or more of the

files

is

a

library

of object modules. The

files

_are

processed in the order given on the command

line.

Since PILINK

satisfies

forward references, a n

external

reterence _must b e

unsatisfied

when Ñ1LINK _{searches the}

library

_{containing the object}

module

for that external.

In other words, the

library

file,

containing an external that

is

referenced in another

file,

should

follow that other

file

in the ccnomand _line.

MLINK _{performs selective}

linking

_with a

library

file

when _the

library

file

name is prefaced with -L. Only those object modules irí

the

library

file

_{that are required to satisfy} undefined ex,ternals

will

be _{linked. For instance,} MLINK

f

i1e1 _-Lfi1e2

generates the linked filel.COM

(filel.c6!lj

or

filel.EXE),

which doe:z not _include any object modules front

f

_{ile2 that are} not _{referenced in}

f

ilel.

*In looking for an _overlay

file,

the _{current user area of} the _default

drive is searcheá

first.

If

it

_is not founá then _drive A

is searched

(if

user areas are supported, then only user area O

of drive a _is

searched) _.

MOBS MLINK MANUAL

-

I.

MLINK DESCRIPTION - MOBS MLINK MANUAL

Several _{other optional} arguments can be includeá on the command

line. As _{noted in the following descriptions, some of these arguments}

are pertinent only

for

certain operating systems or programming languages.

-Ahhhh where hhhh

is

a hex number that specifies _the

address where _the

linker's

_output

file

is

_to be loaded. When _{this optional argument is omitted a}

load address of lOó hex _is used. _{This argument} can be used only under CP/M or MP/M.

-A<hhhh where hhhh

is

a hex number that specifies the

address below which MLINK's _output

file

is

_to be

loaded. After MLINK _{determines the size of the}

object program to be _{generated, MLINK assigns a}

starting

address (on a 256 byte boundary) such

that the program

will

reside below hhhh. This argument can be _{used only under} CP/bl _or MP/M.

-B This option

is

used when

linking

_{an overlay.}

It

tells

the _overlay lQaaer _{that the overlay}

is

_not

to be _{re-loaded at run time}

if it

is

already in

memory.

-C This option causes a "compact" output

file

to be

produced by

first

_assigning

all initialized

program, common, and data seqments.

It

_then assigns

all uninitialized

_program, common and data

segments. _{Uninitialized} segments _are not _written

to the output

file.

This option can be used only

under CP/M _or MP/M _and

it

may cause improper

operation of code produced by _{certain compilers.} -E This option must be _specified when

linking

C'

programs.

It

inserts ?CRT0 (C' runtime startup

module) _{into the} symbol _{table as an}

unsatisfied

external. This option must be _{specified before}

LIBC

is

_searched. -E does _not have _to be

specified when _linking C' _overlays.

-Esymbol _{where symbol}

consists

_{of from one to}

six

characters. This option has _the

effect

_of

inserting

the indicated symbol _name

into

_the symbol _{table as} an undefined external.

-Esymbol=hhhb where _symbol

consists

_{of from one to}

six

characters and hhhh _is a hex address. This option

_

defines the _indicated symbol _to be an _{entry point}

with address bhhh.

-Iincfile

where

incfile

_{is the name of} a

file

containing _one

or more KJLINK _arguments.

All

_{arguments from}

incfile

are included in the command line in place

of the

-I

argument. The _{contents of}

incfile

_are

free form and can extend over many

lines.

MLINK arguments _in

incfile

are separated by blanks. Any

line in

incfile

that begins _with a semi-colon (;)

is

ignored by MLINK. The

-I

argument can be nesteá _{within any}

incfile.

MDBS MLINK MANUAL

-

I.

MLINK DESCRIPTION - MDBS MLINK MANUAL

-R _{This option} must be _{specified when}

linking

_the

"root"

file

of an overlayed _program. Note _that

this argument must occur before the search of the

library

containing the overlay loader (?OVLD). For _{any language} other than C', _{this means that} -R must precede -LOSCPM _{(under CP/E, MP/M),} -LOSCPM86

(under CP/M86, MP/M86), _or -LOSMSDOS _(under PCDOS, MSDOS).

-Rffff

This option must be _specified when

linking

an

overlay.

ffff

indicates the name of the "root"

file

and

its

symbol _table

file.

_This argument must occur before any -L arguments.

—Sstring where

string

_is a _sequence of characters. This

option _{suppresses the}

writing

of any symbol (to

the symbol

table

file)

that

begins with a

character in the _indicated

string.

For _instance, -SS? _{suppresses the}

writing

_{of any symbols} beginning _with ?

or $.

If

no

string

is specified, a _{new symbol} table

file will

_not be _createá.

-Uhhhh where hhhh _is the address given _to

all

_unsatisfied

externals at the end _of pass

I.

If

hhhh

is

omit-ted, each _{unsatisfied external is given} a unique

address _{outside any areas} assigned by the _linker. -V _This

is

a toggle that _causes 9LIFK to alternate

between verbose mode _{and terse mode. Verbose} mode

causes MLINK _to

display

_{the nature} of

its

processing as

it

executes. The

first

_{use of} a -V

option turns on the verbose mode, the second -V turns

it

off,

the

thirá

-V _turns

it

on", _etc.

-X This _{option suppresses} the _{automatic generation of}

a jump to the transfer address that _{may occur at}

the beginning of the _output

file.

-Xhhhh where hhhh

is

a hexadecimal number. _{This option}

defines the _transfer address (the address _at which program execution begins: ?XFER?) _to be _hhhh.

If

this

option _appears before modules

with

the transfer aádress, then hhhh _overrides the _transfer address _{specified in} these modules and MLINK

will

issue a multiple ?XFER? _{definition diagnostic.}

-Ystfile

where

stfile

is

a ZSID _type symbol _table

file.

This option enters the symbols _from

stfile

into

MLINK's symbol _table.

-Z _{This option}

initializes

_(to O)

all

uninitialized

areas on the output

file

generated by MLINK.

MDBS MLINK MANUAL

-

I.

MLINK DESCRIPTION - MDBS MLINK MANUAL Unless otherwise noted, the optional arguments can be used in any

order. For _instance:

NLINK -V -A0200 -OC:PRG PRG -LNDBSL _-U C. _{Using MLINK: Interactive} Mode

To _execute MLINK _in

interactive

mode, a command

line

of the

following forní _{is entered:}

MLINK

The _{following response is displayed:}

Interactive mode: _enter MLINK _arguments. To

start

_{pass 2, enter} a

null line.

>

The > _{symbol is the interactive} mode _{prompt. Any argument that can} be

used _{in regular mode can also} be _{used in}

interactive

_{mode. However,}

since interactive mode _{is normally verbose, the}

first

-V

will

_turn

off

the _{display of} verbose _messages, the second _{-V causes} verbose _messages

to be _{displayed again, etc.} To

exit

_the

interactive

_{mode of MLINK,}

press the carriage return in response to an interactive mode prompt. D. MLINK.Operation

MLINK _is a two-pass _{linker that} processes the command line in a

left

to

right

fashion. The

first

_{pass constructs the} symbol

table,

containing entries for each _{of three types of segments: program} segments, common segments, and data segments. 14LINK _{determines the}

size of each segment and assigns an absolute address _to each. When

determining the _{size of} a segment, _{the largest}

definition

_{of that} segment _is used _{(multiple definitions} of common segments are legal). Program segment addresses _are assigned

first,

common segments are then

assigned (blank common,

if it

is used, is the

first

of these common segments), and data segment addresses _are assigned _last. MLINK _then

passes through the symbol table to resolve

all

entry points, by

trans-forming

offsets into

absolute addresses. The second _pass examines needed

files

and _object modules _to generate _{executable object} code.

Appendix B _{shows the minimal MLINK command}

line

_arguments

for

programs in various languages.

At any time during MLINK execution (batch or interactive), MLINK

can be aborted by typing Control-C or Escape.

MDBS MLINK MANUAL

-

I.

MLINK DESCRIPTION - MDBS MLINK MANUAL

E. Overlays

The

initial

executable

file

generated by MLINK _{is called the root}

file;

it

has a .COM (.CMD _{or .EXE) extension. The overlay}

files

generated by MLINK _have .OVL _extensions.

Dürinc _{execution of your linked} program an invoked overlay

file

must be _{on the}

default

_{drive or drive A.* The overlay loader}

will

load the specified

file

(e.g., OVER) _and

initiate

execution of the

first

routine

in

that

file.

Therefore,

for simplicity,

it

is

advisable to give _{this routine} the same name that the overlay

file

has

(e.g., OVER).

l.

Single-Level Overlay _Structures

Overlay Structure Memory Layout

ROOT

——"--—-—---——-—— — ROOT

present at all times

either OVERI, OVER2,

·.· _{____-_-} Overlay OVER3_{is present}... or_atOVERn_any

OVERI : OVER2 i OVER3

... OVERn

!

moment

L

Durinc _execution, the _{root is} always _resident. Overlays _are

loaded as requireá, with each overlay

overwriting

the previously resident overlay. Thus _{overlays are} convenient

in memory constrained environments, where the

total

program

length exceeds the _{available memory.} Such a _{program can} be

segmented _into a root and a _group of overlays, no two _of

which need _to be _{resident simultaneously.} When _MLINK

detects a

call

_in the _{root for} an overlay (e.g., OVER),

it

generates a

call

_{to the overlay} loader ?OVLD. _{Examples of} how _{to use} MLINK _{for handling overlays in various languages}

are shown in Appendix C.

* _{In locking for} an overlay

file,

the _{current user area} of the _default

drive

is

searched

first.

If

it

is

riot found then drive A _{is searched}

(if

user areas are supporteá, then only user area O

of drive A _is

searched).

MDBS MLINK MANUAL

-

I.

MLINK DESCRIPTION - MDBS MLINK MANUAL

2. _Multi-Level Overlay _Structures

Overlay Structure Memory Layout

ROOT

—--- - —

- —

-- --- — ROOT _{present at} all times

_.__

aoverlayLevel l oneoverlaysof the Levelis present

l

i)

.

..

at any moment

e OVERI OVER2 OVER3 OVERn _a Level 2 _a Level 2 overlay

I . . overlay that is subordinate

I . . to the current Level

. · . l overlay is present

))0VERla

OVERlb OVER3a OVER3b

OVERÍ,""

:

2

Q 4 e 0 *

a Level _n overlay — a Level n that is subordinate

overlay to the _{current Level}

n-l overlay is present

i

MLINK imposes _{no maximum on} the number _{of levels in an}

overlay structure. During execution, the root

is

always resident. At any given moment, one overlay frorn each level

in the _{overlay structure} can also be _{resident. The overlay}

that is resident for

a

particular

level

_wast be a

subordinate of the _{next higher}

level's

_{resident overlay.} For example, OVERI _must be _{resident before} OVERla _{or OVERlb}

can be invoked during execution. Dynamic metnory allocation

occurs when overlay

files

generated by MLINK are loaded,

thereby avoiáing excessive _{memory requirements.} Thus, OVER3

inay be _{very large} corrlFared to GVERI _while

its

subordinate overlays are small

relative

to those of OVEP.l. Appendix C

shows examples _of MLINK usage for handling

multi-level

overlays in various languages.

MDBS MLINK MANUAL

-

I.

MLINK DESCRIPTION - E4DBS KLINK MANUAL

3. Overlay Load _Errors

As ?OVLD _{attempts to load an overlay,}

it

can detect any

of three possible _errors. The _{diagnostics issued} by ?OVLD

and an explanation of each appear below.

Overlay error on file.OVL : incompatible overlay

?OVLD _{attempted to load the}

indicated

_file.OVL. However, the _{copy of file.OVL presently} on the default

drive is incompatible with the _{version of} the _root (or

a higher

level

overlay) that is being executed.

If

file.OVL does _not

exist

on the

default

drive, then the

file.OVL on drive A _{is inconsistent with the executing}

root.

Overlay _{error on file.OVL} :

file

not accessible

The _{indicated file.OVL is not presently on either the}

default drive or drive A.

Overlay _{error on file.OVL} : read

error

When ?OVLD _{attempted to load file.OVL ar.}

error was

detected while loading a header, data, _or code _area of

file.QVL. This may be caused by a disk read _error.

It

may also be due to a _{corrupt copy} of the file.OVL

(e.g., due _to bad _media).

For non-C' _programs, the _{program exits to} the _operating system _after the _{diagnostic is displayed.} Fcr a C' _program

the diagnostic is displayed. Then, a signal SIG_OVL is

generated which can be _{trapped by the} C' _{program (see the}

signal function in the C'

library),

_{but which cannot} be

ignored.

If

the pro¢ram attempts to ignore

it,

control returns to the _operating system.

MDBS MLINK MANUAL

-

I.

MLINK DESCRIPTION - MDBS MLINK MANUAL

F. _{Miscellaneous} Notes _for Advanced MLINK _Uságe

l.

If split

I&D

(instruction

and _{data areas) is permitted} by the _operating system, then MLINK _{generates executable}

split

I&D

files.

2. The _{value of} ?NEXT? _{is the}

first

free memory data address

(in hex).

If split

I&D is permitted then the value of

?NXTC? _{is the}

first

free memory code address (in hex).

3. The _{value of} ?XFER? _{is the address (in hex) where execution}

of the _{linked program}

will

begin. _{This is either} a transfer

address specified in one of the .REL

files

or the lowest

code-relative reference point.

If

there is no

transfer

address and no code-relative entry points _are defined, then ?XFER? _{is undefined.}

4.

If

.END. _is an

unsatisfied

external reference at the end of pass

l,

then

it

is

set to ?NEXT?.

5. A _{program being}

linked

_{can define three}

entry points

(?MEMRY, $MEMRY, _{.NEXT.) which are treated}

specially

_by

MLINK. At the end of _pass 2, M-LINK _{puts the value of} ?NEXT?

into

the word

existing

_{at any of the three special entry}

points.

6. For IRL

files,

KLINK _skips the IRL header.

MDBS MLINK MANUAL MDBS MLINK MANUAL

II. MLINKMESSAGES

A. Normal _Operation Messages

The _following messages can appear in the course of normal P!LINK

operations:

MDBS MLINK _Vl.xx (XXX)

(C) COPYRIGHT _1983, Micro Data Base Systems, _Inc.

Lafayette, IN 47902

Appearance of _{this message}

identifies

the _{version of} MLINK

and _{indicates that} MLINK _{has successfully begun to execute.}

nn overlays called

The -R _option was specified, and the entry points

listed

were not defined in

this link.

Calling to one of these

entry points

will

execute a linker generated

implicit call

to the _{overlay loader.}

Xfer = hhhh

Execution of the _{linked program}

will

begin _at address bhhh

(hex). This mes'sage appears only when a transfer address

has been _{specified in} a relocatable

file.

ijrg = hhhh

The

first

address _of the _output

file

_is hhhh _{(hex). This} message _occurs when

linking

overlays or when the -A<hhhh argument _is used.

If

_using the BASCOPI _{chaining features,}

this is

the address at which _{blank common begins}

(i.e.,

_the address _{specified in} the BCLOAD

file).

Next = hhhh The

first

free memory address (following those assigned to

program, common and data segments)

is

hhhh (hex). This message indicates the end _of MLINK'S

first

_pass.

ffff

linking complete.

This rriessage indicates that the linker has _{finished without}

encountering errors which would _abort the

link.

Some

non-fatal

errors may have beer, encountered.

ffff

is the name _of

-the _output

file

_created by MLINK.

MDBS MLINK MANUAL

-

II.

MLINK EJESSAGES - MDBS MLINK MANUAL

B. Verbose Mode _Messages

When _{the -V option is used to toggle verbose mode, the following}

kinds of verbose mode _{messages may} be _{displayed in addition to normal}

messages described above.

Code _{= hhhh}

The

start

_{of the area that holds}

all

_{modules' program} segments _is hhhh (hex).

Common _{= hhhh}

The

start

_{of the area}

that

_holás

all

_{modules' common} segments _is hhhh (hex).

Data = hhhh

The _{start of the area that holds}

all

_{modules' data segments}

is

hhhh _(hex).

ffff:

The name of a

file (ffff)

and

all

modules selected from

ffff

are displayed. For each

file

this

_{display occurs once}

during the

first

pass scan and once during the second pass

link.

Initialized

Uninitialized

These _messages precede the Code, Common, _{and Data messages}

for their respective areas. See _the -C _{argument in Section}

i-b

of _this manual. nn Modules:

nn (decimal) modules have been selected for linking from the

specified

file.

nnk table space used:

nn (decimal) K bytes has been dynamically allocated by FiLINK

for buffers and _tables.

MDBS MLINK MANUAL

-

II.

MLINK MESSAGES - MDBS MLINK MANUAL

C. MLINK _{Error Messages}

If

an _error occurred in a

particular

file

(rather than in the

command _line), then the _{error message is} prefaced by the name of that

file:

ffff:

If

such an _error occurred in a REL, _{erl or IRL}

file,

_{then the affected}

module's name

(if

known) is displayed in square brackets

after

the

file

name and before the _message

itself.

ffff:

lmodule: ínmmml

The _{possible error messages are} shown _below. Note _that some

errors are

fatal,

while others are non-fatal. Processing is aborted and _{the user is returned to} command mode _{in the event of} a

fatal

error. Processing continues for non-fatal errors. When processing halts, the _message

nn Errors

appears, where nn _is the number _{of error} messages NILINK _{issues during}

the

link.

-A: bad address _non-fatal

The A _{argument did not contain} a hexadecimal number _or the

number _contained a bad

digit.

The argument is ignored and

linking continues.

Address _outside seg-desc segment _non-fatal

A _{byte outside of the segment currently being worked on was}

initialized

or there is a reference to an address outsiáe of

the segment. The _{segment is indicated by seg-desc which is}

either: code, data, _or a common block name enclosed between

/

and

/.

_Generally,

this

_{condition is} caused by

incorrect

assembler or compiler operation (or by a corrupt REL

file)

aná

it

typically

produces _{unpredictable results.}

Bad argument _{-z non-fatal}

-z is not a valid MLINK _{argument and is ignored. Processing}

continues. See _{section I-B of this manual for a description}

of valid MLINK _arguments.

Bad _{header non-fatal}

The header _{on an IRL}

file

_{was not of proper format. This}

usually indicates a _{corrupt IRL}

file.

On _CP/Pi,

this

_may

have been caused by copying the

file

_with PIP _without using

the O

option of PIP. This

file

is

ignored and

linking

continues.

(C) CC)PYRIGET _{1983 ¥icro Data Base Systems, Inc.}

MDBS MLINK MANUAL

-

II.

MLINK MESSAGES - MDBS MLINK MANUAL

Cannot _load address _{xxxx non-fatal}

The

"pecified

address _xxxx

is

_{lower than the}

origin

_{of the}

output

file.

This load _is ignored and _{linking continues.}

Can't create output

file

fatal

Under CP/M,

tbis is generally

_caused by a

full

disk

directory.

In rare instances,

this

is

caused by

insufficient

memory.

Can't create symbol _table

file

fatal

Under CP/M,

this is generally

_caused by a

full

disk

directory.

In rare instances,

this

is

caused by

insufficient

niemory.

Can't load

ffff

fatal

Overlay

file

ffff

was not present (see _{section I-B of}

this

manual) _or could not be _read.

non-fatal (pass

l)

Can't open

ffff

fatal

(pass 2)

The _specified

file

ffff

_{could not} be _{read. This}

results

from a non-existent

file,

_{an error} in the

file

_{name, or} in

rare instances,

insufficient

memory (this occurs when

inyit

buffer space cannot be _{allocated). This}

file

is skipped aná

linking

continues (during pass

l).

Can't open root

file

fatal

When _{attempting to}

link

an overlay, the _root

file

specified

with

-Rffff

coulá not be _{opened for read/write access.}

Chain _too long

fatal

An _{external or} aCdress _chain exceeded 1000 _{items. This}

indicates a _corrupt REL

file

or more than 1000 references to

a given external within a particular module.

Code _{size redefined non-fatal}

píere tharí _one code _{size declaration was encountered in} the

sFecified module, _generally a _corrupt REL

file.

The _largest

definition

is used and _{linking continues.}

Common _{block /bbbb/ size} mismatch _non-fatal

PiLINK _encountered a

definition

of the specified _common

block, bbbb, _smaller than the _{largest defir,ition specified}

for that common block. ¥LINK uses the largest.

EIDBS MLINK MANUAL

-

II.

MLINK MESSAGES - MDBS MLINK MANUAL

Data _{size redefined} non-fatal

More than one data size declaration was encountered in the

specified module, _generally a corrupt REL

file.

The largest

definition

is used and _{linking continues.}

—E: _{name required non-fatal}

A _{symbol name did not immediately follow the} E

argument.

The argument _{is ignored} and _{linking continues.}

End _of

file

unexpected _non-fatal (pass

l)

fatal

(pass 2) The _{end-of-file marker occurred within module} mminm on

file

ffff.

This _{is usually} an indication that this

file

has been

corrupted. On CP/M,

this

may have been caused by copying

the

file

with PIP _{without using} the O

option of PIP. _This module _is ignored and _{linking continues (during Fass}

l).

*** FATAL ERROR _m'*

fatal

MLINK _{is aborting upon encountering} a

fatal

_error.

Insufficient

memory

fatal

PÍLINK _{requires more memory to construct}

all

_{tables required}

by _this

link.

*** INTERRUPTED **:

'

fatal

É4LIK'K

is

_{aborting because the Control-C key or Escape key} was pressed.

Kultiple

definition

— _ssss non-fatal

Entry point ssss is multiply defined. The

first

definition

is used and _{linking continues.}

Multiple

definition -

?XFER? _non-fatal

flore than one transfer address defiriition was encountered. The

first

definition

_is used and _{linking continues.}

MDBS MLINK MANUAL

-

II.

MLINK KESSAGES - MDBS MLINK MANUAL

No common block selected

-

ssss non-f atal

An _{attempt was} made _{to define} an _entry point _ssw3

into

a common block without

first

selecting the common _{block. This}

geneíally indicates a corrupt REL

file.

"Absolute" mode is

used _{for this reference} and _{linking continues.}

No _{modules linked}

fatal

The

link directives

_{did not specify}

linking

_{of any} modules

which coulá be _properly accessed by _the

linker.

_This

is

usually due _{to the}

fact

_that one or more of the

files

specified could not be opened _(in

this

_case

this

_message would be _preceeáed by

error messages specifying those

files

which _could not be _{opened). The}

linker

_{aborts without}

creating a new _{output or} symbol f

lle.

No _{output file-name}

f

_atal

No _output

file

naine was specified by _the

directives.

If

this occurs, the O

option must be _{used to specify a name.}

Overlay _{error on MLINK1.OVL or} MLINK2.OVL : incompatible overlay

f

atal

?OVLD _{attempted to load the}

indicated

MLINKI.OVL _or PiLINK2.QVL. However, _the copy of MLINKI.OVL or NLINK2.OVL

presently on the default drive is incompatible with the version of the root that

is

being executeúú.

If

MLINKI.OVL or É4LINK2.OVL _{does not exist on the default drive, theri the}

MLINKI.OVL _or L'1LINK2.QVL _{on drive} A _{is inconsistent with the}

executing root.

Overlay error on P'LINKI.OVL or I'ILINK2.OVL :

file

not _accessible

fatal

The _indicated ¥-LINK1.OVL _or MLINK2.OVL

is

_{not presently on}

either the _{default drive or drive} A.

Overlay _error on MLINKI.OVL or MLINK2.OVL : read _error

fatal

When ?OVLD _{attempted to load MLINKI.OVL or 6JLINK2.OVL an}

error was detected while loading a header, data, _or code area of file.OVL. This may be caused by a disk reaá

error.

It

may also be due to a _{corrupt copy of} the M-LIP'KI.OVL _or R1LINK2.OVL _(e.g., due _to bad _media).

Read _{error non-fatal (pass-l)}

fatal

(pass-2)

This indicates that the _specified

file

is

_{corrupt. This}

file

is skipped and _{linking continues (during pass}

l)

.

Read _{error on output}

file

fatal

An _{error occurred when attempting to "page-in" a part of the}

output

file.

This should not _occur.

MDBS MLINK MANUAL

-

II.

MLINK MESSAGES - MDBS MLINK MANUAL

Syntax _error non-fatal

The _specified

text

file

_{contained improper syntax.} For

instance, when

linking

a EASCOM _program the syntax of the BCLOAD

file

was

incorrect.

Consult the language manual

(e.g., BASCOM) _{for correct syntax.}

nn Unsatisfied externals non-fatal

No _{entry point}

definitions

_{were found for} the _specifieá

externals (a

list

of names

follows this

message). This is

usually caused by _missing or misnamed subroutines, or by

out-of-crder libraries.

If

the -U argument was not used,

MLINK _{automatically enters} the _interactive mode, _displaying the _message

Type "C _{to abort, or} CR _to

start

pass 2, or enter further MLINK _{arguments now:} >

Typing Control-C aborts processing. Pressing the carriage return causes

all

unsatisfied externals to be _{given an}

address of _zero and

linking

_{continues. Therefore, during}

execution,

calling

such a routine

will

result

in a

call

to

address _zero (under CP/M _or 61P/M _{this causes the program to}

exit).

Version mismatch

fatal

One _{or more of the ¥LINK overlay}

files is

_{not of the same}

version as the HILINK _{root. Kake fresh copies of the} IGLINK

root and _overlay

files

from the _{distribution disk to ensure}

a _version match.

Write error on output

file

fatal

Under _{cuu., this is generally} caused by a

full

disk.

Write error on symbol table

file

fatal

Under CP/M, _{this is generally} caused by a

full

disk.

MDBS MLINK MANUAL

-

II.

MLINK MESSAGES - MDBS MLINK MANUAL

This _{page intentionally}

left

_blank.

Do _{not purchase or otherwise accept} MDBS

III

software products not bearing the

official

colored MDBS

diskette/tape

_{label. The}

serial

number on the label uniquely

identifies

the system _licensee.

If

you are approached by a _{person or} organization attempting _to

illegally

C!istribute KDBS _{products, please contact}

Micro Data Base Systems, _Inc. P.O. Box 248

Lafayette, IN 47902

(317) 448-1616 Telex 209147 ISE UR

We

appreciate your assistance in preventing software piracy.

Sample _of MDBS

III

diskette/tape label:

MDBS III Z80

e,:

Ácro

~~

Data6asc ó _:

SU5fcm5,tnc.

.OAOX2U LAFAYETTE,IN 47902

©COPYRÍGHT1981 SERIALNC)

9DBS MLINK MANUAL MDBS MLINK MANUAL

Appendix A

Relocatablé

Ob

ject

File Format

MDBS MLINK MANUAL MDBS MLINK MANUAL

Appendix a

Microsoft REL _is a format for RELocatable object

files,

usually

used

for

8080/z80 _object code unáer CP/M.

It

is

a

bit-stream,

which

means that the

linker directives

(here _{called items) occur} on

bit

boundaries, _rather than byte or word boundaries (except _for a couple

of special items mentioned _later).

BElQcatahle-Qkject_Eile-EQtwak:

Each _{item in the}

bit

_{stream consists of} a header

bit(s),

and

depending on the item type, other

fields

(expressed here _in BNF

grammar):

byte :₌

bit bit bit bit bit bit bit bit /*

8 bits

*/

word :₌ byte byte

/*

low byte

first

*/

/*

address

field */

a-field

:₌ O O word l

/*

absolute */

O

l

word l

l*

code-relative */

l

O _word l

l*

data-relative */

l l

word

l*

common-relative

*/

l*

name

field

_*/

b-field

:₌ O O O I

/*

header bits _are name char count _*/

O O

l

byte l O

l

O _{byte byte} l O

l

l

byte byte byte l

l

O O _{byte byte byte byte} I

\,i

O

l

byte byte byte byte byte I

l l

O _{byte byte byte byte byte byte} I

l l l

byte byte byte byte byte byte byte

filler

:₌ (null) l

bit

l*

enough bits to force next item */

bit bit

l

/*

to byte boundary

*/

bit bit bit

I

bit bit bit bit

l

bit bit bit bit bit

I

bit bit bit bit bit bit

I

bit bit bit bit bit bit bit

Given

all this,

the _{definitions are:}

REL

file

:

= L_ENDF i _{module-group L_ENDF}

module-group :_{= module} l module module-group

module :₌ L_EPRG ! item-group L_EPRG

item-group :₌ relitem l relitem item-group

reliteríí :₌ L_ESYM l L_SCOM I L PNAF1 I —

L_LSCH l _{L_DCCN} l _{L_CEXT} j

L_DENT l _{L_MOFF} l _{L_POFF} I

L_DSIZ i _{L_SLOC} l _{L_CADR} I

L_PSIZ I _{L_EPRG} { _{L_ENDF} l

L_WORD i _{L_BYTE}

(C) COPYRIGHT _{1983 Eicro Data Base Systems,}

MDBS MLINK MANUAL MDBS MLINK MANUAL

L_ESYM _{"entry symbol"} :₌

l

O O O O O O

b-field

(b-field

is name of entry point contained in

this

module. Th

i

s

item is used _during

library

searches _{to determine whether}

this

module _satisfies an _{unsatisfied external.)}

L_SCOM _"select COITllñQñ block" _:

=

l

O O O O O

l

b-field

(b-fielá

is the name of a common block _to use for common-relative

references after this item.)

L_PNC,M _"module name " :₌

l

O O O O 1 O

b-field

(b-field

is the name used by LIB _to

identify

the module. _Note:

P _stands

for program, but this really means module.)

L_LSCE1

"library

_search

file"

:₌

l

O O O O

l l

b-field

(b-field

is the _{name cjf} a REL

file

to be _searched

after all

_the

linker directives

are processed

if

there are

still

unsatisfied

externals.)

L_DCOM _"declare common block" :₌

l

Q O O

l

O

l

a-field b-field

(b-field

is the name of a _common block whose size is specified by

the

a-field

(the mode _{is ignored).)} L_CEXT _{"chain external"} :

=

l

O O O

l l

O

a-field

E-field

(a-field

is the head address cjf the chain, arid the

b-field

_is the

name of the _{entry point} whose acidress is to replace into each

member _of the _{chain (chain is terminated} by an absolute _zero

entry.)

L_D£NT _{"declare entry point"} :

=

l

O O O

li

l

a-field

b-fielR

(b-field

is the name of _{an entry} point, and

a-field

is i t

s

address.)

L_ MOFF _{"External - offset"} :

=

l

O O

l

O O O

a-field

(a-field

is

offset

to be _{subtracteCi from value at}

this

_address,

after

all

chaining has been done.)

L_PCJFF _"External + offset" :₌

l

O O

l

O O

l

a-field

(a-field

i

s

just

like

i

n L_ MOFF, b u

t

added _instead o

t

subtracteá.)

MDBS MLINK MANUAL MDBS MLINK MANUAL

L_DSIZ '4jata _{area size"} :₌

l

O O

l

O

l

O

a-field

(a-field

is data area size, mode is ignored.)

L_SLOC _{"Set loading location"} :₌

l

O C

l

O

l l

a-field

(a-field

specified the location of the next byte/word

is

to loaded.)

L_CADR _{"Chain address"} :₌

l

O O

l l

O O

a-field

(a-field

is starting

address of chain, and _{present loading}

location

is

to replace

into

each member _{of the chain (chain}

is

terminated by an absolute _zero entry) .)

L_ _{PSIZ "Module size" :}

=

l

O O

li

O

l

a-field

(a-field

is module _{code area size,} mode _{is ignored.)}

L_ EPRG _{"Module end, with transfer address"} :₌

l

C O

Ill

O

a-field

filler

(a-field

is the _transfer adáress; _absolute zero means no transfer

address.)

L_EN1)F _{"End of}

file"

:₌

l

O O

Ill

l

L_BYTE _"Load a byte" :₌ O byte

L_WORD _{"Load a word" :=}

l

O

l

word

/*

_{code-relative}

*/

In a RELITEM,

"ri_

_type"

is

the _{item type,}

"ri_val"

_{is the}

a-field

(address

f

_ield)

if

the item _{has one,}

"ri

_mode" is the address mode of

the

a-field,

and

"ri_

name" _is a null-terminated _{array containing} the

b-field

(name

field)

if

the item _{has one.} For the _cases of L_BYTE _and L_WORD, _{"ri_val" is the byte/word value, with "ri_moáe" the addressing} níode _for L_WORD.

MDBS MLINK MANUAL MDBS MLINK MANUAL

Appendix B

Minimal MLINK

Command

Line Arguments

(C) COPYRIGHT _{1983 Micro Data Báse Systems,}

MDBS MLINK MANUAL MDBS MLINK MANUAL

Appendix B

PROG _{is the} name of a

file

holding the _program to be linked.

Assewkl¥-LangRage

MLINK PROG

C:_CQInE?il¢L

MLINK -CE PROG

EáSCQLLizáQ

NLINK PROG _-LBASLIB

CEz8Q

MLINK POG _-LCB80.IRL

CQEQLz8Q

NILINK PROG _{-LCOBLIB -LTDRIVER}

EQRTEAN: :8Q

ELINK PROG _-LFORLIB

EbscbL_KT+_CQwpilet

MLINK -ZX PROG.ERL -LPASLIB.ERL

PLIz8Q

MLINK PROG _-LPLI80.IRL

MDBS MLINK MANUAL MDBS NLINK MANUAL

Appendix C

Using

MLINK with Overlaying

MDBS MLINK MANUAL MDBS MLINK MANUAL

Appendix C

ássemhly-LangRage

Single-level overlays:

MLINK _-R ROOT LOSCPM MLINK _-Z -RRQOT OVERI MLINK _-Z -RROOT OVER2

Multi—level overlays:

MLINK _-R ROOT -LOSCPM MLINK -RROOT OVER1 MLINK -RROQT OVER2

MLINK -RROOT -YOVER2 OVER2a MLINK -RROOT -YOVER2 OVER2b

MLINK -RROOT -YOVER2 -YOVER2b OVER2bx MLINK -RROOT -YOVER2 -YOVER2b OVER2by

C!_Ccmpilet

Single-level overlays:

MLINK -CE -R ROOT MLINK -RROOT OVERI MLINK -RROOT OVER2

Multi-level overlays:

MLINK -CE _-R ROOT FILINK -RROOT OVERI MLINK -RROOT C)VER2

F1LINK -RRCOT -YOVER2 OVER2a MLINK -RROOT -YOVER2 OVER2b

MLINK -RROOT -YOVER2 _-YOvER2b OVER2bx MLINK -RROOT -YOVER2 -YOVER2b OVER2by

EQETEANxEQ

Single-level overlays:

FÍLINK _-R ROOT.ERL _{-LFORLIB -Loscppi} MLINK -RROOT _{OVERI.ERL -LFORLIB} MLINK -RROOT OVER2.ERL _-LFORLIB

RASCAL_MT±-CQwpilet

Single-level overlays:

EILINK -ZX -R ROOT.ERL PINI.ERL -LPASLIB.ERL -LOSCPM MLINK -Z -RRCOT OVERI.ERL -LPASLIB.ERL

MLINK _-Z -RROOT OVER2.ERL _-LPASLIB.ERL

Multi-level overlays:

MLINK _{-ZX -R} ROOT.ERL _{PINI.ERL -LPASLIB.ERL} -LOSCPM MLINK _-Z -RROOT _{OVERI.ERL -LPASLIB.ERL}

MLINK _-Z -RROOT OVER2.ERL _-LPASLIB.ERL

MLINK _-Z -RROC)T -YOVER2 OVER2a.ERL _-LPASLIB.ERL MLINK _-Z -RROOT -YOVER2 OVER2b.ERL _-LPASLIB.ERL

MLINK _-Z -RROOT -YOVER2 -YOVER2b OVEP.2bx.ERL _-LPASLIBERL MLINK _-Z -RROOT -YOVER2 -YOVER2b _{OVER2by.ERL -LPASLIB.ERL}

DOCUMENTATION COMMENT FORM

MDBS _Document

Title:

We _{welcome and appreciate}

all

_{comments and suggestions that can}

help us to improve our manuals and products. Use

this

form to express your views concerning this manual.

Please do _{not use}

this

_{form to report} system _problems or to request materials, etc. System _{problems shoulá} be _{reported to}

MDBS _{by phone or telex, or in a separate}

letter

addressed _to the

attention

of the _{technical support}

division.

Requests _for

published materials should be _{addressed to the attention of} the

marketing division.

Sender:

(name) _(position)

(company) (telephone)

(address)

(city,

state, zip)

CC)1(NENTS:

Areas _of comment are general _{presentation, format, organization,} completeness,

clarity,

_{accuracy, etc.}

If

a comment _{applies to} a

specific page or pages, please _cite the _{page number(s).}

MOBS

MLINK REFERENCE MANUAL

(VERSION

l.xx)

FOR _CP/M AND MP/M

Micro Data Base Systems, _Inc. P. O. Box 248

Lafayette, Indiana 47902

USA

February 1982

(Revised August 1982 _{for Version} 1.03) (Revised November 1982 _{for Version} 1.03h)

Copyright Notice

This

entire

manual _{is provided}

for

_the use of the customer and the customer's employees. The _{entire contents have been copyrighted}

by _Micro Data Base Systems, _Inc., and _{reproduction by any means is}

prohibited except _{as permitted in} a written agreement _with Micro Data Base Systems, _Inc.

Trademarks: CP/!4 and MP/M _{are trademarks of}

Digital

Research.

NEWS RELEASES, VERSIONS, AND A WARNING

Any programming endeavor _of the magnitude _of the MDBS _software

will

necessarily continue to evolve _{over time. Realizing}

this,

Micro Data Base Systemsk' _nnc., vows to provide

its

users with updates to

this

version for

a nominal handling _fee. New _{versions of} MDBS _software

will

be _{considered as separate products.}

Our _products have been produced _with a _{very substantial} investment of

capital and _{labor, to say nothing of} the _{years of prior involvement in} the data base management area by our principals. Accordingly, we _are

seriously concerned about _{any unauthorized} copying _{of our products} and

will

take _any and

all

_{available legal action against}

illegal

copying or

distribution

of our products.

(C) COPYRIGHT _{1982 Micro Data Ease Systems,}

MDBS MLINK MANUAL MDBS MLINK MANUAL

I.

MLINK DESCRIPTION

A. Overview

MLINK _is a

utility

_program that is executable under the CP/M and

MP/M _{operating systems.} When MLINK _{is invoked,}

it

links

together relocatable object modules. The

result

_is a .COM

file

that _can be

executed under CP/M or MP/M. MLINK _accepts REL, ERL, and IRL _object

files.

B. Using MLINK: Batch Mode

MLINK

is

_{provided on the}

files

named MLINK.COM, MLINKI.OVL, and MLINK2.OVL. The two _overlay

files

must be on the

default

drive. To execute MLINK, a command line of the following form is entered:

mlink

file1 Ifile2 file3 ... filekj

where

filel,

_fi1e2,

... and

filek

are names of REL, ERL, and/or IRL

files.

These must be

fully

_qualified

file

_names.

If

_{an extension is}

not specified

for

a

file,

then the .REL _{extension is} assumed. MLINK

generates two

files

_{on the} same drive as

filel:

filel.COM and

filel.SYM. The _{former contains executable object} code; _the

latter

contains a symbol table.

If

_an

alternative

_{name or} drive is desired

for the COM _and SYM

files,

_the -O _{option can} be _used:

MLINK

-Oaltfile fiilel Ifile2 file3 ... filekl

where

altfile

_{is the}

alternative

file

_name.

If

_{no extension is}

specified

for

altfile,

the .COM _{extension is used}

for

_{the linked}

output

file.

The .SYM _{extension is used for the symbol table.}

The _{ordering of}

files

_in the command _{line is important}

if

_{one or} more of the

files

is a

library

of object modules. The

files

_are

processed in the order given on the command

line.

Since MLINK

satisfies

forward

references,

an

external

reference must be

unsatisfied

when MLINK _{searches the}

library

_{containing the object}

module

for that external.

In other words, the

library

file,

containing an external that is referenced in another

file,

should

follow that other

file

in the command _line.

MLINK _performs

selective linking

_with a

library

file

when the

library

file

name is prefaced with -L. Only those _object modules _in the

library

file

_{that are required to satisfy} undefined _externals

will

be _linked. For _instance,

MLINK

filel

-Lfile2

generates the linked filel.COM, which does _{not include any object} modules from

file2

_{that are} not _{referenced in}

filel.

(C) COPYRIGHT _{1982 Micro Data Base Systems, Inc.}

MDBS MLINK MANUAL

-

I.

MLINK DESCRIPTION - MDBS MLINK MANUAL

Several _optional arguments _{can be included} on the command

line:

-Ahhhh where hhhh

is

a hex number _that

specifies

_the

address where _the

linker's

_output

file

_{is to be} loaded. When _{this optional argument is omitted a}

load address _of lOó hex _is used.

-C _{This option causes} a "compact" output

file

_to be

produced by

first

_assigning

all initialized

program, common, and _data segments.

It

_then assigns

all uninitialized

_program, common and data

segments. _{Uninitialized} segments are not _written

to the output

file.

This

option

may _cause

improper operation of code _produced by

certain

compilers.

-E _{This option} must be _specified when

linking

C'

programs.

It

inserts

?CRT0 _{(C' runtime startup}

module)

into

_the symbol _{table as an}

unsatisfied

external. This option must be _{specified before} LIBC _is searched.

-Esymboí _{where symbol}

consists

_{of from one to}

six

characters.

This

option

has _the

effect

_of

inserting

the indicated symbol name

into

the

symbol _{table as an undefined external.}

-Esymbol=hhhb _{where symbol}

consists

_{of from one to}

six

characters and hhhh _is a hex address. This option

defines the _{indicated symbol to be an entry point}

with address hhhh.

-Iincfile

where

incfile

is

_{the name of} a

file

containing _one

or more MLINK _arguments.

All

_{arguments from}

incfile

are included in the command _{line in} place

of the

-I

argument. The _{contents of}

incfile

_are

free form and can _{extend over} many

lines.

MLINK arguments in

incfi1e

are separated by blanks. Any

line in

incfi1e

that begins _with a semi-colon (;)

is

ignored by MLINK. The

-I

_{argument can} be nested _{within any}

incfile.

—Sstring where

string is

a _sequence of characters. This

option _{suppresses the}

writing

of any symbol (to

the symbol

table

file)

that

begins

with

a

character in the _indicated

string.

For _instance,

-S$? suppresses the

writing

of any symbols

beginning with ?

or S.

If

no

string

is specified, anew symbol table

file will

not be created.

-Uhhhh where hhhh _is the address given _to

all

_unsatisfied

externals at the end _{of pass}

l. If

hhhh

is

omit-ted, each

unsatisfied

_{external is given} a unique

address _{outside any areas} assigned by the _linker. -V This

is

a toggle that _causes NILINK to

alternate

between verbose mode _{and terse mode. Verbose mode}

causes MLINK _to

display

the nature of

its

MDBS MLINK MANUAL

-

I.

MLINK DESCRIPTION

-

MDBS MLINK MANUAL processing as

it

executes. The

first

_{use of} a -V

option turns on the verbose mode, the second -V

turns

it

off,

the

third

-V _turns

it

on, etc.

-X _{This option} suppresses the automatic generation of

a jump _{to the}

transfer

address that _{may occur at}

the _{beginning of} the _output

file.

-xhhhh where hhhh

is

a hexadecimal number. This option

defines the _transfer address (the address _at which program execution begins: ?XFER?) _{to be hhhh.}

If

this

option _appears before modules

with

the transfer address, then hhhh _overrides the _transfer address _{specified in} these modules and MLINK

will

issue a multiple ?XFER?

definition

diagnostic.

-XS _{This option causes the}

linker

_{to generate stack}

pointer

initialization

code, _{so that the stack}

pointer

will

be _{set to the top of user address} space before the

start

of execution. See _section

I-E-5 of this manual.

-XShhhh where hhhh

is

a hexadecimal number. This option

both defines the

transfer

address (?XFER?) _to be hhhh _{and causes} stack _pointer

initialization

code

to be _generated.

If

this

_{option appears before} modules _with the

transfer

_{address, then} hhhh

overrides the _transfer address _{specified in} these modules and MLINK

will

_issue a

multiple

?XFER?

definition

diagnostic.

-Ystfi1e where

stfi1e

is

a ZSID _type symbol _table

file.

This option enters the symbols _from

stfile

into

MLINK'S symbol _table.

-Z _{This option}

initializes

_(to O)

all

uninitialized

areas on the _output

file

generated by MLINK.

These _optional arguments can be used in any order. For instance:

MLINK -V -A0200 -OC:PRG PRG -LMDBSL -U

C. Using MLINK: _Interactive Mode

To _execute MLINK _in

interactive

mode, a command

line

_{of the}

following form _{is entered:} MLINK

The _{following response is displayed:}

Interactive mode: _enter MLINK arguments. To

start

_pass 2, _enter a

null line.

>

The > _{symbol is the interactive} mode _{prompt. Any argument that can} be

used _{in regular mode can also} be used _in

interactive

mode. However,

since interactive mode _{is normally verbose, the}

first

-V

will

_turn

off

MDBS MLINK MANUAL

-

I.

MLINK DESCRIPTION - MDBS MLINK MANUAL

the _{display of} verbose _messages, the second _{-V causes} verbose _messages

to be _{displayed again, etc.} To

exit

_the

interactive

mode _of MLINK, press the carriage return in response to an interactive mode prompt.

D. MLINK _Operation

MLINK _is a two-pass _{linker that} processes the command

line

in a

left

to

right

fashion. The

first

pass constructs the symbol

table,

containing

entries for

each _{of three types of segments: program} segments, common segments, and data segments. MLINK _{determines the}

size of each segment and assigns an absolute address _to each. When

determining the size of a segment, the

largest definition

of that

segment _is used _{(multiple definitions of} common segments are legal). Program segment addresses _are assigned

first,

common segments are then

assigned (blank common,

if it

is used, is the

first

of these common segments), and data segment addresses _are assigned _last. MLINK then passes through the symbol table to resolve

all

entry points, by

trans-forming

offsets into

absolute addresses. The second _{pass examines} needed

files

and _object modules _to generate _{executable object} code.

At any time during MLINK _{execution (batch or interactive), ML}