Google
 

Trailing-Edge - PDP-10 Archives - cuspmar86binsrc_2of2_bb-fp63a-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+	@(6;N$x	N+x	(0Y:\\Y+(z++0F`
&	6F F'.|+,~%LNKLNS	Low segment data base not same size
COPYRIGHT (c) DIGITAL EQUIPMENT CORPORATION 1973,1986. ALL RIGHTS RESERVED.
+ Z.0B\Y+ (n*" 
K 6d@@)B/"(H.(5D &"q4B(o1"q+"/"q+.0$q/$q!A1H++4F=+!Z6A"`B@G(o_^	2"2b+=/.Z+-!7 +%Z,>,*_,97x,>.",*g,9P x.",*d,6,^7B+=7@+/+-Q"A`,>x4B(p0B+<7 X+< ",9e ",9e+7+) 1d"Z.0D\Y+,>+-S;
>g.c]e@]RkV!1Nfn	K>.^Ck>LSJ
Y:fY:nY:v3G26VINK?6	#Y;>kN MKQg7*SnJINf#C&-gNv#af^SB~
rSZZK21][JgO&0K26@_23g>.okK6 9I3&AY&NOaFSK2vHM2.
MNv
K3KC&ya"
a2[Jv_"yS?6
[gRBGC.Y1]&:hEWG56sG5>G
~fC6n@eVn$a3<C7IK&6_tS2pg:9Y6ni[C&jG6SNvaV6G66M.
kJ SOXSO&o[OON.
Lg;SM&v
G7)SKoafo[66)[?6AG7FEGe3KaS]CWKS	:]"vEMRF
;YNnYg:fMq&![]UB}_S&K7ZS"Y]Nnef_?6{[Nv
G&G.QNf
^[6SCFHU]NnY:y]N~QRfC:nWKc	IG@S6
Kc	Z_FCK.`i_gKS6N
)SS(kN mS6n
.MflY&vXSNn?S6&[CeCJftS3
G;>Ue2K&nI;TIWV:[R3k; Y7Y@e&SgRfMo:!OQf
MY6vuYNGIJruO6!aeMGK)[SDkN&!mf!Fa
NIkge^CYOt_"v_6biR6,a=_Mi6fMJ.
SR
a&`a6!gJG>.mG>6?vmg;cx"%!m"""3"<"K"o##=#b$$$$H$[$i$t%%,%2%V%]%h%s&&-&E&N&s'"'E'h(((!""""3"<"K"o##=#b$$$$H$[$i$t%%,%2%V%]%h%s&&-&E&N&s'"'E'h(((!!m"""3"<"K"o##=#b$$$$H$[$i$t%%,%2%V%]%h%s&&-&E&N&s'"'E'h(((!""""3"<"K"o##=#b$$$$H$[$i$t%%,%2%V%]%h%s&&-&E&N&s'"'E'h(((!	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.	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.(Q	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.(Q	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.(Q	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.(Q	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.(Q	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.(Q	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.(Q	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.(Q	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.(Q	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.(Q	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.YX9",^,~)?)F)g)n****	*
*@*@***-*/*2*3*" JM 
+M**L 15+(q 4*(}+(q7 B+)	 5aB+)"*q0"+$*r3$50$+),*d,),*_,9+)	 "6 X,9e ".59e"*r2"51B7+)&Z`71B
+) 
M7b6+),8@@6:1+= $,0E @Q!B
@@@@	\")6 X\")
&+8,8@@6+8[	Please retype the incorrect parts of the file specification]
[ Please retype the incorrect parts of the file specification ]
 *1B,8 ")=6@7,9P&",>!*xZ	b4B)0 (~ZB[0BK8+)0Z,.+ *j)+,^ "$*qcB51$	` B5@@7@@6 Z1B,	` 7,8
26@+\"+N6 X\"+R
&	b+	[End of log file]
O@B"*r5B)C,^b*r1B "b*r,*4+){Z,*_,9P+){,^B B  ~^`jp+)P0d $[+,`h6`1[++f*s&*r`h0F
+)Pl*p,*4+){Z,*_,9P,*_,9e B4H)]X
 ~^(0d,)b7"A"GB6Z+,`h6`1Z++,*,9PZ,*,*t+){Z/0d,)bZ+,,*,9PZ".,*,*~+(~,>*",*,9e,^,*,9(*$,~,^B,*4+){Z,*,9P BZ ~  @@ ,*,9",*,9b+(~,^B,*45){Z,*,9P ",*,9e "+V,*,9PSB(BG+W+@Z,*,8
(~Z,*_,*t+){,*_,9e+){.,D,,*_,9+){Z1 DA/"XB1l*+){.AXB1$*s 
d*s+){ "+Y6@7,9P7@67`77+){6 6+*,* +){ 7,8,>,* ,^,8+){ "+Z6 X "+Z59P/{4"+[.8X
 (,*_,9"6"(+ab+){.*6"(`b?+){ (,*_,9"7B(+){,*_,9"+*'+@+){:1+){7@7+){7@6,9+){,*_,8W+){+){7"B+*8Z`$*r1D
1B+*8 $d*r"*r3"4+*C6@6++[7@7+*C " BB,*k"*r3"4+*H 7,8,>,*V,^,8\`7+*H"*r3"4++] " BB6@6+*HZ8,8ZB6,*V ( B6 "6,*g,9P 5aB+*N "6,*d,9P 5aB++^ ",*g,9e 5aB7+_ ",*d,9e.*6`B:x,~$*r "-0$ "2$5 "@@X1B-+*[
6+ ,9e 5aB,~O@X "+_59P6 7,~,>+A 7,8*x+A,^:x586@6,~6`7+*U,>+*a7@67@7+*U,>+A,^+*U,8^,9e,9e"*r $,8e,9e,9e"*r $,8e "+`59P8.$.$(   ,9",9b  ,9"R   `d4B*zl("},9" "  `d586 .+`586   ,9",9b  ,9"R l("},9" " 586,>@
`bp5+,>[
"`S
X
+(,+,~,+)B1B++1B++."4L+0" 0b-1.",9e++
++
++TER errorFLELOOKUP errorFRERENAME errorGSEGETSEG errorNEDNon-existent device OFDOPEN failure for device EIFError for input file CNWCode not yet written at ~+a~+cq~+eq~+hq~+mq~+oq~+r~+v~+y~+|~+~~,~,~,q~,
q~,~,B,~,~,~, q~,%q~,'q~,*q~,-q~,1q~,5q~,7~,;~,@~,E~,I~,N~,R~,V~,Y~,] V,_@ H ,`` ,b  @ V,_@ H ,c`p ,b  @ ,f`Y V,h@ ,h`Z@ H` (` P >+L >+Ih,~K[	Type CONTINUE for more information][ Type CONTINUE for more information ]Status 
@ for file 
			
	
*+-"-BB+*HO@B+*T@@B+*TLNK,i (2)directory$full(0)Illegalifilename(0)filewas[notfound$(1)noEdirectoryforproject-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@Z name  6B~,~ ~.[,,i 	d D4D.R $7 ,~(EA5D.,> ~.^,,i $Q$PG+@+.QZ$	d +4D- 0F+,{[1&Q$3D+-
 $ Dl ( Dk ( Dm (RDn ( Dm7@(,~ Du "t Bm .b $(  F4F..$*b-,~,,i l$| af+-)X$+@,~  D $ DQ$	d$@@5.X$+@,~5.[x B $7B~,0E \B~ ^x B:x -eSBRB ( B " B7B(  B7B( RB7B( b.b!$cD(+-= (ahPaHX "(+-DbD(+-C .c (ad7D(+-B	b$@aF7.c "(  Z~7@+.d H
9$ D."7D+-J+DR7D+-Q .c	b$@aF+-Q (ad7D!$Lu Z~ D+,l,,l[4D-^Z` d&pG  +@=d-X $7@+-],>,1,,i,^+-V,1,,i@@ $Q$~G af.$,>+@,.T,^ Z`~,~xz{

{
,-}4B.Z4D-{@@!&tG+@ d&pG  +@=d-u $7@+-z,>,1,,i,^+-q,1,,i!$rG+@,~,,i!$pG+@,~,,i6D,~6D+.RX$KU D,~S(D ~ DX$l$P+@+.QX$h$. +@,~ Fd$X$+@X$l$
+@,~ Fl$+@,~+.:x,~,.,~h$(R+@+.S(D ~SZX*&l$p+@X$l$
,>+@+.@@h$&+@+.:,^ SX&@@*&,~,>,-},^ &l&|G,>+@+.e,^h&&X&(.f6@h.f  HZXH,>+@+..,^+.,^Z0H,~,>,>* ,.+.g,^,^+.",>,> 
~Q* 
~Q,\J~[L,,l h"_hb_ab+.K,,s,-T ( B( B0  B(!"X"(	b$@@(
!"(X"0*"06"(7B(1"0.B0R`(!"~AB(@@(@@(!"(X"(	@B(*"(@	b'+"+.M!"LuB0@@0[ZL~,.7:,^,^,~,>~+",>dq~+,~ Q"D`d#+.h,>"@+,~,>d@+,~INSI/OdatablocknotsetupIDMIllegaldatamodefor"devicePu6$*H+-J,^x,~6$6$/.g,~+~Z1FT`+.W4L/m.,D, (?/(:3"+.p.L(:.L(I:x,~0*+.v6B(@6@(;+.v/(63"+.v.L(6.L(?+.m,09 -./B5$/6@
@,0<+02"5+/z3b:+/66@R+/> :/5Q5.N*",/?+/6,0+/67BN,~O@b/5.B5.B:.BD,~4J/V "/7D?="/D/:/4$/V(D{&$.(D."1J.D
.D?6@R+/R.D(:.D(DS(5.d(5P*%(: (:@@Q&X&*'(?+/.(5 D(N !&@,0,02@@(N+/1j+/m"S,09/4"/m"S (6@53D61.(*f/[(B{&" 6@."(B"S7H5*f/a HN7@5+/i.:/52D6..(D(7@6*f/f HO?@/"*f/b!&/{X&(*F/l6B5 BN*f/k+/3!${ 5 BN &.:/5."D"1J.7@6+/t BO.&*d/o,>,09/(B{,^&6F."(B!${+/..:/577@ 5*h/{ah+/~2" 5+/66@R+/>,> :/5Q4(6.5l( N/5l" BS,IS4(0,^3D6+6,/?+/6,>,>,> 
N/
5 
:/
5.,4L04*0"" :+0 " 5(
{(L{(N{ .Ql(,00.=l0,^,^,^+/?6@R,02!${ 7B6*f0/"7@:+02B?O@b B?*d0  "7@5=0 D?O@6@R+/!${Z:4B0)7@b+0)@@b."Q"."7F6*d0&4F0)1f+0)@@*"*d0" "7@5=0*Z:."Q."Z1f+/@@*"+/ H*f.p+033F6 ,~_.&@ F!X&	f2,07!&@,~ !~6!@!${@.?/:*d0:D",~*d0=!${ N2B5;x*d0=,~DYLCHCASRTLSFXTPBGGS,> *,0W,^,~,> *50F,> *50F,> *50F,> *50F,> *50F,> *7@8,0w50F,> *7@9,0y50F,> *50F,> *50F5d0X ~6%2d(X+0m!&(S!YaB+0m `F.(5!0d+0Z![6@/(5XHXZ(X/& F(X1D+0i,>,>Z[."/F,1(,^,^[@@SX& .(0D*& ,~ (I/"4"0q B(I (D.*(D,~,>,> 
/
(I,.k+/,^,^6@(},~+0m,>,0{,^,~,>,0{,^,~ "(7@5=b0{ ?/:0$+1,>6(,:/ , *,.k,/"".B(:.B(I7@(},~+.1++1	+1	+++1
++++.B(}+1
7,~.B7(:."Q"@@/$*",~.?/D(?.D(:"$.d?.$.D(5@@1D(D+"0B(I0J1J1,~:(D>(I,~,>2*,1(,^,~,>@*51,>,*51,>.*51,>.*51,>/*51,>+*51,>,*51,>,*51,> *514D.p2"(52b(:,181$+14 .&2F(:+14 G& *(:Q@@.&*&  D&".F(DA$4D.pSD.D(X6@(S+19/(5ZB(S,~ ~6( (SXHZ/(5 H(S,~,:, *51K,:, *51K,:, *51K,:, *51K,:, *51K,:, *51K,:, *51K,:, *51K,:, *51K,:, *51K7@(X,~@@(X (S.(5 ZD(SR`ZB(N7B(S+1Z.(5ZZD(SR` (N@1b+1W Z 5F1SXB +1O5H1YXFZB(N+1OXFXB +1O7(NZ4H1a  [.$ Z0D+1[R`  .D @@+1\!.(I3D(D1"+1m G$ (D D(: F(DA" B(I "(N1 Z0D+1hR`Q.&@@*& 7B(N,~ ZD(N[,1(+1m,> *,21:,^,~,> *51q,> *51q,> *51q,> *51q,> *51q,> *51q,> *51q,> *51q,> *51q7D(S,~Q+2QZ4D.p.(50D+2[+.o,> *,2,^,~,> *52,> *52,> *52,> *52,> *52,> *52,> *52,> *52,> *52507D5+2Q.$@@*%: ?,>7@5=2 D?,^@@5@@:@@?@@D@@I@@S@@X,~[4D6,Zb2d ,> $4$.p6@53"5=2&Z5 B5,^@@Q.&*' 5;57@5=2, B?,~7@7+216@+25,4n+21+/7@`7@8+2G6@+2?,4\+2G+/ F/7D$4D21.z,>/$ z,3?,^z FD"/",2" z.</7 B+/ =/8D$4D2G }D$,>/$ {,36,^{ GD"/",2"+/7@6+2U;/6/61B0D+2M,2Z+/;/6/66@~7@~+2P3d+2m+2p &3" &3,56,0J1J5.6,56,7@6+/ ;/60B+2Y,2Z+/7@~+5
g.*j.* Jg." 2"+34H3,^,^+3
 
A* 
.*  /* "
 d.. 2.+3., 3L0*`+3.* +3 */
 $(@ 
(L/
y.
6/,Q
@j1+3+.0/2ph Ph.3b+3
,^,^,^,^,~,>64 ~642d D (F|, //& /y.6/$Q@l,~,>67 ~682d D (F|. //& /{.8/$Q@n,~,>6; ~6;2d D (F|6 //& /z.7/$Q@v,~,>6> ~6?2d D (F|8 //& /|.9/$Q@x,~,>6B ~6B ~6E6J444"6J46J4.6J6J2d D,>,>,>,>(B|(D| (F}f63(5H3h 
(J/
y.
6l 
2, 
(Ll
?/
y.
6@@(Q`.***0`93| 
A* 
. /* "
 d.. 2.+3q., 3L0*`+3r.* +3l */
 .(/3hh+3u*  Hh
@ $(@ 
(L/
y.
6/,Q
@J1+4.3b+3^,^,^,^,^,~,>64 ~6K 3d+4 D(F|, (F|
6//&6/y.6/$Q@L,~,>67J~6N3d+4HD(F|.(F|//&/{.8/$Q@N55*,>6;H~6Q43d+46D(F|66(F|//&/z.7/$Q@V,~,>6>~6T43d+4'6D(F|84(F|6//&6/|.9/$Q@X,~,>6BB~6W6J3X446J4
`:/
`5/*@ ,f44 .`5.*+4v,>,> 8,4z+4x >/9@,3I D^:^ (Bd B| D,4$/.9 D>+4w,>,> 8,4z+4x 
`D/
`5D*@/$,f44`DD"/"O@`}J`x,2",51:,^,^,~5`:/`5D"4B.p,f4CZf4>B~@@$D$DXf49D!$K8D@@`:/`5(D}D6d-2Df7+5	[f4>Zf4>,.5,f4P+.o!$Lu D@@Zf4>,.,f4P+.o,> 8+5,> 8,f4C Zf4> B~@@!$Lu D $ D $ D Xf49 D!$K8 D@@ ``(D} DZf4>,.,f4P `:/`5 B`} $(D{(D1$ $/",>7@ "Z$@,f62,^4B5% B`x.`5/",2",51,/1: `:/`5.`x B`},^,~7@f,~,>,>7,>7,53,^,^,^4B.pdG$536 $,0E B,~@@fZf.8$7.$[f.8&73d3&{,~/$.&2${2f+5= f Bf@@f+5L "f[4B.p.8$7.$2d+5=Z4F7Q.8R`/8!Bf.8[4B7.8$72${+5E /8QZXDf.8Z`YFPBZf.8"7 B[f.8"7." BZf4B.p.8ZXDf$7&7 .8/{,5X $,1"+5Q5`5c5e5g5]5]5]5]666,>!"GB,^/&55XZ.XF!& +5i[.QF!&@+5i.H!&`+5i&7.f7!&`!(cH+67@:+6,>,>,>,>,>,>,>,> ,7
EXPExpanding low segment to MEFMemory expansion failed)hOMOVMoving low segment to expand area p ,>6/6+0Q(l(+0xPUFPAGE. UUO failed, error code was AZWAllocating zero words0{RUMReturning unavailable memory,>+2%2l2oMSS/MAXCOR: set too small, expanding to 33,$HhOLCError outputting area LCOHCError outputting area HCOLSError outputting area LSOASError outputting area ASOTPError outputting area TPCBOCannot build overlays outside section zero+ILCError inputting area LCIHCError inputting area HCILSError inputting area LSIASError inputting area ASITPError inputting area TPPLCArea LC overflowing to diskPHCArea HC overflowing to diskPLSArea LS overflowing to diskPASArea AS overflowing to diskPTPArea TP overflowing to diskELCError creating area LC overflow fileEHCError creating area HC overflow fileELSError creating area LS overflow fileEASError creating area AS overflow fileETPError creating area TP overflow filex &f+5C "f+5I<xSFUSymbol table fouled upMMFMemory manager error7 +744T7S,7(+7.
2,
/

!
1N+74B7=p77 f+8,~Q
 
 (ab`:x:x,~7 +7[.: atp+72T+7+7,>,>,>`dp+7U[.:Q$I *PQ*I[b7V+7&,^,^,^+7,^,^,^+7 `tp+7/[1B+7X@"`S`XF*b7-5N7/ P[
Z2JFj 
&*@4J7Y1*@,~/*@+72,>f@@f,>,>,>,>"
S,>
 
(B/".B
,7b {/:4B7@ x !B7Z` 7^@
 
.$&$$$,0UX
,>
XB
7Bp+7I,>.: ,7,^Q C
*|7D,^Z,^.$&$$$,1',^,^,^,^,^f 
$
&"2/{/B+7 "+7!@ P +7/9
7RGSRehashing global symbol table from  to ISNIllegal symbol name `
 
."7h4B7g6@2"3"
+7b B
,~ ~7ux}h~_X{h}_h~Xu_8zh{_HyX#|_H'w+~]x/|83~^x7{X;z_?~HC|_8G}	8K{	_XO~
8S}
_hWw([~_h_}
HTLSymbol hash table too largeab+7}Z,>[,7,^58,> $,9e=d7~,^(b8 $/$	&$4D9( ,9e=d8 59((b8 $/$	&$4D9(  ",9e=d8 59(,> ",9e,^,9) "59e,> ",9e,^,9( "59e & @)B.",9e=f8,~ 8+,Y:^8w 8+,Y:]X8,~*",~,:, 
7B(+8,9""/,9e](,9" ",9e7B(,~,9"R((B}l"`,9"7@(,~ "(586Z8  ,9",9b  [ 1DYR5b9h,9" ",9eR ,9" " 586 7B +8/,9",9b  ,9"R !$bD bD 4F85 ",9e ,9" " l" 7B +9i`h+8:`b59 ([/",>Q(} "-,9e  2B9l4"9l6 x+9m,9%*H8D6 x:7@ +8D,9c  ,9"+8@,^x+9!!`)"w,>!`,8I,9c,^iB59a  & ")B5B8N=f8K ")B."`d ",9e=f8M,~,9{."z3b9o+8T.$/9o,> ,8W,9b,^58^	b,:,&"  " $,8e&( ".9o,9P "  &"2"59)	b	&9u  $,8e,9b &"j0 ,8d,9b &"t $4"9)0b59)*,9e "59e0"+8q!${P8z2B8z*d8j5$8o ",9eR8z,9" ",9e,~." ,> "/+8y1"+8v/",>8 ",9e,^,9" "59e1"059e/",> ",9e,^59eK>7K>gC3 E`iYmPMGHKN
TXz9"9v6@,9("9v4B9>&"
 " ,9e " ,9eZ4B9 ",9eZ,9( ",9e$9w4D9h ",9e 59(`B?59 9w+94B9 9xU$*D9 9xbB+9&" 7!(+,9)[59e,> ",9e ",9e,^,~,> "-,9e,^4"9y,9% ".59e 4D9h ")B.",9e+9",>[,9(,9c,^Z79z &5"9,  ",9e &#`QDx6@,9,[x."0b."59e79z (5"94/&l(#&" QDx/&0B,945B9;4f9: "`h?"9{,9e=f99`h,9^[x."0b."59e79z (Q(592 &  ")B.",9e=f9@,~,>,>!$A`+9G,>,>!$B,9K#4B9I,9e+9G,^,^,~,>*#C&9L`fl"*#XD#*,^,~Q"A`aB,~,>x4B9,9e+9R B"@@# ""59P,9"59b,>,9_,^ &,9>59`,> 4d9],9e=9[,^,~ "59e "59e "59e "59e "59e "59e "59e "aB,~6@"5"
",~,9+8*[1D7@ ,~+8:,9"+8@  ,8E+8@L\-Jan-Feb-Mar-Apr-May-Jun-Jul-Aug-Sep-Oct-Nov-Decmn@0$$B
?X,9"+9!$,>4":2."n `D+:&$27@aDg &/"V$":5F:	1(+:
>!$z3(:%+:
."*d:
/:$.*xd"%:+),^,~ :+	b "5B:$	b		d,:,,>&$:0d~+: &&.:$ *0& * .$&$0F *.(} $$6.^$m4d:&$2/0F1.0hO@,^ $)w':+2d:,."Q,~-<KZjy'6L\X
&.*
xQ*x,:<>+::*
xQ*x,>,:<>+::*
xQ*x,>,>,:<>~+:9*
xQ*x,>,>,>,:<>~,^,^,^,^:x,~-j(,>,>,>*~,> ~,~,^,^,^,^*x,~