Trailing-Edge
-
PDP-10 Archives
-
cuspbinsrc_1of2_bb-x128c-sb
-
10,7/link/lnkerr.exe
There are 28 other files named lnkerr.exe in the archive. Click here to see a list.
?p ` ` @ ?x + @ -F; . * x . + x -@ Y:\\Y +)+ + 0F f
& 6F F '.|+ ,~ %LNKLNS Low segment data base not same size
COPYRIGHT (c) DIGITAL EQUIPMENT CORPORATION 1973,1988. ALL RIGHTS RESERVED.
+ Z 40B\Y+ ) *"
Q <d @ @ )B /" (H .( 5D &" q4B)
1" q+ "/" q+ . 0$ q/$ q! A1H + +4F =+ !Z <A" `B @ G)
0 ^ 2" 2b + =/ . Z + -! 7 + %Z ,> , *|, 9?7x ,> ." , +, 9w x ." , +, 6,^ 7B + =7@ + /+ -Q"A`,> x 4B)
>g. ]e ]i6n >]R kV!NNfn K>.^Ck>LSJ
I;kNN!?e6. *GN65K>~
Y:fY:nY:v3G26VIN K?6 # Y; >kN jK Qg7 G Sn JINf# C& -gNv @af^SB~
rSZ ZK2 1][JgO& MK26@_2 3g>.
kK6 VI3&AY&NOaF S K2vHM2.
MNv
K3 K C &ya"
a2 [Jv_" y S?6
[gR _ GC.Y 1]&:hE tG56sG5>G
~fC6n@eVn Aa3 <C7IK&6_ tS2 pg: VY6ni[C&jG6 SNv aV6-G66 M.
kJ <SO XSO&o[O ON.
Lg; p M&v
G7)SK
afo [66)[?6AG7FEG e _3 KaS ]C WKS :]"vEMRF
;YNnYg:f jq&!x] UB}_S&K7 ZS" Y]Nne _?6{[Nv
G&G. QNf
^[6SCFe U]NnY:y]N~QRf C:nW Kc IG @S6
Kc Z_FC K.`i |gK 1S6N
)SS( kN !
S6n
.MflY&vXSNn?S 6 & [C eCJftS3
G;>U e2 K &n I; TIWV: [R3k; 4Y7Y @e&pgRf jo:!lQf
MY6vuYNGIJ r uO6!~ exk jGK )[S DkN&! mf!ca
NIk e^ `YO t_"v_6biR6 Ia =_M i6f -MJ.
SR
a&`a6!gJ #G>.mG>6?vmg; x "B "
", ": "P "Y "h #
#9 #Z # $ $A $e $x % % %% %I %O %s %z & & & &J &b &k ' '? 'b ( (. (7 (> "% ", ": "P "Y "h #
#9 #Z # $ $A $e $x % % %% %I %O %s %z & & & &J &b &k ' '? 'b ( (. (7 (> "
", ": "P "Y "h #
#9 #Z # $ $A $e $x % % %% %I %O %s %z & & & &J &b &k ' '? 'b ( (. (7 (> "% ", ": "P "Y "h #
#9 #Z # $ $A $e $x % % %% %I %O %s %z & & & &J &b &k ' '? 'b ( (. (7 (> You loaded programs containing more ambiguous subroutine
requests than can fit in the tables of one or more overlay
links. You received a LNKARL message for each ambiguous
request, and a LNKTMA message for each link with too many
requests. You can solve this problem in either of two
ways. One is to use the /ARSIZE switch before the
/OVERLAY switch, thus expanding all the tables. The other
is to use the /ARSIZE switch just before each /LINK switch
to expand the tables separately. FORTRAN common areas cannot be expanded once defined.
Either load the module with the largest definition first,
or use the /COMMON: switch to reserve the needed space. The caller supplied argument does not match the argument
expected by the callee. You loaded ALGOL procedures, but no main program. The
missing start address and undefined symbols will terminate
execution. LINK expected a particular user address to be in memory,
but it is not there. This is an internal LINK error.
This message is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. More than one successor link can satisfy a call from an
ancestor link. The ancestor link requests an entry point
that is contained in two or more of its successors. You
should revise your overlay structure to remove the
ambiguity.
If you execute the current load, one of the following will
occur when the ambiguous call is executed:
1. If only one module satisfying the request is in
memory, that module will be called.
2. If two or more modules satisfying the request are in
memory, the one with the most links of its path in
memory will be called.
3. If no modules satisfying the request are in memory,
the one with the most links of its path in memory will
be called.
If a module cannot be selected by the methods 2 or 3
above, one of the modules will be called at random. LINK's memory manager was called with a request for 0
words. This is an internal LINK error. This message is
not expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. You have tried to build an overlay structure for a program
that is either too large to fit in section zero or which
loads outside section zero by default. Check your LINK
commands and also the assembly or compiler commands used
to produce the program modules. You have loaded modules compiled with conflicting CPU
specifications, such as loading a MACRO program compiled
with the statement .DIRECTIVE KA10 and another compiled
with .DIRECTIVE KI10. Recompile the affected modules with
compatible CPU specifications. Link has detected a character constant that did not begin
on a word boundary. This error is most likely the result
of a language translator error. This error is not
exspected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. LINK is unable to create the specified section. This
could be because your system does not have extended
addressing hardware, or because there are insufficient
resources to create a section. You have changed the log file specification. The old log
file is closed; further log entries are written in the
new log file. Fixups may not have been done because of a psect exceeding
it's upper limit. The resulting image is probably
incorrect. You cannot use COBOL-68 and COBOL files in the same load.
Compile all COBOL programs with the same compiler and
reload. You cannot use COBOL-74 and COBOL files in the same load.
Compile all COBOL programs with the same compiler and
reload. You cannot use COBOL-68 and COBOL-74 files in the same
load. Compile all COBOL programs with the same compiler
and reload. You are loading a mixture of COBOL-compiled files and
other files. Load one of the COBOL-compiled files first. You have loaded a module which specifies that the named
common block must be loaded in a psect which is not
compatible with the psect in which it was originally
loaded. Compile the module with the common in the same
psect as the original. You cannot load modules produced by FORTRAN with modules
produced by GFLoating FORTRAN. Compile all FORTRAN
modules the same way, then reload. You attempted to use an unimplemented feature. This is an
internal LINK error. This message is not expected to
occur. If it does, please notify your Software Specialist
or send a Software Performance Report (SPR) to DIGITAL. One of the modules you have already loaded explicitly sets
an attribute for the named psect which conflicts with the
declaration of psect attributes in the current module.
Check the compiler switches or assembly language
directives that were used in the generation of this
module. LINK cannot open the specified file for input. The module you are attempting to load does not contain a
.DIRECTIVE for any of the CPUs you specified with the /CPU
switch. Recompile the module with the proper .DIRECTIVE,
or use a different /CPU switch. You have loaded a module which contains code for the
section specified. LINK is creating that section. LINK is generating your executable (EXE) file. LINK is beginning program execution at the named debugger. Though you have asked for program execution, LINK cannot
proceed due to earlier fatal compiler or LINK errors.
Your program is left in memory or in an executable file. You used a device switch (for example, /REWIND,
/BACKSPACE), but LINK cannot associate a device with the
switch. Neither LINK's default device nor any device you
gave with the /DEFAULT switch can apply. Give the device
with or before the switch (in the same command line). You are using the /SET switch to reduce the value of an
already defined relocation counter. Unless you know
exactly where each module is loaded, code may be
overwritten. You loaded a FORTRAN-compiled module with DATA statement
assignments to a common area. The common area is already
defined in an ancestor link. Restructure the load so that
the DATA statements are loaded in the same link as the
common area to which they refer. You have a data store for an absolute location outside the
specified link. Load the module into the root link.
NOTE
If the location is less than 140, this message has
level 8 and severity 8.
LINK's undefined symbol count has become negative. This
message is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. LINK could not make the ALGOL symbol table on the disk.
You could be over your disk quota, or the disk could be
full or have errors. LINK could not write the saved file on the disk. You
could be over your disk quota, or the disk could be full
or have errors. LINK has expanded its low segment so large that one of its
larger high segments will not now fit in memory. LINK
will attempt to shrink its internal tables so that the
GETSEG will succeed and loading continue. LINK could not write your high-segment code on the disk.
You could be over your disk quota, or the disk could be
full or have errors. A read error has occurred on the input file. Use of the
file is terminated and the file is released. The status
is represented by the right half of the file status word.
Refer to the DECsystem-10 Monitor Calls for the
explanation of the file status bits. LINK could not write your low-segment code on the disk.
You could be over your disk quota, or the disk could be
full or have errors. LINK has finished writing your log file. The file is
closed. The link is loaded. LINK could not write your local symbol table on the disk.
You could be over your disk quota, or the disk could be
full or have errors. The map file is completed and closed. LINK could not write the saved file on the disk. The
status is represented by the left half of the file status
word. Refer to the DECsystem-10 Monitor Calls for the
explanation of the file status bits. An error has been detected while reading the named file.
The status is represented by the right half of the file
status word. Refer to the DECsystem-10 Monitor Calls for
the explanation of the file status bits. An error has been detected while writing the named file.
The status is represented by the right half of the file
status word. Refer to the DECsystem-10 Monitor Calls for
the explanation of the file status bits. LINK could not write the overlay file on the disk. The
status is represented by the left half of the file status
word. Refer to the DECsystem-10 Monitor Calls for the
explanation of the file status bits. LINK could not make the typechecking area on the disk.
You could be over your disk quota, or the disk could be
full or have errors. LINK is expanding memory to the specified amount. You can
speed up future loads of this program by using the /CORE:
switch to allocate the required memory. LINK is in the last stages of loading your program (for
example, creating EXE and symbol files, preparing for
execution if requested). LINK is reading one or both segment overflow files
backwards to perform any needed code fixups. This may
cause considerable disk overhead, but occurs only if your
program is too big for memory. @ 2 LINK is finished. Control is passed to the monitor, or to
the loaded program for execution. @ D @ V During final processing of your root link, LINK found that
the FUNCT. subroutine was not loaded. This would cause an
infinite recursion if your program were executed. The
FUNCT. subroutine is requested by the overlay handler, and
is usually loaded from a default system library. Either
you prevented searching of system libraries, or you did
not load a main program from an overlay-supporting
compiler into the root link.
A symbol with a value greater than 777777 was used to
resolve a halfword reference. This may indicate a that a
global symbol was used improperly. @ g You have attempted to load high segment code into an
overlay link other than the root. Any high segment code in
an overlaid program must be in the root. You have set the high-segment counter to a page containing
low-segment code. Reload, using the /SET:.HIGH.:n switch,
or (for MACRO programs) reassemble after changing your
TWOSEG pseudo-op. Note that you cannot set the
high-segment counter below 400000 for a KI10 monitor
before 5.07, or for any KA10 monitor. Your symbol hash table is larger than the maximum LINK can
generate (about 50P). This table size is an assembly
parameter. This message is not expected to occur. If it
does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. An error occurred while reading in the ALGOL symbol
table. The status is represented by the right half of the
file status word. Refer to the DECsystem-10 Monitor Calls
for the explanation of the file status bits. REL block type 12 (chain), generated by the MACRO
pseudo-op .LINK and .LNKEND, must contain a number from 1
to 100 (octal) in its first word. The link word is
ignored. You specified an illegal combination of device and data
mode (for example, terminal and dump mode). Respecify a
legal device. An error occurred while reading in your high-segment
code. The status is represented by the right half of the
file status word. Refer to the DECsystem-10 Monitor Calls
for the explanation of the file status bits. An error occurred while reading in your low-segment code.
The status is represented by the right half of the file
status word. Refer to the DECsystem-10 Monitor Calls for
the explanation of the file status bits. An error occurred while reading in your local symbol
table. The status is represented by the right half of the
file status word. Refer to the DECsystem-10 Monitor Calls
for the explanation of the file status bits. The INCREMENTAL keyword for the /MAP: switch is not
implemented. The switch is ignored. LINK needs more memory than is available. You have requested with the /INCLUDE: switch that the
named modules (if any) be loaded. Specify files
containing these modules. LINK attempted a monitor call (for example, LOOKUP, ENTER)
for a channel that is not set up. This is an internal
LINK error. This message is not expected to occur. If it
does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. An error occurred when reading the overlay file. The
status is represented by the right half of the file status
word. Refer to the DECsystem-10 Monitor Calls for the
explanation of the file status bits. You are attempting to load a file containing an invalid
REL block type 11 or 1072 (polish). This message is not
expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. A REL block contains a reference to a nonexistent psect.
This error is probably caused by a fault in the language
translator used for the program. This error is not
expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. The file is not in the proper binary format. It may have
been generated by a translator that LINK does not
recognize, or it may be an ASCII or EXE file. One of the new style 1000+ block types has an illegal
relocation counter. This message is not expected to
occur. If it does, please notify your Software Specialist
or send a Software Performance Report (SPR) to DIGITAL. One of the REL block types 1042 or 1043 is in the wrong
format. This message is not expected to occur. If it
does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. The specified module contains an incorrectly formatted
polish fixup block (type 11 or 1072). The store operator
specifies a symbol fixup, but the block ends before all of
the symbol is specified. This error is probably caused by
a fault in the language translator used for the program.
This error is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. The LINK symbol table routine was called with the blank
symbol. This error can be caused by a fault in the
language translator used for the program. This message is
not expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. There is an error in the global symbol table. This is an
internal LINK error. This message is not expected to
occur. If it does, please notify your Software Specialist
or send a Software Performance Report (SPR) to DIGITAL. There is insufficient address space for the symbol table
between the named psect and the next higher one or the end
of the address space. Restructure your psect layout to
allow sufficient room for the symbol table. LINK has found errors in the switch table passed from the
SCAN module. This is an internal error. This message is
not expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. LINK has failed to complete the processing of an ASCII
text REL block from the named file. This is an internal
error. This message is not expected to occur. If it
does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. An error occurred while reading in the typechecking area.
The status is represented by the right half of the file
status word. Refer to the DECsystem-10 Monitor Calls for
the explanation of the file status bits. LINK's user UUO (LUUO) handler has detected an illegal
UUO. This is an internal error. This message is not
expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. The range checking of LINK's internal tables and arrays
failed. The address given is the point in a LINK segment
at which failure occurred. This is an internal error.
This message is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. The specified module contains an incorrectly formatted
polish fixup block (type 11). Either the last unused
halfword (if it exists) is non-zero, or there are extra
halfwords following all valid data. LINK ignores the
extra data. This error is probably caused by a fault in
the language translator used for the program. This error
is not expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. The LINK module LNKLOD is beginning its processing. LINK is creating your log file as a result of defining the
logical name LOG:. LINK is continuing your log file as a result of the /LOG
switch. LINK is beginning your log file as a result of the /LOG
switch. A REL block type 14 (index) for a MAKLIB or FUDGE2
generated library file is inconsistent. The library is
searched, but the index is ignored. LINK is beginning its processing by initializing its
internal tables and variables. The length of the argument passed by the caller does not
match what the called routine expects it to be. LINK is loading the named module. You used this name for another link. Specify a different
name for this link. The link with this number has not yet been loaded. The
/NODE switch is ignored. If you have used link numbers
instead of link names with the /NODE switch, you may have
confused the link numbers. To avoid this, use link
names. LINK cannot find the named link in memory. This is an
internal error. This message is not expected to occur.
If it does, please notify your Software Specialist or send
a Software Performance Report (SPR) to DIGITAL. The name you gave with the /NODE switch is not the name of
any loaded link. The switch is ignored. ^_
The length of LINK's low segment differs from the length
stored in the current LINK high segment. This occurs if
some but not all of LINK's EXE files have been updated
after rebuilding LINK from sources. Update all of LINK's
EXE files. Your use of the /NODE switch shows that you want to begin
a new overlay link, but the current link is not yet
completely loaded. LINK assumes a /LINK switch
immediately preceding the /NODE switch, and loads the link
(without a link name). The listed symbols and their values (if any) are those
that are library search entry points. The named module contains a new definition of an already
defined global symbol. The old definition is used. Make
the definitions consistent and reload. LINK cannot expand memory further. All permitted
overflows to disk have been tried, but your program is
still too large for available memory. A probable cause is
a large global symbol table, which cannot be overflowed to
disk. The internal memory manager in LINK has failed a
consistency check. This error is not expected to occur.
If it does, please notify your Software Specialist or send
a Software Performance Report (SPR) to DIGITAL. LINK is rearranging its low segment to make more room for
the specified area. Area is one of the following:
AS=ALGOL symbol table, BG=bound global symbols, DY=dynamic
free memory, FX=fixup area, GS=global symbol table,
HC=your high-segment code, LC=your low-segment code,
LS=local symbol tables, RT=relocation tables. The LINK module LNKMAP is writing a map file. This module contains both psect code and twoseg code. LINK
cannot load such a module. Change the source code to use
psects .HIGH. and .LOW. as the high and low segments, and
remove the TWOSEG or HISEG pseudo-ops. The REGION keyword for the /OVERLAY: switch is not
implemented. The argument is ignored. Alphabetical or numerical sorting of the map file is not
implemented. The symbols in the map file appear in the
order they are found in the .REL files. The current value of MAXCOR is too small for LINK to
operate. You can speed up future loads of this program by
setting the /MAXCOR: switch to this expanded size at the
beginning of the load. You are attempting to specify the /MAXCOR: switch so large
that the low segment cannot fit before the high segment.
LINK will use only the core indicated. LINK needs more space than you gave with the /MAXCOR:
switch. Give a new /MAXCOR: switch with at least the
required size. The specified module contains an incorrectly formatted
polish fixup block (type 11 or 1072). The store operator
specifies a memory fixup, but the block ends before the
address is specified. This error is probably caused by a
fault in the language translator used for the program.
This error is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. The argument you gave for the /NODE switch would indicate
a link before the root link. (For example, from a
position after the third link in a path, you cannot give
/NODE:-4.) No REL block type 5 (end) was found in the named module.
This will happen if LINK finds two type 6 blocks (name)
without an intervening end, or if an end-of-file is found
before the end block is seen. LINK simulates the missing
end block. However, fatal messages usually follow this,
since this condition usually indicates a bad REL file. You gave a device that does not exist on this system.
Correct your input files and reload. You have attempted to load high segment code into a
program that is being loaded into a nonzero section.
Programs with high segments must be in section zero. You have specified the name of a psect after which LINK
should append the symbol table, but no psect with that
name was loaded. Load the named psect or specify an
existing psect for the symbols. Your program does not have a starting address. This can
happen if you neglect to load a main program. Program
execution, if requested, will be suppressed unless you
specified debugger execution.
You used the /LINK switch, which indicates that you want
to begin a new overlay link, but you have not specified a
NODE switch to tell LINK where to put the new overlay ink. The specified module contains an incorrectly formatted
polish fixup block (type 11 or 1072). Either the block
does not have a store operator, or LINK was not able to
detect it due to the block's invalid format. This error
is probably caused by a fault in the language translator
used for the program. This error is not expected to
occur. If it does, please notify your Software Specialist
or send a Software Performance Report (SPR) to DIGITAL. The called routine does not return a value, however the
caller expected a returned value. An error occurred while writing out the ALGOL symbol
table. The status is represented by the right half of the
file status word. Refer to the DECsystem-10 Monitor Calls
for the explanation of the file status bits. An error has occurred on the output file. The output file
is closed at the end of the last data successfully output.
The status is represented by the right half of the file
status word. Refer to the DECsystem-10 Monitor Calls for
the explanation of the file status bits. An error has occurred on the output file. The output file
is closed at the end of the last data successfully output.
The status is represented by the right half of the file
status word. Refer to the DECsystem-10 Monitor Calls for
the explanation of the file status bits. An error has occurred on the output file. The output file
is closed at the end of the last data successfully output.
The status is represented by the right half of the file
status word. Refer to the DECsystem-10 Monitor Calls for
the explanation of the file status bits. An error has occurred on the output file. The output file
is closed at the end of the last data successfully output.
The status is represented by the right half of the file
status word. Refer to the DECsystem-10 Monitor Calls for
the explanation of the file status bits. An OPEN or INIT monitor call for the specified device
failed. The device may be under another user's control. The standard released version of LINK does not support F40
code. Specify a disk device for the overlay file. An error occurred while writing out your high-segment
code. The status is represented by the right half of the
file status word. Refer to the DECsystem-10 Monitor Calls
for the explanation of the file status bits. Internal symbols in the overlay handler could not be
referenced. If you are using your own overlay handler,
this is a user error; if not, it is an internal error.
This message is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. An error occurred while writing out your low-segment
code. The status is represented by the right half of the
file status word. Refer to the DECsystem-10 Monitor Calls
for the explanation of the file status bits. An error occurred while writing out your local symbol
table. The status is represented by the right half of the
file status word. Refer to the DECsystem-10 Monitor Calls
for the explanation of the file status bits. The /OVERLAY switch must appear before you can use any of
the following switches: /ARSIZE:, /LINK, /NODE, /PLOT,
/SPACE. (It is sufficient that the /OVERLAY switch appear
on the same line as the first of these switches you use.) An error has occurred while writing the overlay file. The
status is represented by the right half of the file status
word. Refer to the DECsystem-10 Monitor Calls for the
explanation of the file status bits. LINK's module LNKOV2 is writing your overlay file. You have specified /SYMSEG:HIGH or /SYMSEG:PSECT: when
loading an overlay structure. Specify /SYMSEG:LOW or
/SYMSEG:DEFAULT. An error occurred while writing out the typechecking area.
The status is represented by the right half of the file
status word. Refer to the DECsystem-10 Monitor Calls for
the explanation of the file status bits. The load is too large to fit into the allowed memory and
the ALGOL symbol table is being moved to disk. The highest address allocated in the named module is
greater than 512P. This is usually caused by dimensioning
large arrays. Modify your programs or load list to reduce
the size of the load. Your program is too complex to load into memory for one of
the following reasons:
1. There are page gaps between psects (except below
the high segment).
2. There are psects above the origin of the high
segment.
3. Your program will not fit in memory along with
LINK's final placement code.
4. Your program's low segment has the read-only
attribute, or the high segment has the read and
write attribute.
LINK has saved your program as an EXE file on disk and
cleared your user memory. You can use a GET or RUN
command to load the EXE file. Your program is too complex to load into memory for one of
the following reasons:
1. There are page gaps between psects (except below
the high segment).
2. There are psects above the origin of the high
segment.
3. Your program will not fit in memory along with
LINK's final placement code.
4. Your program's low segment has the read-only
attribute, or the high segment has the read and
write attribute.
LINK will save your program as an EXE file on disk and
automatically run it, but the EXE file will not be
deleted. LINK found an end-of-file inside a REL block (that is, the
word count for the block extended beyond the
end-of-file). This error can be caused by a fault in the
language translator used for the program. The Psect named has exceeded the upper limit set for it.
No additional chained fixups will be performed, and the
resulting image will probably be incorrect. Symbol table
fixups, however will be performed, and all map information
will be correct. The load is too large to fit into the allowed memory and
your high-segment code is being moved to disk. The load is too large to fit into the allowed memory and
your low-segment code is being moved to disk. The caller has specified that the argument should not be
modified. The called routine contains code which may
modify this argument. In some cases this message will
occur although the argument is not actually modified by
the routine. The load is too large to fit into the allowed memory and
your local symbol tables are being moved to disk. The named psects have begun to overlap each other at the
indicated address. This may cause LINK to get other fatal
errors or even link incorrectly if fixup chains overlap.
If you do not expect this message, restructure your psect
origins with the /SET:PSECT: switch. LINK is creating your overlay tree file. The named psects overlap each other in the indicated range
of addresses. If you do not expect this message,
restructure your psect origins with the /SET:PSECT:
switch. Your program extends beyond location 777777, which is the
highest location that LINK is capable of loading. You may
be able to make your program fit by moving psect origins,
lowering the high segment origin, loading into a single
segment, reducing the size of arrays in your program, or
using the overlay facility. The load is too large to fit into the allowed memory and
your argument typechecking tables are being moved to disk. A PAGE. UUO to rearrange LINK's address space has failed,
and returned the error code given. You may be able to
avoid this problem by varying the physical and virtual
limits for the job, or by varying the values given with
the /CORE: and /MAXCOR: switches. This is an internal
LINK error. This message is not expected to occur. If it
does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. The REL block is inconsistent. This may be caused by
incorrect output from a translator (for example, missing
argument for an end block). Recompile the module and
reload. LINK is reclaiming memory by deleting its internal
tables. The listed symbols and their values (if any) represent
subroutine entry points in the current link. LINK is expanding the global symbol table either to a
prime number larger than your /HASHSIZE: switch requested,
or by about 50 percent. You can speed up future loads of
this program by setting /HASHSIZE: this large at the
beginning of the load. The listed symbols and values represent the current
placement of psects in your address space. The REMAP UUO to place your program's high segment has
failed. This message is not expected to occur. If it
does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. LINK attempted to return memory to the memory manager, but
the specified memory was not previously allocated. This
is an internal error. This message is not expected to
occur. If it does, please notify your Software Specialist
or send a Software Performance Report (SPR) to DIGITAL. One of the modules you have already loaded explicitly sets
an attribute for the named psect which conflicts with the
declaration of psect attributes in the current module.
Check the compiler switches or assembly language
directives that were used in the generation of this
module. There are errors in the local symbol table. Loading
continues, but any maps you request will not contain
control section lengths. This is an internal error. This
message is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. LINK's hashing algorithms failed; they are trying to
write a new symbol over an old one. You may be able to
load your files in a different order. This is an internal
error. This message is not expected to occur. If it
does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. You loaded some SIMULA procedures or classes, but no main
program. Missing start address and undefined symbols will
terminate execution. You defined a FORTRAN common area with the same name as a
non-common symbol. You must decide which definition you
want. If you want the common definition, load the common
area first. LINK is ready to process the next command line. The named subroutine is in a different path from the
calling link. Redefine your overlay structure so that the
subroutine is in the correct path. LINK does not support the .REL file format produced by the
SITGO compiler. Load your program by using SITGO. An error occurred in outputting the EXE file. The status
is represented by the right half of the file status word.
Refer to the DECsystem-10 Monitor Calls for the
explanation of the file status bits. You cannot use the /SET: switch to set the named
relocation counter below its initial value. The attempt
is ignored. Relocatable psects are not implemented; you must specify
an explicit absolute origin with the /SET:PSECT: switch
for the named psect. Alphabetical or numerical sorting of the symbol table is
not implemented. The symbols appear in the order they are
found. LINK is rearranging the symbol table, and if required, is
converting the symbols from the new to old format as
indicated on the /SYMSEG, /SYFILE, or /DEBUG switch. The symbol table has been sorted and moved according to
the /SYMSEG, /SYFILE, or /DEBUG switch. A symbol specified in a rel block is longer than the
maximum allowed by LINK. REL block type 13 (LVAR) is obsolete. Use the MACRO
pseudo-op TWOSEG. LINK has already loaded the initial symbol table. To
prevent this loading, place the /NOINITIAL switch before
the first file specification. You have more ambiguous subroutine requests (indicated by
LNKARL messages) than will fit in the table for this link.
Continue loading. Your load will abort at the end with a
LNKABT message; if you have loaded all modules, the
message will give the size of the needed /ARSIZE switch
for a reload.
You have specified more overlay links than were allowed by
the current value for the /MAXNODE switch. Reload your
program with a larger /MAXNODE value. The data type of the argument passed by the caller does
not match what the called routine expects. In producing the index for a map file, LINK found more
program names than there are programs. The symbol table
is in error. This is an internal error. This message is
not expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. The named symbol was referenced in a REL block type 100
(ASSIGN), but the symbol is undefined. This is generated
with the MACRO pseudo-op .ASSIGN. The assignment is
ignored. You should load a module that defines the
symbol. A reference was made to a common block, however the block
does not exist. The listed symbols and their values (if any) represent
symbols not yet defined by any module. Each value is the
first address in a chain of references for the associated
symbol.
If this message resulted automatically at the end of
loading, this is a user error. In this case, the load
will continue, leaving references to these symbols
unresolved. Extraction of symbols from a MACRO universal file is not
implemented. In a REL block type 2 (symbols), the first 4 bits of each
word pair contain the Radix-50 symbol code. LINK found
one or more invalid codes in the block. This error can be
caused by a fault in the language translator used for the
program. The called routine returns a value which was not expected
by the caller. You gave an undefined global symbol as the start address.
Load a module that defines the symbol. LINK has detected an undefined global symbol in a type 1004
REL block. This global symbol is used to relocate a byte
pointer and must be defined before the 1004 block that uses
it is seen. This error is most likely the result of an
error in the language translator used to generate the REL
file. The named link contains a call for a subroutine you have
not loaded. If the subroutine is required for execution,
you must reload, including the required module in the
link. LINK has detected an undefined global symbol in a type
1160 REL block. This global symbol is used to relocate a
byte pointer and must be defined before the 1160 block
that uses it is seen. This error is most likely the
result of an error in the language translator used to
generate the REL file. You have specified an undefined symbol to a switch that
can only take a defined symbol or a number. Specify the
correct switch value. You gave the named symbol as an argument to the /UPTO:
switch, but the symbol was never defined. Load a module
that defines the symbol, or change your argument to the
/UPTO: switch. LINK has printed the specified symbol, its value and its
attributes as requested. The number of arguments in the routine call is not the
number of arguments expected by the called routine. LINK is beginning execution of your program. You omitted required arguments for a switch (for example,
/REQUIRE with no symbols). Respecify the switch. One of the following conditions occurred:
1. The specified file name was illegal.
2. When updating a file, the specified file name did not
match the file being updated.
3. The RENAME monitor call following a LOOKUP monitor
call failed. The named file was not found. Specify an existing file. The named directory does not exist on the named file
structure, or the project-programmer number given was
incorrect. You do not have sufficient access privileges to use the
named file. The directory on the DECtape has no room for the file.
Delete some files from the DECtape or specify another
device. Another job is currently modifying the named file. Try
accessing the file later. The named file already exists, or a different file was
specified on the ENTER monitor call following a LOOKUP
monitor call. ({ LINK has specified an illegal sequence of monitor calls
(e.g., a RENAME without a preceding LOOKUP or ENTER
monitor call, or a LOOKUP after an ENTER). This is an
internal error. This message is not expected to occur.
If it does, please notify your Software Specialist or send
a Software Performance Report (SPR) to DIGITAL. One of the following conditions occurred:
1. A transmission, device or data error occurred while
attempting to read the directory or the RIB of the
named file.
2. A hardware-detected device or data error was detected
while reading the named directory's RIB or data block.
3. A software-detected data inconsistency error was
detected while reading the named directory's or file's
RIB. (n The named file is not a saved file. This message can
never occur and is included only for completeness of the
LOOKUP, ENTER and RENAME error codes. This message is not
expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. (n The system cannot supply enough memory to use as buffers
or to read in a program. This message can never occur and
is included only for completeness of the LOOKUP, ENTER and
RENAME error codes. This message is not expected to
occur. If it does, please notify your Software Specialist
or send a Software Performance Report (SPR) to DIGITAL. (n The named device is currently not available. This message
can never occur and is included only for completeness of
the LOOKUP, ENTER and RENAME error codes. This message is
not expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. (n The named device dies not exist. This message can never
occur and is included only for completeness of the LOOKUP,
ENTER and RENAME error codes. This message is not
expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. (n The machine does not have a two-register relocation
capability. This message can never occur and is included
only for completeness of the LOOKUP, ENTER and RENAME
error codes. This message is not expected to occur. If
it does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. You have exceeded the quota of the named directory, or the
entire capacity of the file structure. Delete some files,
or specify a directory or structure with sufficient space. The named device is write-locked. Specify a write-enabled
device or ask the operator to write-enable the named
device. There is not enough internal monitor table space for the
named file. Try the load at a later time. Because of the named directory's quota or the available
space on the file structure, the total number of blocks
requested could not be allocated. A partial allocation
was given. (n The block required by LINK is not available for
allocation. This message can never occur and is included
only for completeness of the LOOKUP, ENTER and RENAME
error codes. This message is not expected to occur. If
it does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. You have attempted to supercede the named directory. (n You have attempted to delete a directory that is not
empty. This message can never occur and is included only
for completeness of the LOOKUP, ENTER and RENAME error
codes. This message is not expected to occur. If it
does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. One of the sub-file directories in the named path was not
found. A LOOKUP or ENTER monitor call was performed on generic
device DSK: and the search list is empty. You have attempted to create a sub-file directory nested
deeper than the maximum level allowed. No file structure in your job's search list has both the
no-create bit and the write-lock bit equal to zero, and
has the named directory. (n A GETSEG monitor call was issued from a locked low segment
to a high segment which is not a dormant, active or idle
segment. This message can never occur and is included
only for completeness of the LOOKUP, ENTER and RENAME
error codes. This message is not expected to occur. If
it does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. A LOOKUP and ENTER monitor call was given to update a
file, but the file cannot be updated for some reason
(e.g., another user is superceding it or the file was
deleted between the time of the LOOKUP and the ENTER). The end of the low segment is above the beginning of the
high segment. ({ An attempt has been made to run a program from a
not-logged-in job. This message can never occur and is
included only for completeness of the LOOKUP, ENTER and
RENAME error codes. This message is not expected to
occur. If it does, please notify your Software Specialist
or send a Software Performance Report (SPR) to DIGITAL. (n The ENQ/DEQ facility has been used for simultaneous
updating of the named file, but some ENQ/DEQ requests are
still outstanding and the file cannot be closed. This
message can never occur and is included only for
completeness of the LOOKUP, ENTER and RENAME error codes.
This message is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. (n The named file has a bad EXE format directory. This
message can never occur and is included only for
completeness of the LOOKUP, ENTER and RENAME error codes.
This message is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. ({ An attempt has been made to run an EXE-format file with a
non-.EXE extension. EXE format files (those with an
internal directory) must have the extension .EXE. This
message is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. An attempt has been made to run an EXE-format file with a
directory that is too large for the monitor to handle.
This message can never occur and is included only for
completeness of the LOOKUP, ENTER and RENAME error codes.
This message is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. The monitor's ability to accept another network connection
has been exceeded. The named task is not available. Specify an existing task
name. You have specified a network node that does not exist.
Wait for the node to come up or specify an existing
network node. ({ This message indicates that a LOOKUP, ENTER or RENAME
monitor call error occurred with an error code larger in
number than the errors LINK knows about. This message is
not expected to occur. If it does, please notify your
Software Specialist or send a Software Performance Report
(SPR) to DIGITAL. ({ This message can never occur and is included only for
completeness of the LOOKUP, ENTER, and RENAME error codes. This message is not expected to occur. If it does, please
notify your Software Specialist or send a Software
Performance Report (SPR) to DIGITAL. Z8 9 " ,^ ,~ )\ )c * * *! *# *$ *& *' ** *+@ *.@ *1 *4 *J *L *O *P *? J S
+j** R 15+) 4*)+)7 H+ )& ;aB + ) "+0" + $+3$ ;0$ + )", +, )$, *|, 9?+ )& " 6 X, : " .5 :"+2" ;1B 7 + )CZ` =1B
+ ).
S7b <+ )-, 85@@ <: 1+ = $ , 0b @ Q !B @@ @@ \")56 X\")<
& + 82, 85@@ <+ 82[ Please retype the incorrect parts of the file specification]
[ Please retype the incorrect parts of the file specification ]
01B , 83 ")Z6@ =, 9w& " ,> !*xZ b 4B)M (ZB [ 0BK8+ )MZ , ./+ *j)H,^ " $+cB ;1$ ` B ;@@ =@@ < Z 1B, ` =, 85
2 6@ + \"+k6 X\"+o
& b + [End of log file]
O@ H"+5B)`,^ b+1B " b+, *Q+ *Z , *|, 9w+ *,^ H H ^ `j p+ )m0d $ [+I`h 6` 1 [+Hf+&+`h 0F
+ )ml* p, *Q+ *Z , *|, 9w, *|, :
^( 0d , )7" A" GB <Z+I`h 6` 1 Z+H, *|, 9wZ , *|, ++ *Z 50d , )Z+I, *|, 9wZ" 4, *|, ++ ),> " , *|, :,^ , *|, 9N $ ,~ ,^ H, *Q+ *Z , *|, 9w HZ @@ , *|, 9G, *|, :
+ ),^ H, *Q5 *Z , *|, 9w " , *|, : "+s, *|, 9wS H(B G+t+@ Z , *|, 8* "+t, *|, 9w HZ + )yaj + )"+: 1 1b+6` H+ * "+6 )+ *Z aj + * 1b 7P $++), *|, 9w+ *, *|, +!+ *, *|, 9N+ *, *|, 9N+ *X
(Z , *|, ++ *, *|, :+ *. 2D 2, *|, 99+ *Z 1 D G/" XB 1l* + *. GXB 1$+
d++ * "+v6@ =, 9w7@ <7` =7 + *6 <+ *9, *=+ * =, 85,> , *=,^ , 85+ * "+w6 X "+w5 9w/ {4"+x. >X
( , *|, 9G6"( + ab + *.* 6"( `b?+ * ( , *|, 9G7B( + *, *|, 9G+ *D+@ + *: 1+ *7@ =+ *7@ <, 9?+ *, *|, 8v+ *+ *7" H+ *UZ` $+1D
1B + *U $ d+"+3" :+ *`6@ <+ +x7@ =+ *` " B H, +"+3" :+ *e =, 85,> , *s,^ , 85\` =+ *e"+3" :+ +z " B H6@ <+ *eZ >, 85ZB <, *s ( B < " <, +, 9w ;aB + *k " <, +, 9w ;aB + +{ " , +, : ;aB 7+| " , +, :.* 6` H: x ,~ $+ " -0$ " 2$ ; " @@ X1B -+ *x
6 + , : ;aB ,~ O@ X "+|5 9w6 =,~ ,> +A =, 85*x +A,^ : x 5 856@ <,~ 6` =+ *r,> + *~7@ <7@ =+ *r,> +A,^ + *r, 9, :
, : $ , 9
"+}5 9w8 . $ . $( , 9G, :
, 9GR `d 4B+l ("}, 9G " `d5 8Q .+}5 8Q , 9G, :
, 9GR l ("}, 9G " 5 8Q,> @
`bp 5 +(,> [
"` S
X
( , +**j+%,^ ,^ ,~ , +*,^ ,~ 4D*r " )B 1B + +31B + +2." 4L+10" 0b -1 ." , :+ +*O
+ +*@
+ +*FEE ENTER error FLE LOOKUP error FRE RENAME error GSE GETSEG error NED Non-existent device OFD OPEN failure for device EIF Error for input file CNW Code not yet written at ~+~~, q~,q~,q~,
q~,
q~,~,~,~,~,~, ~,!~,#q~,'q~,+~,-B,1~,4~,8~,=q~,Bq~,Dq~,Gq~,Jq~,Nq~,Rq~,T~,X~,]~,b~,f~,k~,o~,s~,v~,z V,| @ H ,}` , @ V,| @ H - ` p" , @ -` _ V- @ -` ` @ H ` ( ` P$ >+i >+f h ,~ Q[ Type CONTINUE for more information] [ Type CONTINUE for more information ] Status
@ for file
+ " B H+ *eO@ H+ *q@@ H+ *q LNK (2) directory full (0) Illegal file name (0) file was not found (1) no directory for project-programmer number (2) protection failure (3) file was being modified (4) rename file name already exists (5) illegal sequence of UUOs (6) bad UFD or bad RIB (7) not a saved file (10) not enough memory (11) device not available (12) no such device (13) not two reloc reg. capability (14) no room or quota exceeded (15) write lock error (16) not enough monitor table space (17) partial allocation only (20) block not free on allocation (21) can't supersede (enter) an existing directory (22) can't delete (rename) a non-empty directory (23) SFD not found (24) search list empty (25) SFD nested too deeply (26) no-create on for specified SFD path (27) segment not on swap space (30) can't update file (31) low segment overlaps high segment (32) RUN not allowed when not logged in (33) file still has outstanding ENQ/DEQ locks (34) bad EXE file directory format (35) EXE format files must have .EXE extension (36) EXE file directory is too big (37) network capability exceeded for TSK: (40) task is not available (41) undefined network node for TSK: ) Unknown cause a@ Detected in module from file Error detected in module link number 7@ ` name 6B,~ ~.x, - d D 4D.o $ 7 ,~ (E A 5D./,> ~.{, - $ Q$ P G +@ + .nZ$ d + 4D- 0F + -[ 1& Q$ 3D + -** 4D-", - + -", - Z@@ $ 5 15, - 4d./[ Z $$ 5 15, - h$ id + -0 [ Z $$ , 0b D + -*, - D ([ P ddm$ j Q$ h G +@ D (,~ @@ @@ ,~
$ D r ( D q ( D s ( RD t ( D s7@( ,~ D { " z B s . $( F 4F./.$ *b-:,~ , - l$ | af + -FX$ +@ ,~ D $ D Q$ d $@@ 5 ..X$ +@ ,~ 5 ..[x B $ 7B, 0b \B ^x B : x .SB RB ( B " B 7B( ! B 7B( "RB 7B( "b.!$ cD( + -Z ( ahP aHX "( + -abD( + -` / ( ad 7D( + -_ b $@ aF 7/ "( Z7@ + / H
9$ D ." 7D + -g+D o7D + -n / b $@ aF + -n ( ad 7D !$Lu Z D + - , - [ 4D-{Z` d& pG +@ =d-u $ 7@ + -z,> , 15, -,^ + -s, 15, -@@ $ Q$ ~ G af .$ ,> +@ , .q,^ Z`,~ ~
, .4B./Z 4D.@@ !& t G +@ d& pG +@ =d. $ 7@ + .,> , 15, -,^ + ., 15, -!$ r G +@ ,~ , -!$ p G +@ ,~ , -6D ,~ 6D + . R X$KU D ,~ S (D D X$ l$ P +@ + .nX$ h$ . +@ ,~ F d$ X$ +@ X$ l$
+@ ,~ F l$ +@ ,~ + ..: x ,~ , .2,~ h$ ( R +@ + ..S (D S Z X *& l$ p +@ X$ l$
,> +@ + .<@@ h$ & +@ + .<: ,^ S X& @@ *& ,~ ,> , .,^ & l& | G ,> +@ + /,^ h& & X& (/6@ h/ H Z XH ,> +@ + .K,^ + ..,^ Z 0H ,~ ,> ,> * , .4+ /,^ ,^ + .?,> ,>
Q*
Q, \J[L , - h"_hb_ab + .h, -, -q ( B( B0 B( !" X"( b $@@(
!"( X"0 *"0 "( B( "0 B0 R`( !"~ AB( @@( @@( !"( X"( @B( *"( b '+ + .j!"Lu B0 @@0 [ ZL, .!7 : ,^ ,^ ,~ ,> ~+?,> q~+<,~ Q" `d + /,> @+4,~ ,> @+6,~ INS I/O data block not set up IDM Illegal data mode for device P{6$ # H + -g,^x ,~ 6$ 6$ / /,~ Z 1F T` + .t4L0
., D, :(E/(@3" + /6B(F6@(A+ //(<3" + /.L(<.L(E+ /
, 0V" 3. /B 5$/16@ . 3$ 7 2f ++ /# f + /# !B6.@ 0 Z " 7@;=/ DE0J + /4L/
+ /7@ 3+ /%@@ 3+ /O@ + /*/ 2=/&,> !B&6.@ 0 ,^ " 7@;=/- FE3d + /"+ 2K ~62 65@@ T*" Y ".0] !B65@ !$/{X$( , 0V3" + /`/ ,> "$( S ; BT*d/9!$/{X$( @."0D" + /@.@/;." D" 6@< BU*d/>,^ (B{^$( # !$/{X$( @ 6@;3D691 .& *d/E&" 6@ ." (B !$/{X$( @ *D/P7@;+ /K3D69+ /O. ?@ /" .HT+ /K!&@ Y/ @4B/S.B
@ , 0Y+ 042";+ 03b@+ /S6@ R+ /[ @/;Q;.T*" , /\+ /S, 0%+ /S7BT,~ O@h/;.B;.B@.BJ,~ 4J/s "/7DE="/a/@/ 4$/s(D{&$ . (D . " 1J .D
.DE6@ R+ /o.D(@.D(JS(;.d(;P *%(@ (@@@ Q& X& *'(E+ /".(; D(T !&@, 0%, 0O@@(T+ /"1j + 0
" S , 0V/ 4"0
" S ( 6@;3D691 .( *f/x(B{&" 6@ ." (B " S 7H;*f/~ HT7@;+ 0.@/;2D69. .( D( 7@<*f0 HU?@ /" *f/!&/{X&( *F0 6B; BT*f0+ /P!${ ; B T & .@/;." D" 1J . 7@<+ 0 BU.& *d0
,> , 0V/ (B{,^ & 6F ." (B !${+ /K.@/;7 7@ ;*h0ah+ 02" ;+ /S6@ R+ /[,> @/;Q 4(6:.;l( T/;l" B S,I S4(0",^ 3D6:+ 6<, /\+ /S,> ,> ,>
T/
;
@/
;., 4L024*0,"" @+ 0- " ;(
{(L{(N{ . Q l( , 0M. =l0.,^ ,^ ,^ + /\6@ R, 0O!${ 7B<*f06/" 7@@+ 0:2BEO@hBE*d05 0" 7@;=0; DEO@ !6@ R+ /"!${Z@4B0F7@h+ 0F@@h." Q" ." 7F<*d0C4F0F1f + 0F@@*" *d0? " 7@;=0GZ@." Q ." Z 1f + /"@@*" + /" H*f/ ?, 15 0c,> * 5 0c,> * 5 0c5d0u ~6B2d(^+ 1
!&(Y! Y aB+ 1
`F.(;! 0d + 0w! [ 6@ /(;XH X Z(^/& F(^1D + 1,> ,> Z [ ." /F , 1E,^ ,^ [ @@ S X& .(0D *& ,~ (O/" 4"1 B(O (J. *(J,~ ,> ,>
/
(O, /+ /0,^ ,^ 6@(},~ + 1
,> , 1,^ ,~ ,> , 1,^ ,~ +"( 7@;=b1ZE/@0$ + 1,,>6E, :X5, D* , /, /0"" .B(@.B(O7@(},~ + .1!+ + 1&+ 1&+ + + 1'+ + + + .B(}+ 1)7 ,~ .B ,(@." Q"@@,$*" ,~ .E D(EZD(@"$ .dE.$ +D(;@@ ZD(JZ" RB(O0J 1J 1 ,~ : (J> (O,~ ,> +* , 1E,^ ,~ ,> X* 5 16,> 7* 5 16,> * 5 16,> Z* 5 16,> R* 5 16,> @* 5 16,> .* 5 16,> +* 5 16,> * 5 164D/
G$ (J D(@ F(JA" B(O "(T1 Z 0D + 2R` Q .& @@ *& 7B(T,~ ZD(T[ , 1E+ 2
,> 0* , 2 1 : ,^ ,~ ,> * 5 2,> * 5 2,> * 5 2,> * 5 2,> * 5 2,> * 5 2,> * 5 2,> * 5 2,> * 5 27D(Y,~ Q + 2"Q Z 4D/
,> 3* , 2 ,^ ,~ ,> @* 5 2%,> ** 5 2%,> 7* 5 2%,> ,* 5 2%,> 6* 5 2%,> +* 5 2%,> 7* 5 2%,> +* 5 2%,> +* 5 2%5 0|7D;+ 2;Q .$ @@*%@,E,> 7@;=29/DE,^ @@;@@@@@E@@J@@O@@Y@@^,~ [ 4D6IZb 2d / ,> ,$ 4$/{ MD" /" , 2?+ /"7@ <+ 2r A/ </ <1B 0D + 2j, 2w+ /" A/ </ <6@ ~7@ ~+ 2m3d + 3
+ 3 3" & 3, 5 6I0J 1J 5 .6I5 6I7@ <+ /0 A/ <0B + 2v, 2w+ /"7@ ~+ 5*+ 3
7@ ++ /
@. E/ @. C/ >. B/ =. D/ ?." 6@ <." 6@ =." 0J 1J + 30J 1J + 3. G 23b ++ /
/$ 2b + /
,B + @ !PF6K@ 0 @@ + 37@ ~+ 5+,> 8 `@/`;.$ (DD$ 4D3,> .`x/$ `x, f6O,^ .B`x.`;/" , 2?,^ + /",^ 6@ D6@ g,~ 6@ + 3, 5,~ + /" / |1" ,~ (Bl . | B ." , 3f / |. ? B D+ /"2d D ,> ,> ,> ,> (B|(D| (F}f6P( 5H31,> ,>
m.* j .* J m." 2" + 30 4H3+,^ ,^ + 3)
A*
. * /* "
d .. 2. + 3; ., 3L 0* `+ 3<.* + 36 * /
$(@
(L /
y.
</, Q
@ j 1 + 3H.0/2p n P n. 3b + 3),^ ,^ ,^ ,^ ,~ ,>6Q ~6Q2d D (F|, / /& / y. </$ Q @ l ,~ ,>6T ~6U2d D (F|. / /& / {. >/$ Q @ n ,~ ,>6X ~6X2d D (F|6 / /& / z. =/$ Q @ v ,~ ,>6[ ~6\2d D (F|8 / /& / |. ?/$ Q @ x ,~ ,>6_ ~6_ ~6b 6g 4 4( 4? 6g 44 6g 4K 6g 6g2d D ,> ,> ,> ,> (B|(D| (F}f6P( 5H4
(J /
y.
<l
2,
(L l
?/
y.
<@@( Q` .* **0 ` 94
A*
. /* "
d .. 2. + 4 ., 3L 0* `+ 4.* + 4 * /
.(/3h n+ 4* H n
@ $(@
(L /
y.
</, Q
@ J 1 + 4 . 3b + 3{,^ ,^ ,^ ,^ ,~ ,>6Q ~6h 3d + 4! D (F|, (F|
6 / /& 6 / y. </$ Q @ L ,~ ,>6T ~6k 3d + 4- D (F|. (F| / /& / {. >/$ Q @ N 5 5G,>6X ~6n 3d + 48 D (F|6 (F| / /& / z. =/$ Q @ V ,~ ,>6[ ~6q 3d + 4D D (F|8 (F| / /& / |. ?/$ Q @ X ,~ ,>6 ~6t 6g 3u 4 45 6g 4* 6g 4A 6g 6g 6g 3# 3I 3\ 6g 3S 6g 3f 6g 6g K J H9 K M p p 6g 4e 4g 4j 6g 4h 6g 4k 6g 6g B6w,~ B6z,~ B6~,~ B7,~ B7,~ 6g 4r 4s 4v 6g 4u 6g 4x 6g 6g,>6Q ~7,>6T ~7
`@/
`;/* @ , f4Q .`;.* + 5,> ,> 8 , 5+ 5 D/ ?@ , 3f D ^: ^ (Bd B | D , 4A/ . ? D D+ 5,> ,> 8 , 5+ 5
`J/
`;D* @ 4 /$ , f4Q `JD" /" O@`}J`x, 2?, 5N: ,^ ,^ ,~ `@/`;D" 4B/f7 + 5&[f4[Zf4[, .R, f4m+ /
!$Lu D @@ Zf4[, .!, f4m+ /
,> G8 + 5,,> ,8 , f4`, Zf4[ZB@@ !$Lu.D [$ .D $ 3D 3 Xf4V/D !$K82D @@ +``(D}.D Zf4[, .!, f4m[`@/`;B`}X$ (D{(D 1$ .$ /",> 7@ ." Z$@ , f6O,^ 4B5B!B`x.`;/" , 2?, 5N, /"1 : ,`@/`;.`x,B`},^ ,~ 7@ f,~ ,> ,>7 ,>7 , 5P,^ ,^ ,^ 4B/ar + 6 .* 7l( + 6 `l + 6al + 6+ 6 `f `r X( `f @`r @P( 3H( g !( GH ,^ ,^ ,^ ,^ ,^ ,^ Bf `f `,~ !& BF ,~ af @ + 6* H ,~ 6& af + 6*7@ @h H ,~ 6& af + 6* H ,~ ,> PF7$,^ ,~ ~7' EXP Expanding low segment to MEF Memory expansion failed *HUMOV Moving low segment to expand area p ,>6:/6:+ 0 Q(l( + 0"x PUF PAGE. UUO failed, error code was AZW Allocating zero words 1RUM Returning unavailable memory ,> + 2B 3 3
MSS /MAXCOR: set too small, expanding to 3# 3I$H n OLC Error outputting area LC OHC Error outputting area HC OLS Error outputting area LS OAS Error outputting area AS OTP Error outputting area TP CBO Cannot build overlays outside section zero + ILC Error inputting area LC IHC Error inputting area HC ILS Error inputting area LS IAS Error inputting area AS ITP Error inputting area TP PLC Area LC overflowing to disk PHC Area HC overflowing to disk PLS Area LS overflowing to disk PAS Area AS overflowing to disk PTP Area TP overflowing to disk ELC Error creating area LC overflow file EHC Error creating area HC overflow file ELS Error creating area LS overflow file EAS Error creating area AS overflow file ETP Error creating area TP overflow file x & f+ 5` " f+ 5f< x SFU Symbol table fouled up MMF Memory manager error 7 + 7Q4T7p, 7E+ 7..
2,
/
!
1N + 754B70=p7,7 l+ 85,~ Q
( ab `: x : x ,~ 7 + 70[ . @ atp + 7:2T + 70+ 72,> ,> ,> `dp + 7r[ . @Q$I *P Q*I [ b7s+ 7C,^ ,^ ,^ + 70,^ ,^ ,^ + 72 `tp + 7L[ 1B + 7u@ "` S` X F *b7J5N7L P [
Z 2J Fj
&*@ 4J7v1*@ ,~ /*@ + 7O,> l@@ l,> ,> ,> ,> "
S ,>
(B/" .B
, 7 / @4B7] x !B7w` 7{@
.$ &$ $$ , 0rX
,>
XB
7Bp + 7f,> . @ , 7+,^ Q C
*|7a,^ Z ,^ .$ &$ $$ , 1D,^ ,^ ,^ ,^ ,^ l
$
&" 2/ / B + 7* !~7|` >+Z $ " + 7>@ P + 7L9
75RGS Rehashing global symbol table from to ISN Illegal symbol name `
."8 4B86@ 2" 3"
+ 7 B
,~ ~8 x } h~ _X{ h }_h~ Xu_8z h{_H y X#|_H'w +~]x/| 83~^x7{ X;z_?~ HC|_8G} 8K{ _XO~
8S}
_hWw ([~ _h_}
HTL Symbol(hash/table$too4large ab+ 8Z ,> [ , 8 ,^ 5 8!,> $ , :9N " 5 :,> " , :,^ , 9N " 5 : & @ )B ." , :=f8/,~ 83+ 2Y:^8w 84+ 2Y:]X8,~ * (,~ , :U
7B( + 8:, 9G " /, :6B( , 97B( ,~ , 9GR( (B}6@ l"` , 9G7@( ,~ "( Q" 5 8QZ 8 , 9 [ 1DYR5b:, 9G " , :R , 9G " 5 8Q 6B , 9 , 9GR !$ bD bD 4F8P " , : , 9G " l" 7B + :`h+ 8U`b5 9C ( [ /" ,> Q(} " -, : 2B:4":6 x + :, 9K*H8`6 x : 7@ + 8`, : , 9G+ 8[,^x + 9F!` )"w,> !` , 8d, : ,^ iB5 : & " )B 5B8i=f8f " )B ." `d " , :=f8h,~ $ + 8n, :9 $ ,> , :$." z3b:+ 8r.$ /:,^ ,> , 8w, :
,^ 5 9 & + 8w b & , :U&" " $ , 9
&( .:, 9} " &" 2 : f + 9&& 21B + 9$" 2. 5 9 ( + 9 b ( &: * , 9
, :
&"j0 , 9 , :
C &" t]$ 4"9N0b 5 9N* , : " 5 :0" + 9!${P9 2B9 *d95$9 " , :R9 , 9G " , :,~ ." ,> " /+ 9 1" + 9/" ,>9$ " , :,^ , 9G " 5 :1" 05 :/" ,> " , :,^ 5 :K>7K>gC3 E` i Y mP M GH KN
TXz9 ": 6@ , 9N": 4B90> &" :Z , 9N " , :$: 4D: " , : 5 9N`B ?5 9= : + 9<4B9= :!U$*D9; :!bB + 9=&" 7 !( +, 9N[ 5 :,> " , : " , :,^ ,~ ,> " -, :,^ 2B:4":", 9K " .5 : 4D: " )B ." , :+ 9H,> [ , 9N, : ,^ Z 7:# & 5"9Q " , : & #` QDx 6@ , 9Q[x ." 0b ." 5 :7:# ( 5"9[/& l( &" # # 1 &" QDx /& 0B , 9[5B9b4f9a " `h ?":$, :=f9``h , :[x ." 0b ." 5 :7:# ( Q( 5 9W & " )B ." , :=f9g,~ ,> ,> !$A`+ 9n,> ,> !$B , 9r )4B9p, :+ 9n,^ ,^ ,~ ,> * )C&9s`f l" * )XD )* ,^ ,~ Q"A`aB,~ ,> 7@ (
& x 4B9B6@ (, :+ 9z B (@@ ) " (5 9w, 9G5 :
,> , :,^ & , 9e5 :,> 4d:, :5 : " 5 : " 5 : " 5 : " aB ,~ 6@ (5 (
" ,~ , 9C+ 8F[ 1D 7@ ,~ + 8U, 9G+ 8[ , 8a+ 8[ L\ -Jan--Feb--Mar--Apr--May--Jun--Jul--Aug--Sep--Oct--Nov--Dec- p mn@0$ $ B
? X , 9G+ 9F $ ,> 4":6[ ."~L&":X(D &$:XG& && Z(H(B . $" 2."n `D + :/&$ 27@ aD g & /" V$" :5F:21( + :5> !$z3(:N+ :5." *d:3/:M. *x d"%:T) ,^ ,~ :T b " 5B:M b d , :U,> &$ :0d ~+ :I&& . :M * 0& * .$ &$ 0F * .(} $$ 6. ^$m4d:H&$ 2/ 0F 1. 0hO@ ,^ $ )w':T2d:U." Q ,~ - < K Z j y ' 6 L\ X
&. *
x Q*x , :e> + :c*
x Q*x ,> , :e> + :c*
x Q*x ,> ,> , :e> ~+ :b*
x Q*x ,> ,> ,> , :e> ~,^ ,^ ,^ ,^ : x ,~ -j( ,> ,> ,> *~,> ~,~ ,^ ,^ ,^ ,^ *x ,~