Google
 
Trailing-Edge - PDP-10 Archives - ap-c796e-sb - lnkerr.rel
There are 3 other files named lnkerr.rel in the archive. Click here to see a list.
 (
d0(
dH CL/z	*(+ Z0B\Y+ c*" 
(d@@)B/"(H.(5D	"E(&"q4Bc1"q+^	2"2b+/.Z+!7 +Z,>,,	 Q7x,>.",,,^7B+7@+++ d"Z0D\Y+	"A(",>+S;
eTK>,Ck<SJ
dK"A	("U**K>L!GN4K>|8Y:d

}[?4SINOK$K?4OkJ	*(U3G4;a2Sl	HINdM?4[hE

IN|wgRSZ

K2mg,3KNt]	"U Q
;MN4gY&L

Hi$MNLoK2t|M2,ZMNtvK3C$K3[Jt
eVe,g]Y

B]$8_MGM,OSN$
uK&$PC7DS	*E(U(LS2	kg:_CG6aSNt!SN|<G64okN

'a"|SO$o_2	ON,$g;*M&tP	"
E*Ue{_4JS"	c_dO_ll]dggJWaM[O _	aV4$	**
]YNlD&aN4K7S
	1"tf?40[Nt
S	 U UfW&

1RR$mY:

_a3QRdHKcuSfS6

	yKcK,3	*Q*niRS	RS$	S$	WkN2i6

<SS$

I:

M49a4nSOYY:

h	*QU"w[Cg>,:I;IWT

W[R6k;g7e$s	"(U
QNd%Y6t

[]SIJ;]D	uO4ESL	CkzSB|
6[SEg3ra
LY	6iR4]MJ,fgNta	"QU*gO$og&4Q[	**U*!.Lloaded programs containing more  ambiguous	subroutine
	requests than can fit in the 	 Ttables of one or more overlay
	links.	You received a LNKARL message for  each  ambig	 ]uous
	request,  and a LNKTMA message for each link with too many
	requests.  You ca	 en solve this problem  in  either  of  two
	ways.	One  is  to  use  the  /ARSIZE	swit	 nch	before the
	/OVERLAY switch, thus expanding all the tables.  The other
	is to us	 ve the /ARSIZE switch just before each /LINK switch
	to expand the tables separately.	 	You loaded ALGOL procedures, but  no  main  program.   The
	missing start	  address and undefined symbols will terminate
	execution.	LINK expected a par	 ticular user address to be  in  memory,
	but  it  is  not  there.   This is an inter	 nal 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 DIGI	 )TAL.	More than one successor link can satisfy a  call  from	an
	ancestor  link	 2.  The ancestor link requests an entry point
	that is contained in two or more of it	 :s  successors.   You
	should	 revise  your  overlay	structure  to  remove  the
	amb	 Ciguity.

	If you execute the current load, one of the following will
	occur when t	 Khe ambiguous call is executed:

	1.  If only  one  module  satisfying  the  request	 T  is	in
	    memory, that module will be called.

	2.  If two or more modules sati	 \sfying the request  are	in
	    memory,  the  one  with  the most links of its path 	 ein
	    memory will be called.

	3.  If no modules satisfying the request  are  in	 m  memory,
	    the one with the most links of its path in memory will
	    be calle	 vd.

	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  re	 quest  for  0
	words.	 This  is an internal LINK error.  This message is
	not expec	 ted to occur.	If it  does,  please  notify  your
	Software  Specialist or send a Sof	 tware Performance Report
	(SPR) to DIGITAL.	Either the compiler produced incor	  rect code  or  the  .REL
	file wasincorrectly	modified.  Two possible causes for
	the error are:	a  table  is  too  long  (more	than  2^18
	words);   or  a table th	 1at should have paired words has an
	odd length.  LNKB4R is usually followed by a fat	 :al error.	LINK cannot expand core further.  All permitted  overflows
	to  disk	 B  have	been  tried, but your program is still too
	large for available memory.  A pr	 Kobable cause is  a  large
	global symbol table, which cannot be overflowed to disk.	 S	You have changed the log file device.  The old log file is
	closed;   further 	 \ log	entries are written in the new log
	file.	You cannot use COBOL-68 and C	 dOBOL-74  files  in  the  same
	load.	Compile  all COBOL programs with the same compi	 mler
	and reload.	You are loading a  mixture  of	COBOL-compiled	files  and
		 uother files.  Load one of the COBOL-compiled files first.	You attempted to us	 ~e 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 S	 oftware Performance Report (SPR) to DIGITAL.	LINK is generating your .EXE file.	 	A monitor call for SYS:UDDT.EXE failed.	You  used  a  device   s	  witch	(for   example,   /REWIND,
	/BACKSPACE),  but  LINK cannot associate a device 	 (with the
	switch.  Neither LINK's default device nor any device  you
	gave  with th	 1e /DEFAULT switch can apply.  Give the device
	with or before the switch (in the sam	 9e command line).	You are using the /SET switch to reduce the  value  of	an
	 B	already  defined  relocation  counter.	 Unless  you  know
	exactly  where	each  mod	 Jule  is  loaded,  code   may	be
	overwritten.	You loaded a FORTRAN-compiled	 S  file  with  DATA  statement
	assignments  to a COMMON area.	The COMMON area is alr	 [eady
	defined in an ancestor link.	You have a data store for an absolute l	 docation outside the
	specified link.  Load the module into the root link.


				 	 l  NOTE

	    If [octal] is less	than  140,  this  message  has
	    level 8 and se	 uverity 8.


		Incorrect code has been generated  by  the  F40  compiler.
	This message is not expected to occur.	If it does, please
	notify	your  Software	S	 pecialist  or	send  a   Software
	Performance Report (SPR) to DIGITAL.	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   Softwar	 e
	Performance Report (SPR) to DIGITAL.	LINK could not make the ALGOL symb	 (ol table  on	the  disk.
	You  could  be	over your disk quota, or the disk could be
	 0	full or have errors.	LINK could not write the saved	file  on  the  disk.   	 9You
	could  be  over your disk quota, or the disk could be full
	or have errors.	 A	LINK could not write your high-segment code on	the  disk.
	You  could  be	over	 J your disk quota, or the disk could be
	full or have errors.	A read error h	 Ras occurred on the input device.	Use of the
	device is terminated and the file is re	 [leased.	The status
	is represented by the right half of the file status  word.
	Ref	 cer	to   the   DECsystem-10   Monitor  Calls  for  the
	explanation of the file statu	 ls bits.	LINK could not write your low-segment code  on	the  disk.
	You  coul	 td  be	over your disk quota, or the disk could be
	full orhaveerrors.	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	fil	 e  on  the  disk.   You
	couldbeover your disk quota, or the disk could be full
	orhaveerrors.	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	 0 the DECsystem-10 Monitor Calls  for
	the explanation of the file status bits.	 8	An error has been detected while writing the  named  file.
	The  status  is  repres	 Aented by the right half of the file
	status word.  Refer to the DECsystem-10 Monitor	 I Calls  for
	the explanation of the file status bits.	LINK cannot write the ov	 Rerlay file on disk.   You  may	be
	over  your disk quota;	the disk may be full;  or 	 Zthe disk
	may have errors.	Long symbol names  (more  than	six  characters)  	 care  not
	implemented.   This  message is not expected to occur.	If
	it does, pleas	 ke notify your Software Specialist or send  a
	Software Performance Report (SPR) to D	 tIGITAL.	LINK is expanding memory to the specified amount.  You can
	speed  u	 |p  future loads of this program by using the /CORE
	switch to allocate the required 	 core.	LINK is in the last stages of loading  your  program  (for
	example,	Xsymbol files, preparing for
	execution if requested).	 	You are loading incorrect F40-compiled 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 expected to occur.	If it does, please
	notify	 /	 your  Software  Specialist  or  send  a  Software
	Performance Report (SPR) to DIG	 8ITAL.	LINK  is  reading  one	or  both  segment  overflow  files
	backwards	 @  to  perform	any  needed code fixups.  This may
	cause considerable disk overhead, 	 Ibut occurs only if  your
	program is too big for memory.@	LINK is f	 Qinished.  Control is passed to the monitor, or to
	the loaded program for execution.	"Z@"	You cannot load F40-compiled code in an overlay structure.
	Rec	 bompile with the FORTRAN compiler.@0	LINK  cannot  find  a  return	from	 k   this   F40-compiled
	subroutine.	You gave the /FORSE switch while loadin	 sg  FORTRAN-compiled
	code.	During final processing of your root link, LINK f	 |ound that
	the FUNCT. subroutine was not loaded.  This would cause an
	infinite rec	 ursion if your  program  were  executed.   The
	FUNCT.asubroutine isdrequested by th	 
	is usually loaded from a default system  library.   Either
	 	you  prevented	searching  of system libraries, or you did
	not  load  a  main  prog	  ram  from  an	overlay-supporting
	compiler into the root link.@=	You 	 &have set the high-segment counter to a page containing
	low-segment code.  Reload, u	 /sing the /SET:.HIGH.:n switch,
	or (for MACRO programs)  reassemble  after  changing	 7  your
	TWOSEG	 pseudo-op.    Note   that   you  cannot  set  the
	high-segment cou	 @nter  below  400000  for  a  KI10  monitor
	before 5.07, or for any KA10 monitor.	 H	Your symbol hash table is larger than the maximum LINK can
	generate  (about  	 Q50P).   This	table  size is an assembly
	parameter.  This message is not expected to	 Y occur.  If	it
	does,  please  notify  your  Software Specialist or send a
	Softwar	 be Performance Report (SPR) to DIGITAL.	An error  occurred  while  reading  in		 jthe  ALGOL  symbol
	table.	Incorrect code has been generated  by  the  F40  	 scompiler.
	This message is not expected to occur.	If it does, please
	notify	your  	 {Software	Specialist  or	send  a   Software
	Performance Report (SPR) to DIGITAL.	 		Incorrect code has been generated  by  the  F40  compiler.
	This message is no	 	

t expected to occur.	If it does, please
	notify	your  Software	Specialist  or	send  	 	a   Software
	Performance Report (SPR) to DIGITAL.	Incorrect code has been 	 	generated  by  the  F40  compiler.
	This message is not expected to occur.	If it doe	 	&s, please
	notify	your  Software	Specialist  or	send  a   Software
	Performance Rep	 	.ort (SPR) to DIGITAL.	A blank COMMON	area  cannot  be  expanded  once  defin	 	7ed.
	Either	load the module with the largest definition first,
	or use the /COMMON 	 	?switch to reserve the needed space.	LINK needs more memory than is availabl	 	He.	You specified an illegal combination of  device  and  data
	mode  (for  e	 	Pxample, terminal and dump mode).  Respecify a
	legal device.	An OPEN or INI	 	YT monitor  call  for  the  specified  device
	failed.  The device may be under anoth	 	aer user's control.	An error  occurred  while  reading  in	your  high-segment
	 	j	code.	An error occurred while reading in your low-segment code.	An e	 	rrror occurred  while  reading  in  your  local  symbol
	table.	The INCREMENTA	 	{L keyword for /MAP is not implemented.   The
	switch is ignored.	LINK atte	 
mpted 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 th	 
.e DECsystem-10  Monitor  Calls  for  the
	explanation of the file status bits.	 
6	You are attempting to load a file  containing  an  invalid
	REL  Block  Type  11  (	 
?POLISH).   This is an internal LINK
	error.	This message is not  expected  to  occur	 
G.   If	it
	does,  please  notify  your  Software Specialist or send a
	Software Per	 
Pformance Report (SPR) to DIGITAL.	A REL block contains a reference to a  nonex	 
Xistent  PSECT.
	This  error  is probably caused by a fault in the language
	transla	 
ator used for the program.	The file is not in the proper binary format.  It 	 
imay  have
	been   generated  by  a  translator  that  LINK  does  not
	recognize, o	 
rr it may be an ASCII or .EXE file.	The named symbol either has a partial  defin	 
zition  and	an
	explicit  definition,  or  has	two  partial  definitions.
	Later res	 olution of partial definitions may  result  in  a
	multiply-defined global symbol.
	 
	A partial definition is one in which a symbol  is  defined
	in  terms  of  other 	  undefined symbols.  If your code has
	A=:B##+3 and A=:7, then either B## will have 	 to be 4 or  A
	will be multiply-defined.	The LINK symbol table routine was 	 %called  with	the  blank
	symbol.This is an internal LINK error.  This message is
	not expected to occur.	If it  does,  please  notify  your
	Software  Specialist or	 6 send a Software Performance Report
	(SPR) to DIGITAL.	You are attempting 	 >to load a file  containing  an  invalid
	REL  Block  Type  11  (POLISH).   This is a	 Gn internal LINK
	error.	This message is not  expected  to  occur.   If	it
	does,  p	 Olease  notify  your  Software Specialist or send a
	Software Performance Report (SPR	 X) to DIGITAL.	There is an  error  in	the  global  symbol  table.   This
	mess	 `age  is  not  expected  to	occur.	If it does, please
	notify	your  Software	Speciali	 ist  or	send  a   Software
	Performance Report (SPR) to DIGITAL.	LINK has found	 q errors in the switch table passed from  the
	SCAN  module.	This message is not expe	 zcted to occur.	If
	it does, please notify your Software Specialist or send  a
	Soft	 

ware Performance Report (SPR) to DIGITAL.	REL Block Type 12 (CHAIN) must con	 

tain a number from 1	to
	100 (octal) in its first word.	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 message is  not  expected
	to  oc	 

$cur.   If  it  does,  please  notify  your  Software
	Specialist or send a Software 	 

-Performance Report (SPR)	to
	DIGITAL.	Some modules loaded were compiled for t	 

5he KA10	processor,
	and  some  for	the KI10 processor.  Recompile so that all
	modu	 

>les are compiled for the same processor.	The LINK module LNKLOD is beginnin	 

Fgitsprocessing.	A REL Block Type 14 (INDEX) for a MAKLIB or FUDGE2 library

O
	file  is  inconsistent.   The library is searched, but the
	index is ignored.	 

W	LINK is ready for your input.	LINK is loading the named module.	 

`	You used this name for another link.  Specify a  different
	name for this link.	 

h	LINK cannot find the named link in memory.   This  message
	is  not expected t	 

qo occur.  If it does, please notify your
	Software Specialist or send a Software Per	 

yformance  Report
	(SPR) toaDIGITAL.	The link with this number has not yet  	 
	/NODE  switch  is  ignored.  If you have used link numbers
	in	 
stead of link names with the /NODE switch, you may  have
	confusedavthe  link, numbe	 
	names.	The name you gave with the /NODE switch	 
	anyNloadedilink.hoThetswitchuisaignored.	Your use of th	 
	a  new	overlay ylink,	but  the  curren	 
	completely  loaded.    LINK   assumes	a   /LINK   switch
	immed	che /NODE switch, and loads the link
	(withoutea linklname).	en of  an  already
	definedewglobalisymbol.	.
	theNdefinitionsnconsistentoandereload.	o
	the ispecified	area.	ar	n
	AS=ALGOL symbol table, BG=bound global symbols, DY=	 
	free  core, FX=fixup area, GS=global symbol table, HC=your
	high-segmentur	-  code,  LS=local
	symbolTtables,tRT=relocationntables.	a	Overlay structures consi	 
	not supported.	Alphabetical or numerica	 l sorting of the map file  is  not
	implemented.   The  symbols  in the map file app	 
ear in the
	order they are found in the .REL files.	You must use the /MIXFOR	   switch  to  load  a  mixture	of
	modules  compiled  by F40 and FORTRAN.	The /MIXFO	 R switch
	must precede any module names or filenames.	The current value of MAX	 #COR  is  too  small  for  LINK	to
	operate.  You can speed up future loads of this p	 ,rogram by
	setting the /MAXCOR switch to this expanded  size  at  the
	beginning of	 4 the load.	You are attempting to set MAXCOR so  large  that  the  low
	seg	 =ment cannot fit before the high segment.  LINK will use
	only the core indicated.	 E	LINK needs more space  than  you  gave	with  the  /MAXCOR
	switch.   Give	a  n	 New	/MAXCOR  switch  with at least the
	required size.	The argument you gave fo	 Vr the /NODE switch would  indicate
	a  link  before  the  root  link.   (For  exampl	 _e,  from a
	position after the third link in a path, you  cannot  give
	/NODE:-4.)	 g	Your program is too large to load  from  LINK.	 LINK  has
	saved  it  as  an  	 p.EXE file on disk and cleared your user
	memory.  You can use a GET or RUN command t	 xo load the .EXE
	file.	If  it	is still too large:  use a larger machine;
	obtain	a 	  larger  core  limit;   or  define  an   overlay
	structure for your program.	 		Your program is too large to load into memory;	LINK saved
	it  as	an  .EXE  file	on	   disk.  LINK will automatically
	execute the program with a RUN monitor call, but t	 he  .EXE
	file will not be deleted.	No REL Block Type 5 (END) was found in 	 #the  named  module.
	This  will  happen  if LINK finds two Type 6 Blocks (NAME)
	wi	 +thout an intervening END, or if an end-of-file is  found
	before	the  END.   Fatal  	 4messages  usually  follow  this
	message.	You gave a device that does  not  	 <exist  on  this  system.
	Correct your input files and reload.	An error occur	 Ered  while  writing  out	the  ALGOL  symbol
	table.	Specify a disk device fo	 Mr the overlay file.	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 represen	 ^ted by the right half  of  the  file
	status	word.  Refer to the DECsystem-10 Monito	 gr Calls for
	the explanation of the file status bits.	An error has occurred on	 o the output file.  The output file
	is closed at the end of the last data successful	 xly 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 b	 	its.	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 righ	 t half  of  the  file
	status	word.  Refer to the DECsystem-10 Monitor Calls for
	t	 "he explanation of the file status bits.	An error has occurred on the output fil	 +e.  The output file
	is closed at the end of the last data successfully output.
	Th	 3e 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	 D handles F40-compiled code	with  its  LNKF40  module.
	Your  installation  has  subs	 Mtituted  a  dummy	version of
	LNKF40.   You  can  either  recompile  with  the   FOR	 UTRAN
	compiler, or request your installation to reload LINK with
	the real LNKF40 m	 ^odule.	An error occurred  while  writing  out	your  high-segment
	code.	 f	Internal symbols in  the  overlay  handler  could  not	be
	referenced.   If  y	 oou  are using your own overlay handler,
	this is a user error;  if not, it is  an  i	 wnternal  error.
	This message is not expected to occur.	If it does, please
	notify		 your  Software	Specialist  or	send  a   Software
	Performance Report (SPR) to DIGITA	 L.	An error  occurred  while  writing  out  your  low-segment
	code.	 	An error occurred while  writing  out  your  local  symbol
	table.	The /OVER	 LAY switch must appear before you can use any	of
	the  following	switches:   /ARSIZE	 ",  /LINK, /NODE, /PLOT,
	/SPACE.(Itis sufficient that the /OVERLAY switch appear
	on the same line as the first of these switches you use.)	An error has occurr	 3ed 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
	explan	 Dation of the file status bits.	LINK's module LNKOV2 is writing your overlay	 L file.	The job is too large to fit into the  allowed  memory  and
	the ALGO	 UL 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	 f arrays.  Modify your programs or load list to reduce
	the size of the load.	 n	LINK found an end-of-file inside a REL Block (that is, the
	word   count   for   th	 we   block   extended   beyond   the
	end-of-file).	The job is too large to 	 fit into the  allowed  memory  and
	your high-segment code is being moved to disk.	 	The job is too large to fit into the  allowed  memory  and
	your low-segment c	 ode is being moved to disk.	The job is too large to fit into the  allowed  me	 mory  and
	your local symbol tables are being moved to disk.	The feature yo	 !u requested is not available.	A PAGE. UUO to rearrange LINK's address space has	 *  failed,
	and  returned  the  error  code given.	You may be able to
	avoid this pr	 2oblem by varying  the  physical  and  virtual
	limits	for  the  job, or by varying t	 ;he values given with
	the /CORE and /MAXCOR switches.  This is an internal  LINK
	e	 Crror.	 This  message	is  not  expected to occur.  If it
	does, please notify your So	 Lftware  Specialist  or  send  a
	Software Performance Report (SPR) to DIGITAL.	 T	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  mod	 eule  and
	reload.	The global symbol you gave with the  /SET  switch  is  not
	defined.  Load a module that defines the symbol.	LINK  is  reclaiming  me	 vmory  by  deleting  its   internal
	tables.	LINK is expanding the global  symb	 ol  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  set	 ting  /HASHSIZE  this  large  at the
	beginning of the load.	LINK attempted	  to return memory to the memory manager, but
	the  specified	memory	was  never  allo	 !cated to this job.
	This message is not expected to occur.	If it does, please
	noti	 )fy	 your  Software  Specialist  or  send  a  Software
	Performance Report (SPR) to D	 2IGITAL.	There are errors  in  the  local  symbol  table.   Loading
	continue	 :s,  but  any  maps  you  request  will not contain
	control section lengths.  This m	 Cessage is not expected	to
	occur.	If it does, please notify your Software Specialist	 K
	or send a Software Performance Report (SPR) to DIGITAL.	LINK's hashing algo	 Trithms  failed;   they  are	trying	to
	write  a  new  symbol over an old one.	You ma	 \y be able to
	load your files in a different order.  This message is not
	expected 	 e to  occur.   If  it  does,  please  notify  your
	Software Specialist or send a Sof	 mtware Performance  Report
	(SPR) to DIGITAL.	You have  specified  /SYMSEG:	 vHIGH  or  /SYMSEG:PSECT  when
	loading  an  overlay  structure.   Specify  /SYMSEG:L	 ~OW or
	/SYMSEG:DEFAULT.	You loaded some SIMULA procedures or classes, but no  	 main
	program.  Missing start address and undefined symbols will
	terminate executi	 on.	You defined a COMMON  symbol  with  the  same  name  as  a
	non-COMMON  s	 ymbol.   You must decide which definition you
	want.  If you want the COMMON definit	  ion, load the  COMMON
	area first.	LINK is ready to process the next comma	 )nd line.	The named subroutine is  in  a	different  path  from  the
	calling l	 1ink.  Redefine your overlay structure so that the
	subroutine is in the correct path	 :.	An error occurred in outputting the .EXE file.	 The  file
	was  closed  a	 Bfter the last successful output.	The status
	is represented by the right half of the	 K file status  word.
	Refer	to   the   DECsystem-10   Monitor  Calls  for  the
	expl	 Sanation of the file status bits.	You cannot /SET the named  relocation  count	 \er	below  its
	initial value.	The attempt is ignored.	Alphabetical or numerica	 dl sorting of the symbol  table	is
	not implemented.  The symbols appear in the order	 m they are
	found.	LINK is rearranging the symbol table, and if required,	is
	 u	converting  the  symbols  from	the  new  to old format as
	indicated on the /SYMSEG	 ~, /SYMBOL, or /DEBUG switch.	The symbol table has been sorted and  moved  acco	 rding	to
	the /SYMSEG, /SYMBOL, or /DEBUG switch.	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 switc	  h before
	the first file specification.	You cannot expand an already defin	 (ed  COMMON  area.   Load
	the  largest  definition of a given named COMMON first, or	 1
	use the /COMMON switch to reserve space for it.   You  can
	define a new COMMON a	 9rea with a new name any time.	You have more ambiguous subroutine requests (indi	 Bcated	by
	LNKARL messages) than will fit in the table for this link.
	Continue load	 Jing.  Your load will abort at the end with  a
	LNKABT	message;   if  you  have  load	 Sed  all modules, the
	message will give the size of the  needed  /ARSIZE  switch
	f	 [or a reload.	In producing the index for a map  file,  LINK  found  more
	pro	 dgram  names	than there are programs.  The symbol table
	is in error.  This message i	 ls not expected to  occur.	If
	it  does, please notify your Software Specialist or se	 und a
	Software Performance Report (SPR) to DIGITAL.	The named symbol was ref	 }erenced in an  .ASSIGN	pseudo-op,
	but  the  symbol  is  undefined.  The .ASSIGN pse	 udo-op is
	ignored.  You  should  load  a	module	that  defines  the
	symbol.	 	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 Rad	 ix-50 symbol code.	LINK found
	one or more invalid codes in the block.	You 	 (gave an undefined global symbol as the start  address.
	Load a module that defines t	 0he symbol.	The named link contains a call for a subroutine  you  have
	not	 9  loaded.  If the subroutine is required for execution,
	you must reload, including 	 A the  required  module  in  the
	link.	You omitted required arguments for a sw	 Jitch (for  example,
	/REQUIRE with no symbols).  Respecify the switch.	One 	 Rof the following conditions occurred:

	1.  The filename given was illegal.

	2. 	 [ When updating a file, the filename given did not match
	    the file to be updated.	 c

	3.  The RENAME monitor call following a LOOKUP monitor call
	    failed.	 l	The file requested by the user was not  found.   The  user
	shouldrespecify the co	 trrect filename.	The directory does not exist on the named file  structure,
	or the project-programmer number given was incorrect.	The user does not h	 ave the correct  privileges  to  access
	the named file.	The directory on th	 e DECtape has no room for the file.	Another user is currently modifying the	  named  file.   The
	user should try accessing the file later.	The specified 	 filename  already  exists,  or  a  different
	filename was given  on  the ENTER moni	 @'tor call following a
	LOOKUP monitor call.R	The user specified an illegal sequ	 0ence  of  monitor  calls
	(e.g., a RENAME without a preceding LOOKUP or ENTER, or  a	 8
	LOOKUP after an ENTER).	One of the following conditions occurred:

	1. 	 A Transmission, device, or  data  error  occurred  while
	    attempting to read the 	 IUFD or RIB.

	2.  A hardware-detected device or data error was  detected
	    whil	 Re reading the UFD RIB or UFD data block.

	3.  A  software-detected  data  inconsis	 Ztency  error   was
	    detected while reading the UFD RIB or file RIB.E	The 	 cnamed file is not a saved file.E	The system cannot supply enough memory to us	 @ke  as  buffers
	or to read in a program.E	The  device  indicated  by  the  u	 tser  is  currently   not
	available.E	The device specified by the user  does 	 | not  exist.E	The  machine  does  not  have  a  two-register  relocation
	cap	 ability.	There is no room on the file structure for the named file,
	orerthe 	   file  structure  would be
	exceededifthe file were placed	  on the structure.	The user cannot write on the specified device  because  it
	iswrite-locked.	There is not enough table space in  the  monitor's  4-WOrd
	blocks for the specified file. The user should try running
	the job at a later tim	 /e.	Because of the user's quota or the available space on  the
	device,  the 	 8total number of blocks requested could not be
	allocated and a partial allocation wa	 @@s given.E	The block required by LINK is not available for allocation.	 I	The user attempted to  supersede  an  existing  directory.E	The user attempted 	 Qto delete  a  directory  that  was  not
	empty.	The required sub-file directo	 Zry in the specified path  was
	not found.	A LOOKUP and ENTER monitor call wa	 bs performed  on  generic
	device DSK and the search list is empty.	An attemp	 kt was made to create a subfile  directory  nested
	deeper  than  the maximum level a	 sllowed.	No file structure in the job's search list  has  both  the
	no-creat	 |e bit and the write-lock bit equal to zero and has
	thegUFDtor SFD specified by the 	  default or explicit path.E	A GETSEG monitor call was issued from a locked lo	 
	to a high segment which is not a  dormant, active, or idle
	segment.	 	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 superseding  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.R	This	 7 message indicates that a  LOOKUP,  ENTER,  or  RENAME
	error  occurred which was la	 @rger in number than the errors
	LINK knows about.R	This  message  can  neve	 Hr  occur  and is included only for
	completeness of the LOOKUP, ENTER, and RENAME er	 Qror codes.	This message is not expected to occur.  If it does, please
	not	 Yify   your  Software  Specialist  or  send  a  Software
	PerformanceReportN(SPR)Rto!bDEC.%(9qboI
]m]}e]`	D"]a]g^

Q	D" 
f
	p
	x

~



 


0	D" 
A
H
O
V
^
i
t
 	D" 
0
1.
16  , ; bI$	D"S" +lk +mv
Zf
Z	p
Z	x
Z
~
Z

Z	D"
Z 
Z

0 +m
ZA
ZH
ZO
ZV
Z^
Zi	D"
Zt
Z  +n
Z0
Z1.
Z16 +n +o, +o;	D" +pb%C"" Q,Q Q-v
6f
6	p
6	x
6
~
6
	D"
6
6 
6

0 Q-
6A
6H
6O
6V
6^	D"
6i
6t
6  Q.
60
61.
616 Q. Q/,	D Q/; Q0bz#"0S1,H"QLk"QMv
i@f
i@	p
i@	x	D"
i@
~
i@

i@
i@ 
i@

0"QM
i@A
i@H
i@O	D"
i@V
i@^
i@i
i@t
i@ "QN
i@0
i@1.
i@16	D""QN"QO,"QO;"QPb0}3"=I8!"#

RR+

(
dd(<	

+#ST	U"~I@"ZZUl)\eo"buWC7eTBEMO6R\B:/DhD2gkD@g
qx8 ((d