Trailing-Edge
-
PDP-10 Archives
-
BB-4157F-BM_1983
-
build/lnkerr.rel
There are 3 other files named lnkerr.rel in the archive. Click here to see a list.
(
d 0 (
d H Ym-* / * A * + * d @ @ )B /" (H .( 5D* &" q4BNh1" q+ *
/" q+ * * *. 0$ q/$ q!*&1H + *4F*$+ *Z A" `B @ GNi_ ^ 2" 2b + *% */ . Z + *! 7 + *
Z ,> , , 7x ,> ." , , x A
*." , , * ,^ 7B + *$7@ + *+ *Q"A`,> x 4BNi0B + *#7X W+ *# 0gU *" " , 0" , *"+ * + @ d" + S; 5Qg-C9]<^e B5 kVKNu1ra3 AnI3%/$[O ;faE@VMNM3K2u1CM2-2^Y&u9J MNu3 *U"* *DK3 1F; ?CC %+^a" A=a2 AH[Ju;9gNuDg S?55o MN52kGC-/Y 9]%=]Nm=KG55.#G5=.1 *U*U
*LM-2SC6m,%eVmCK&51!C7,/DS-L3 >lS2 5$g: DY6m9T[C%;"G6 .?SNu7 G65.MhE EkN[?5:yG7E.ZG . "U*U* *] 3 ?#gJDJ]C = " >q]"u=
/E>K K-0li ERS 4MRS%4dY&M99 kN G S6m5Be>#I:
Q( *wM52=a5A
SO7AS4z_ >> [C ; CJe,YS3 5+G;=.j M%2_u>eK %0{ I; /J *U(U *IWU0Ge2 Bw[R;{k; FRY9!Y 9*e%BIk F* Qe3lY6u9_YM92IJ /h uO5G[ eBP *U"U +[O;USB}5t[S <
kFmeG@a
M@ kF" kNMG YO :D_"u>y_6?*iR5Eg _M?` i6eEK *P
U +MJ-2jSR8
A%>Xa6 a?5AaReBg&5C\[ :NSW-8*S6M5=g; D9 x H *U*U* + Gg H H H- H6 HE Hi I I7 I\ I} J JB JU Jc Jn K *U*U* +! K& K, KP KW Kb Km K} L' L? LH Lm M M? Mb N N N "U*U* +* H H H H- H6 HE Hi I I7 I\ I} J JB JU Jc Jn *U*U* +2 K K& K, KP KW Kb Km K} L' L? LH Lm M M? Mb N N (U*U* +; N Gg H H H- H6 HE Hi I I7 I\ I} J JB JU Jc *U*U* +C Jn K K& K, KP KW Kb Km K} L' L? LH Lm M M? Mb N **U* +L N N H H H H- H6 HE Hi I I7 I\ I} J JB JU *U*U* +T Jc Jn K K& K, KP KW Kb Km K} L' L? LH Lm M M? Mb *@ +] N N N You loaded programs containing more ambiguous subroutine
requ +eests than can fit in the tables of one or more overlay
links. You received a LNKARL +n message for each ambiguous
request, and a LNKTMA message for each link with too +v many
requests. You can solve this problem in either of two
ways. One is t +o use the /ARSIZE switch before the
/OVERLAY switch, thus expanding all the tabl ,es. The other
is to use the /ARSIZE switch just before each /LINK switch
to expa ,nd 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 procedu ,2res, but no main program. The
missing start address and undefined symbols will ,: terminate
execution. LINK expected a particular user address to be in mem ,Cory,
but it is not there. This is an internal LINK error.
This message is n ,Kot expected to occur. If it does, please
notify your Software Specialist or se ,Tnd 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 en ,etry point
that is contained in two or more of its successors. You
should revi ,mse your overlay structure to remove the
ambiguity.
If you execute the curr ,vent 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 w -ill be called.
2. If two or more modules satisfying the request are in
me -mory, 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 mo - st links of its path in memory will
be called.
If a module cannot be select -)ed by the methods 2 or 3
above, one of the modules will be called at random. -1 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 -B notify your
Software Specialist or send a Software Performance Report
(SPR) to -K DIGITAL. Either the compiler produced incorrect code or the .REL
file wa -Ss incorrectly modified. Two possible causes for
the error are: a table is too -\ long (more than 2^18
words); or-da table that should have paired words has an
odd length. LNKB4R is usually followed by a fatal error. You have loaded -mmodules compiled with conflicting CPU
specifications, such as loading a MACRO pr -uogram compiled
with the statement .DIRECTIVE KA10 and another compiled
with . -~DIRECTIVE KI10. Recompile the affected modules with
compatible CPU specifications. . You have changed the log file specification. The old log
file is close .d; 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 t .(he same load.
Compile all COBOL programs with the same compiler and
reload. .1 You cannot use COBOL-74 and COBOL files in the same load.
Compile all .9COBOL programs with the same compiler and
reload. You cannot use COBO .BL-68 and COBOL-74 files in the same
load. Compile all COBOL programs with the .Jsame compiler
and reload. You are loading a mixture of COBOL-compiled fil .Ses and
other files. Load one of the COBOL-compiled files first. You canno .[t load modules produced by FORTRAN with modules
produced by GFLoating FORTRAN. C .dompile all FORTRAN modules
the same way, then reload. You attempted to us .le an unimplemented feature. This is an
internal LINK error. This message is not .uexpected to
occur. If it does, please notify your Software Specialist
or send a S .}oftware Performance Report (SPR) to DIGITAL. The module you are attempting to l /oad 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 /C /PU switch. LINK is generating your executable (EXE) file. LINK is b / eginning program execution at the named debugger. Though you have asked for p /(rogram execution, LINK cannot
proceed due to earlier fatal compiler or LINK er /0rors.
Your program is left in memory or in an executable file. A monitor ca /9ll to obtain SYS:UDDT.EXE failed. This can
happen if you have redefined the logi /Acal name SYS: and
neglected to include any directory that contains UDDT.EXE. /J You used a device switch (for example, /REWIND,
/BACKSPACE), but L /RINK cannot associate a device with the
switch. Neither LINK's default device nor a /[ny device you
gave with the /DEFAULT switch can apply. Give the device
with or /c before the switch (in the same command line). You are using the /SET switch /l to reduce the value of an
already defined relocation counter. Unless you k /tnow
exactly where each module is loaded, code may be
overwritten. /} You loaded a FORTRAN-compiled module with DATA statement
assignments to a commo 0n area. The common area is already
defined in an ancestor link. Restructure the lo 0ad so that
the DATA statements are loaded in the same link as the
common area 0 to which they refer. You have a data store for an absolute location outside 0 the
specified link. Load the module into the root link.
NOTE
0'If the location is less than 140, this message has
level 8 and severity 8.
00
Incorrect code has been generated by the F40 compiler.
This message 08is not expected to occur. If it does, please
notify your Software Specialist or s 0Aend a Software
Performance Report (SPR) to DIGITAL. LINK's undefined sy 0Imbol count has become negative. This
message is not expected to occur. If it 0R does, please
notify your Software Specialist or send a Software
Performance 0Z Report (SPR) to DIGITAL. LINK could not make the ALGOL symbol table on th 0ce disk.
You could be over your disk quota, or the disk could be
full or have e 0krrors. LINK could not write the saved file on the disk. You
could be 0t over your disk quota, or the disk could be full
or have errors. LINK has 0|expanded its low segment so large that one of its
larger high segments will not now 1 fit in memory. LINK
will attempt to shrink its internal tables so that th 1
GETSEG will succeed and loading continue. LINK could not write your hig 1h-segment code on the disk.
You could be over your disk quota, or the disk could 1 be
full or have errors. A read error has occurred on the input file. U 1'se of the
file is terminated and the file is released. LINK could not writ 1/e your low-segment code on the disk.
You could be over your disk quota, or the 18disk could be
full or have errors. LINK has finished writing your log 1@ file. The file is
closed. The link is loaded. LINK could not writ 1Ie your local symbol table on the disk.
You could be over your disk quota, or the 1Q disk could be
full or have errors. The map file is completed and closed. 1Z LINK could not write the saved file on the disk. An error has been detect 1bed while reading the named file. An error has been detected while writing the 1k named file. LINK could not write the overlay file on the disk. Long 1s symbol names (more than six characters) are not
implemented. This message 1|is not expected to occur. If
it does, please notify your Software Specialist or sen 2d a
SoftwaredPerformancepReport (SPR) to DIGITAL. LINK is in the last stag 2
example, creating EXE and symbol files, pre 2paring for
execution if requested). You are loading incorrect F40-compiled 2 code caused by a
source statement of the form
DATA A(I),I=1,4/1,2,3,4/
instead of the form
DATA (A(I),I=1,4)/1,2,3,4/
This message is not e 2/xpected to occur. If it does, please
notify your Software Specialist or send 27a Software
Performance Report (SPR) to DIGITAL. LINK is reading one o 2@r both segment overflow files
backwards to perform any needed code fixups. 2HThis may
cause considerable disk overhead, but occurs only if your
program is to 2Qo big for memory. LINK is finished. Control is passed to the monit 2Yor, or to
the loaded program for execution. You cannot load F40 2b-compiled code in an overlay structure.
Recompile with the FORTRAN compiler. 2j LINK cannot find a return from this F40-compiled
subroutine. Th 2sis message is not expected to occur. If it
does, please notify your Software S 2{pecialist or send a
Software Performance Report (SPR) to DIGITAL. You gave 3the /FORSE switch while loading FORTRAN-compiled
code. LINK ignored the switch an 3
d will use the FORTRAN
run-time system. During final processing of your ro 3ot link, LINK found that
the FUNCT. subroutine was not loaded. This would cause an 3
infinite recursion if your program were executed. The
FUNCT. subroutine is 3&requested by the overlay handler, and
is usually loaded from a default system libr 3.ary. Either
you prevented searching of system libraries, or you did
not load 37 a main program from an overlay-supporting
compiler into the root link. 3?
A symbol with a value greater than 777777 was used to
resolve a halfword 3Hreference. This may indicate a that a
global symbol was used improperly. 3P While attempting to run your program from the named file,
LINK received an error 3Yfrom the monitor. This message is
not expected to occur. If it does, please 3anotify your
Software Specialist or send a Software Performance Report
(SPR) to D 3jIGITAL. You have attempted to load high segment code into an
overlay link other than the root. Any high segment code in
an overlaidprogram mu 3{st 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 4
) reassemble after changing your
TWOSEG pseudo-op. Your symbol hash ta 4ble is larger than the maximum LINK can
generate (about 50P). This table size 4 is an assembly
parameter. This message is not expected to occur. If it
does, p 4%lease notify your Software Specialist or send a
Software Performance Report (SPR 4.) to DIGITAL. An error occurred while reading in the ALGOL symbol
tab 46le. Incorrect code has been generated by the F40 compiler.
This message 4?is not expected to occur. If it does, please
notify your Software Specialist or s 4Gend a Software
Performance Report (SPR) to DIGITAL. Incorrect code has 4Pbeen generated by the F40 compiler.
This message is not expected to occur. If i 4Xt does, please
notify your Software Specialist or send a Software
Performanc 4ae Report (SPR) to DIGITAL. Incorrect code has been generated by the F40 4icompiler.
This message is not expected to occur. If it does, please
notify your 4rSoftware Specialist or send a Software
Performance Report (SPR) to DIGITAL. 4z REL block type 12 (chain), generated by the MACRO
pseudo-op .LINK an 5d .LNKEND, must contain a number from 1
to 100 (octal) in its first word. 5 The link word is
ignored. You specified an illegal combination of device 5and data
mode (for example, terminal and dump mode). Respecify a
legal device 5 . An error occurred while reading in your high-segment
code. 5% An error occurred while reading in your low-segment code. An error occurred 5-while reading in your local symbol
table. The INCREMENTAL keyword fo 56r the /MAP: switch is not
implemented. The switch is ignored. LINK need 5>s more memory than is available. You have requested with the /INCLUDE: s 5Gwitch that the
named modules (if any) be loaded. Specify files
contain 5 5Oing 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 messa 5`ge is not expected to occur. If it
does, please notify your Software Specialis 5it or send a
Software Performance Report (SPR) to DIGITAL. An error occurred w 5qhen reading the overlay file. You are attempting to load a file containing an 5z invalid
REL block type 11 (polish). This message is not expected
to occur. 6 If it does, please notify your Software
Specialist or send a Software Perfor 6 mance Report (SPR) to
DIGITAL. A REL block contains a reference to a nonex 6istent psect.
This error is probably caused by a fault in the language
transla 6 tor used for the program. This error is not
expected to occur. If it 6$does, please notify your
Software Specialist or send a Software Performance Rep 6-ort
(SPR) to DIGITAL. The file is not in the proper binary format. It may 65have
been generated by a translator that LINK does not
recognize, or it 6>may be an ASCII or EXE file. One of the new style 1000+ block types has a 6Fn illegal
relocation counter. This message is not expected to
occur. If i 6Ot does, please notify your Software Specialist
or send a Software Performance Repor 6Wt (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 6h your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. 6q The specified module contains an incorrectly formatted
polish fixup blo 6yck (type 11). The store operator
specifies a symbol fixup, but the block en 7ds before all of
the symbol is specified. This error is probably caused by
a fa 7
ult in the language translator used for the program.
This error is not expected to 7 occur. If it does, please
notify your Software Specialist or send a Sof 7tware
Performance Report (SPR) to DIGITAL. The LINK symbol table routine was 7$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 occ 75ur. If it does, please notify your
Software Specialist or send a Software Perform 7=ance Report
(SPR) to DIGITAL. There is an error in the global symbol tabl 7Fe. This is an
internal LINK error. This message is not expected to
occur. 7N If it does, please notify your Software Specialist
or send a Software Performance 7WReport (SPR) to DIGITAL. There is insufficient address space for the symbol t 7_able
between the named psect and the next higher one or the end
of the address 7h space. Restructure your psect layout to
allow sufficient room for the symbol tabl 7pe. LINK has found errors in the switch table passed from the
SCAN module. 7y This is an internal error. This message is
not expected to occur. If it does, 8please notify your
Software Specialist or send a Software Performance Report
( 8
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 8 is not expected to occur. If it
does, please notify your Software Specialist 8# or send a
Software Performance Report (SPR) to DIGITAL. LINK's user 8,UUO (LUUO) handler has detected an illegal
UUO. This is an internal error. Th 84is message is not
expected to occur. If it does, please notify your
S 8=oftware Specialist or send a Software Performance Report
(SPR) to DIGITAL. 8E The range checking of LINK's internal tables and arrays
failed. The address g 8Niven is the point in a LINK segment
at which failure occurred. This is an inter 8Vnal error.
This message is not expected to occur. If it does, please
notify yo 8_ur Software Specialist or send a Software
Performance Report (SPR) to DIGITA 8gL. The specified module contains an incorrectly formatted
polish fixup 8pblock (type 11). Either the last unused
halfword (if it exists) is non-zer 8xo, or there are extra
halfwords following all valid data. LINK ignores the
9extra data. This error is probably caused by a fault in
the language translator 9 used for the program. This error
is not expected to occur. If it does, please n 9otify your
Software Specialist or send a Software Performance Report
(SPR) to DI 9GITAL. The LINK module LNKLOD is beginning its processing. LINK is c 9#reating your log file as a result of defining the
logical name LOG:. LINK 9+ is continuing your log file as a result of the /LOG
switch. LINK is begi 94nning your log file as a result of the /LOG
switch. A REL block type 14 9< (index) for a MAKLIB or FUDGE2
generated library file is inconsistent. The l 9Eibrary is
searched, but the index is ignored. LINK is beginning its pro 9Mcessing by initializing its
internal tables and variables. The length of 9Vthe argument passed by the caller does not
match what the called routine expects 9^it to be. LINK is loading the named module. You used this name for anothe 9gr link. Specify a different
name for this link. The link with this numbe 9or has not yet been loaded. The
/NODE switch is ignored. If you have used li 9xnk numbers
instead of link names with the /NODE switch, you may have
confused t : he 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. Your use of th :+e /NODE switch shows that you want to begin
a new overlay link, but the curren :3t link is not yet
completely loaded. LINK assumes a /LINK switch
immed :<iately preceding the /NODE switch, and loads the link
(without a link name). :D The listed symbols and their values (if any) are those
that are library search :M entry points. The named module contains a new definition of an already
def :Uined global symbol. The old definition is used. Make
the definitions consistent :^and reload. LINK cannot expand memory further. All permitted
ove :frflows to disk have been tried, but your program is
still too large for availab :ole memory. A probable cause is
a large global symbol table, which cannot be overfl :wowed to
disk. 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 symb ;ol 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 a ;3nd low segments, and
remove the TWOSEG or HISEG pseudo-ops. The REGION k ;;eyword for the /OVERLAY: switch is not
implemented. The argument is ignored. ;D Alphabetical or numerical sorting of the map file is not
implemented. ;L The symbols in the map file appear in the
order they are found in the .REL file ;Us. You must use the /MIXFOR switch to load a mixture of
modules compi ;]led by F40 and FORTRAN. The /MIXFOR switch
must precede any file specifications. ;f The current value of MAXCOR is too small for LINK to
operate. You can s ;npeed up future loads of this program by
setting the /MAXCOR: switch to this expande ;wd 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 g <ave 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). The store operator
specifies a memory <*fixup, but the block ends before the
address is specified. This error is probably <2caused by a
fault in the language translator used for the program.
This erro <;r is not expected to occur. If it does, please
notify your Software Speciali <Cst or send a Software
Performance Report (SPR) to DIGITAL. The argument y <Lou gave for the /NODE switch would indicate
a link before the root link. (F <Tor 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 wi <ell happen if LINK finds two type 6 blocks (name)
without an intervening end, or i <nf an end-of-file is found
before the end block is seen. LINK simulates the missi <vng
end block. However, fatal messages usually follow this,
since this conditio <n 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 s =ection. Programs with
high segments must be in section zero. You have spe =!cified the name of a psect after which LINK
should append the symbol table, but n =)o psect with that
name was loaded. Load the named psect or specify an
e =2xisting psect for the symbols. Your program does not have a starting add =:ress. This can
happen if you neglect to load a main program. Program
executi =Con, if requested, will be suppressed unless you
specified debugger execution. =K
You used the /LINK switch, which indicates that you want
=T 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 =ean incorrectly formatted
polish fixup block (type 11). Either the block does not =m
have a store operator, or LINK was not able to detect it
due to the block's in =vvalid 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, p >lease notify your Software Specialist or send a
Software Performance Report (SPR >) to DIGITAL. The called routine does not return a value, however the
cal >ler expected a returned value. An error occurred while writing out the > ALGOL symbol
table. An error has occurred on the output file. The output >)file
is closed at the end of the last data successfully
output. An e >1rror has occurred on the output file. The output file
is closed at the end of >: the last data successfully
output. An error has occurred on the output fil >Be. The output file
is closed at the end of the last data successfully
out >Kput. An error has occurred on the output file. The output file
is closed at >Sthe end of the last data successfully output. An OPEN or INIT monitor call >\ for the specified device
failed. The device may be under another user's contr >dol. The standard released version of LINK does not support F40
code. >m Specify a disk device for the overlay file. An error occurred while writing >u out your high-segment
code. 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. An error occurred while writing out your loca ?(l symbol
table. The /OVERLAY switch must appear before you can use any of
?1 the following switches: /ARSIZE:, /LINK, /NODE, /PLOT,
/SPACE. (It is sufficie ?9nt that the /OVERLAY switch appear
on the same line as the first of these switches ?Byou use.) LINK handles overlays with its LNKOV1 and LNKOV2 modules.
Your ins ?Jtallation has substituted dummy versions of these.
You should request that your ?S installation rebuild LINK
with the reallLNKOV1 and LNKOV2 modules. An error ?[has occurred while writing the overlay file. LINK's module LNKOV2 is writing yo ?dur overlay file. You have specified /SYMSEG:HIGH or /SYMSEG:PSECT: when
loading an overlay structure. Specify /SYMSEG:LOW or
/SYMSEG:DEFAULT. ?u 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 i @s
greater than 512P. This is usually caused by dimensioning
large arrays. Modif @y your programs or load list to reduce
the size of the load. Either recompi @le the PASCAL program with the debug switch,
or load without the /DEBUG:PASCAL swit @ ch. 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 segme @0nt).
2. There are psects above the origin of the high
segment.
3. You @9r program will not fit in memory along with
LINK's final placement code.
4 @A. One or more psects has the read-only attribute.
LINK has saved your program @J as an EXE file on disk and
cleared your user memory. You can use a GET or @RRUN
command to load the EXE file. Your program is too complex to load int @[o memory for one of
the following reasons:
1. There are page gaps between pse @ccts (except below
the high segment).
2. There are psects above the origin @l of the high
segment.
3. Your program will not fit in memory along with
@t LINK's final placement code.
4. One or more psects has the read-only attribute.
LINK will save your program as an EXE file on disk and
automatically run i At, but the EXE file will not be
deleted. LINK found an end-of-file ins Aide a REL block (that is, the
word count for the block extended beyond A the
end-of-file). This error can be caused by a fault in the
language transla A tor used for the program. The Psect named has exceeded the upper limit set A' for it.
No additional chained fixups will be performed, and the
resulting im A0age will probably be incorrect. Symbol table
fixups, however will be performed, a A8nd all map information
will be correct. The load is too large to fit into AA the allowed memory and
your high-segment code is being moved to disk. The AIload is too large to fit into the allowed memory and
your low-segment code is bei ARng moved to disk. The caller has specified that the argument should not be
modified. The called routine contains code which may
modify this argument. Ac In some cases this message will
occur although the argument is not actually Akmodified by
the routine. The load is too large to fit into the allowed me Atmory and
your local symbol tables are being moved to disk. LINK is creati A|ng your overlay tree file. The named psects overlap each other in the indica Bted range
of addresses. If you do not expect this message,
restructuret g Bh the /SET:PSECT:
switch. Your program extend Bs beyond location 777777, which is the
highest location that LINK is capable of lo B ading. You may
be able to make your program fit by moving psect origins,
loweri B'ng the high segment origin, loading into a single
segment, reducing the size of B/arrays in your program, or
using the overlay facility. The REL block is in B8consistent. This may be caused by
incorrect output from a translator (for exam B@ple, missing
argument for an end block). Recompile the module and
reload. BI LINK is reclaiming memory by deleting its internal
tables. The BQ listed symbols and their values (if any) represent
subroutine entry points in t BZhe 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 Bk. You can speed up future loads of
this program by setting /HASHSIZE: this l Bsarge at the
beginning of the load. The listed symbols and values repr B|esent the current
placement of psects in your address space. The REMAP UU CO to place your program's high segment has
failed.urThisImessage is not expected C
does, please notify your Software Specialist or send a
S Coftware Performance Report (SPR) to DIGITAL. LINK attempted to return memory to C the memory manager, but
the specified memory was not previously allocated. This C&
is an internal error. This message is not expected to
occur. If it does, p C/lease notify your Software Specialist
or send a Software Performance Report (SPR) t C7o DIGITAL. There are errors in the local symbol table. Loading
con C@tinues, but any maps you request will not contain
control section lengths. T CHhis is an internal error. This
message is not expected to occur. If it does, CQ please
notify your Software Specialist or send a Software
Performance Re CYport (SPR) to DIGITAL. LINK's hashing algorithms failed; they are trying Cbto
write a new symbol over an old one. You may be able to
load your files in a Cj different order. This is an internal
error. This message is not expected to Cs occur. If it
does, please notify your Software Specialist or send a
Softwar C{e Performance Report (SPR) to DIGITAL. You loaded some SIMULA procedures or cl Dasses, but no main
program. Missing start address and undefined symbols will
te D
rminate 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 D common definition, load the common
area first. LINK is ready to process D& the next command line. The named subroutine is in a different path from D.the
calling link. Redefine your overlay structure so that the
subroutine is?in t D7he 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 out DHputting the .EXE file. You cannot use the /SET: switch to set the n DPamed
relocation counter below its initial value. The attempt
is ignored. DY Relocatable psects are not implemented; you must specify
an explicit absolute or Daigin with the /SET:PSECT: switch
for the named psect. Alphabetical or num Djerical sorting of the symbol table is
not implemented. The symbols appear in the Drorder they are
found. LINK is rearranging the symbol table, and if required, D{ is
converting the symbols from the new to old format as
indicated on the /S EYMSEG, /SYFILE, or /DEBUG switch. The symbol table has been sorted and moved E
according to
the /SYMSEG, /SYFILE, or /DEBUG switch. REL block type 13 E(LVAR) is obsolete. Use the MACRO
pseudo-op TWOSEG. LINK has already lo E aded the initial symbol table. To
prevent this loading, place the /NOINITIAL E%switch before
the first file specification. You have more ambiguous subro E.utine requests (indicated by
LNKARL messages) than will fit in the table for this l E6ink.
Continue loading. Your load will abort at the end with a
LNKABT message; E? if you have loaded all modules, the
message will give the size of the needed EG /ARSIZE switch
for a reload.
You have specified more overlay links th EPan were allowed by
the current value for the /MAXNODE switch. Reload your
pro EXgram with a larger /MAXNODE value. The data type of the argument passed by th Eae caller does
not match what the called routine expects. In producing the in Eidex for a map file, LINK found more
program names than there are programs. Th Ere symbol table
is in error. This is an internal error. This message is
not ex Ezpected to occur. If it does, please notify your
Software Specialist or send a S Foftware Performance Report
(SPR) to DIGITAL. The named symbol was refer F enced in a REL block type 100
(ASSIGN), but the symbol is undefined. This is gene Frated
with the MACRO pseudo-op .ASSIGN. The assignment is
ignored. You F should load a module that defines the
symbol. A reference was made to F%a common block, however the block
does not exist. The listed symbols an F-d their values (if any) represent
symbols not yet defined by any module. Each val F6ue is the
first address in a chain of references for the associated
symbol.
F> If this message resulted automatically at the end of
loading, this is a user FG error. In this case, the load
will continue, leaving references to the FOse symbols
unresolved. Extraction of symbols from a MACRO universal file FX is not
implemented. In a REL block type 2 (symbols), the first 4 bits of F`each
word pair contain the Radix-50 symbol code. LINK found
one or more invali Fid codes in the block. This error can be
caused by a fault in the language transla Fqtor used for the
program. The called routine returns a value which was not Fz expected
by the caller. You gave an undefined global symbol as the start G address.
Load a module that defines the symbol. The named link G contains a call for a subroutine you have
not loaded. If the subroutine is req Guired for execution,
you must reload, including the required module in the
l G ink. You have specified an undefined symbol to a switch that
can only take G$ a defined symbol or a number. Specify the
correct switch value. You gave G-the named symbol as an argument to the /UPTO:
switch, but the symbol was neve G5r defined. Load a module
that defines the symbol, or change your argument to th G>e
/UPTO: switch. LINK has printed the specified symbol, its value and its
attributes as requested. The number of arguments in the routine call is GO not the
number of arguments expected by the called routine. LINK is beginn GWing execution of your program. You omitted required arguments for a switch G`(for example,
/REQUIRE with no symbols). Respecify the switch. One of th Ghe following conditions occurred:
1. The specified file name was illegal.
2. Gq When updating a file, the specified file name did not
match the file being up Gydated.
3. The RENAME monitor call following a LOOKUP monitor
call fail Hed. The named file was not found. Specify an existing file. The named H
directory does not exist on the named file
structure, or the project-prog Hrammer number given was
incorrect. You do not have sufficient access privi Hleges to use the
named file. The directory on the DECtape has no room f H$or the file.
Delete some files from the DECtape or specify another
device. H, Another job is currently modifying the named file. Try
accessing the H5 file later. The named file already exists, or a different file was
spe H=cified on the ENTER monitor call following a LOOKUP
monitor call. NX LINK HF has specified an illegal sequence of monitor calls
(e.g., a RENAME without HNa preceding LOOKUP or ENTER
monitor call, or a LOOKUP after an ENTER). This HWis an
internal error. This message is not expected to occur.
If it does, ple H_ase notify your Software Specialist or send
a Software Performance Report (SPR) to HhDIGITAL. One of the following conditions occurred:
1. A transmission, dev Hpice or data error occurred while
attempting to read the directory or the Hy RIB of the
named file.
2. A hardware-detected device or data error was d Ietected
while reading the named directory's RIB or data block.
3. A softw I
are-detected data inconsistency error was
detected while reading the named I directory's or file's
RIB. NK The named file is not a saved file. This I message can
never occur and is included only for completeness of the
LOOKUP, I# ENTER and RENAME error codes. This message is not
expected to occur. If it I,does, please notify your
Software Specialist or send a Software Performance Rep I4ort
(SPR) to DIGITAL. NK The system cannot supply enough memory to use as buf I=fers
or to read in a program. This message can never occur and
is included only IEfor completeness of the LOOKUP, ENTER and
RENAME error codes. This message is IN not expected to
occur. If it does, please notify your Software Specialist
or s IVend a Software Performance Report (SPR) to DIGITAL. NK The named device is curr I_ently not available. This message
can never occur and is included only for compl Igeteness of
the LOOKUP, ENTER and RENAME error codes. This message is
not expect Iped to occur. If it does, please notify your
Software Specialist or send a Softw @ Ixare Performance Report
(SPR) to DIGITAL. NK The named device dies not exist. JThis message can never
occur and is included only for completeness of the LOOKUP, J
ENTER and RENAME error codes. This message is not
expected to occur. J If it does, please notify your
Software Specialist or send a Software Perfor Jmance Report
(SPR) to DIGITAL. NK The machine does not have a two-regist J#er relocation
capability. This message can never occur and is included
only fo J+r completeness of the LOOKUP, ENTER and RENAME
error codes. This message is J4 not expected to occur. If
it does, please notify your Software Specialist or send J< a
Software Performance Report (SPR) to DIGITAL. You have exceeded the qu JEota of the named directory, or the
entire capacity of the file structure. Delete s JMome files,
or specify a directory or structure with sufficient space. The JVnamed device is write-locked. Specify a write-enabled
device or ask the operat J^or to write-enable the named
device. There is not enough internal monit Jgor table space for the
named file. Try the load at a later time. Because o Jof the named directory's quota or the available
space on the file structure, t Jxhe total number of blocks
requested could not be allocated. A partial allocatio K n
was given. NK The block required by LINK is not available for
all K ocation. This message can never occur and is included
only for completeness of t Khe LOOKUP, ENTER and RENAME
error codes. This message is not expected to occ Kur. If
it does, please notify your Software Specialist or send a
Software Perfo K"rmance Report (SPR) to DIGITAL. You have attempted to supercede the named di @ K+rectory. NK You have attempted to delete a directory that is not
empty. K3 This message can never occur and is included only
for completeness of the LOOKUP, K< ENTER and RENAME error
codes. This message is not expected to occur. If KDit
does, please notify your Software Specialist or send a
Software Performanc KMe Report (SPR) to DIGITAL. One of the sub-file directories in the named path KU 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 Kf-file directory nested
deeper than the maximum level allowed. No file s Kotructure in your job's search list has both the
no-create bit and the write-lo Kwck bit equal to zero, and
has the named directory. NK A GETSEG monitor call wa L s issued from a locked low segment
to a high segment which is not a dormant, acti Lve or idle
segment. This message can never occur and is included
only for Lcompleteness of the LOOKUP, ENTER and RENAME
error codes. This message is not e Lxpected to occur. If
it does, please notify your Software Specialist or send a
Software Performance Report (SPR) to DIGITAL. A LOOKUP and ENTER monitor ca L*ll was given to update a
file, but the file cannot be updated for some r L3eason
(e.g., another user is superceding it or the file was
deleted between L;the time of the LOOKUP and the ENTER). The end of the low segment is above the LD beginning of the
high segment. NX An attempt has been made to run LLa program from a
not-logged-in job. This message can never occur and is
in LUcluded only for completeness of the LOOKUP, ENTER and
RENAME error codes. Th L]is message is not expected to
occur. If it does, please notify your Software Sp Lfecialist
or send a Software Performance Report (SPR) to DIGITAL. NK The ENQ/ LnDEQ facility has been used for simultaneous
updating of the named file, but Lwsome ENQ/DEQ requests are
still outstanding and the file cannot be closed. Thi Ls
message can never occur and is included only for
completeness of the MLOOKUP, ENTER and RENAME error codes.
This message is not expected to occur. If i Mt does, please
notify your Software Specialist or send a Software
Perform Mance Report (SPR) to DIGITAL. NK The named file has a bad EXE format director M!y. This
message can never occur and is included only for
completeness M* of the LOOKUP, ENTER and RENAME error codes.
This message is not expected to occu M2r. If it does, please
notify your Software Specialist or send a Software
M; Performance Report (SPR) to DIGITAL. NX An attempt has been made to run an EXE- MCformat file with a
non-.EXE extension. EXE format files (those with an
in MLternal directory) must have the extension .EXE. This
message is not expected MT to occur. If it does, please
notify your Software Specialist or send a M]Software
Performance Report (SPR) to DIGITAL. An attempt has been made to r Meun an EXE-format file with a
directory that is too large for the monitor to ha Mnndle.
This message can never occur and is included only for
completeness of Mv the LOOKUP, ENTER and RENAME error codes.
This message is not expected to occur. MIf it does, please
notify your Software Specialist or send a Software
Per Nformance Report (SPR) to DIGITAL. The monitor's ability to accept another netw Nork connection
has been exceeded. The named task is not available. Speci Nfy an existing task
name. You have specified a network node that does no N!t exist.
Wait for the node to come up or specify an existing
network node " N). NX This message indicates that a LOOKUP, ENTER or RENAME
monitor call N2 error occurred with an error code larger in
number than the errors LINK knows abo N:ut. This message is
not expected to occur. If it does, please notify your
NCSoftware Specialist or send a Software Performance Report
(SPR) to DIGITAL. NX NK This message can never occur and is included only for
completeness of the LOO NTKUP, ENTER, and RENAME error codes. This message is not expected to occur. N\ If it does, please
notify your Software Specialist or send a Software
Pe Nerformance Report (SPR) to DIGITAL. 9*
,^ ,~ RPaN R_n R_6n R_l: P ]8{ qboI *$
]m ]}e *$]` * D"]a *]a * ]b * ]b *#]g *^
^ *
^$K Nh D"H Zm" T
Gg
I7
I\
I}
J
JB
JU D"
Jc
Jn
K
K&
K,
KP
KW
Kb D"
Km
K} H-
0 L'
1 L?
1 LH
2 Lm
2 M
3 M? D"
3 Mb
4 N H6
D N
E N
E N* HE Hi I D"I$ H S" + +l H +m H
Z I7
Z I\
Z I}
Z
J
Z
JB D"
Z JU
Z Jc
Z
Jn +m H
Z K
Z K&
Z K,
Z KP
Z KW D"
Z Kb
Z Km
Z K} +n H-
Z0 L'
Z1 L?
Z1 LH
Z2 Lm
Z2 M D"
Z3 M?
Z3 Mb
Z4 N +n H6
ZD N
ZE N
ZE N* +o HE +o Hi D" +p I%C" +* Q, Gg Q- H
6 I7
6 I\
6 I}
6
J
6
JB D"
6 JU
6 Jc
6
Jn Q- H
6 K
6 K&
6 K,
6 KP
6 KW D"
6 Kb
6 Km
6 K} Q. H-
60 L'
61 L?
61 LH
62 Lm
62 M D"
63 M?
63 Mb
64 N Q. H6
6D N
6E N
6E N* Q/ HE Q/ Hi @" Q0 Iz#" +;S1,H "QL H "QM H
i@ I7
i@ I\
i@ I}
i@
J D"
i@
JB
i@ JU
i@ Jc
i@
Jn "QM H
i@ K
i@ K&
i@ K,
i@ KP D"
i@ KW
i@ Kb
i@ Km
i@ K} "QN H-
i@0 L'
i@1 L?
i@1 LH
i@2 Lm D"
i@2 M
i@3 M?
i@3 Mb
i@4 N "QN H6
i@D N
i@E N
i@E N* "QO HE D" "QO Hi "QP I0}3" +MI8!" *&
(
d * d( < d(QK *L*7qx Y Z Z * B NK MO6 NXWE!" \B: /W=B D hD2 *%gk* *#gkD@ *g
qx * H @ @ +Mm3k H @ @ +;m2j H @ @ +*m2^ H @ @ +m2S 8 * ( ( Nj