Trailing-Edge - PDP-10 Archives - AP-D483B-SB_1978 - lnkerr.exe
There are 28 other files named lnkerr.exe in the archive. Click here to see a list.
?p`@?xY:\\YKb)L|uBL`@-e@g#	t{#A)8A{BE@Z-91
&.|+,~	%LNKLNS	Low seg data base not same size*~,~  ,,  [ 1DYR5b", ",R , " + 7B +,,  ,R !$bD bD 4F ", , " l" 7B +#`h+"`b+ ([/",>Q(} "-,  2B%4"&6 x+',*H,6 x:7@ +,,  ,+(,^x+!`)"w,>!`,1,,^iB+  & ")B5B6=f3 ")B."`d ",=f5,~,3,> ,=,,^+D	b,c&"  " $,J&( ",(, "  &"2"+	b	&.  $,J, &"j0 ,J, &"t $4"0b+*, "+0"+W!${P`2B`*dO5$U ",R`, ",,~." ,> "/+^1"+\/",>
e?",,^,}"+1"0+/",> ",,^+K>7K>gC3 E`iYmPMGHKN
TXz"/6@,"/4Bp>&"Z, ",$04D! ", +`B?+~ 0+}4B~ 1U$*D| 1bB+~&" 7!(+,[+,> ", ",,^,~,> "-,,^4"2, ".+ 4D! ")B.",+,>[,,,^Z73 &5"  ", &#`QDx6@,[x."0b."+Q"A`aB,~,>x4B,+ "+ "+ "+ "+ "aB?,~6@~+~
",~,+[1D7@ ,~+",+(  ,-+(-Jan-Feb-Mar-Apr-May-Jun-Jul-Aug-Sep-Oct-Nov-Decmn@0$$B
?X,+,>4"E[."~L&":X(D&$:XG&&&Z(H(B.$"2."n `D+>&$27@aDg &/"V$":5FA1(+D>!$z3(\+D."*dB/[.*xd"%b),^,~ b	b "5B[	b		d,c,>&$:0d~+X&&.[ *0& * .$&$0F *.(} $$6.^$m4dW&$2/0F1.0hO@,^ $)w'bQ,~-<KZjy'6L\X*
xQ*x,>,>,>,r>~,^,^,^,^:x,~-j(,>,>,>*~,> ~,~,^,^,^,^*x,~+ z Q2B+} *" 
X Fd@@)B/"(H.(5D~ &"q4B1"q+/"q+.0$q/$q!1H+4F+ZFA"`B@G_^	2"2b+/.Z+!7 +	Z,>,G,7x,>.",G,,^7B+7@+++% d" Q2D+,>+OS;
pG24gIN KuK?4kJ:G4Cg7Sl
veVYe,e4Y|]$W_MBQNd	HSN$K&$YC7DDS!S2

]8a3{QRd	oKc1S6
LMiR4[JtMJ,aSR4gNtgO$!g&4e[)4GUn user  has  loaded  ALGOL  procedures  without  a  main
	program.   Execution will be terminated because of missing
	start address and undefined symbols.	LINK expected a particular user address to be  in  memory,
	but it is not there.>	More than one successor link  satisfies  a  call  from  an
	ancestor link. At run time, the link in memory, or the one
	with the longest path in memory, will be used  to  satisfy
	the call.   No message will be given.  However, if none of
	the successor links are in  memory,  the  overlay  handler
	picks one with the longest path in memory.  If  all  paths
	are equal, the overlay handler picks  one  at  random  and
	gives  a  warning  message  to  the  user.  To avoid  this
	situation the user should promote, to a common  link,  the
	module containing the called subroutine.	LINK's space allocator was called with a request for zero
	words.	Either the compiler produced incorrect code  or  the  file
	was modified so that the code is no longer valid.  the REL
	file may contain tables longer than 2^18 words  or  tables
	known to contain word pairs but that actually have an  odd
	length.  Although this message is not fatal, it is usually
	followed by a fatal one.	All attempts to  obtain  more  memory,  including  writing
	files onto disk,  have failed.  The program is too big for
	available user memory, probably because of too many global
	symbols.  A future version of LINK  will  overflow  global
	symbols to the disk.  However,  there  will  always  be  a
	minimum size below which LINK will not operate.	This message occurs when the user changes  the  device  on
	which  the  log  file  is  being written.  The log file is
	closed on the first device and the remainder of  the  file
	is written on the second device.	The COBOL-produced file must be the first file loaded when
	loading   COBOL  modules.   COBDDT,  the  COBOL  debugging
	program, or any other modules, such as  a  MACRO  routine,
	cannot  be the first file in the command string.  The user
	should begin  loading  again  and  place  the  COBOL  main
	program  or  routine  as  the  first  file  in the command
	string.	The user attempted a feature that is not yet implemented.	Notification  that  LINK  has   started   generating   the
	requested save file.	The monitor call for obtaining SYS:UDDT.EXE failed.	A device switch, such as /REWIND or /BACKSPACE,  has  been
	given,  but  there  is no device to be associated with it.
	The switch is ignored.  This occurs when the user does not
	give  a  device  name  in the specification containing the
	switch or has not specified a device name in  the  current
	line.   (Remember  that  devices are cleared at the end of
	the line.) LINK's default device DSK  does  not  apply  to
	device  switches nor does a device specified in a /DEFAULT
	switch apply.  The user should respecify the command  line
	and include the appropriate device name with the switch.	The user is  reducing  the  size  of  an  already  defined
	relocation  counter via the /SET switch.  The new value is
	accepted.  The user should be extremely  careful  when  he
	does  this  because  code  previously loaded under the old
	relocation counter may be overwritten.  This  practice  of
	reducing  counters  is  dangerous  unless  the  user knows
	exactly where modules are loaded.	The user has a DATA statement in FORTRAN which sets  up  a
	COMMON area, but the COMMON area is in another link closer
	to the root.  The user should set up the  COMMON  area  in
	the link in which it is first defined.	The  user  has  a  data  store  to  an  absolutely-defined
	location that is not in the specified link (e.g., the user
	is storing data in  JOBDAT).  The  user  should  move  the
	module to the root link.		On an internal check of the counter for undefined symbols,
	LINK determined that the counter was negative.r	A read error has occurred on the input device.  Use of the
	device is terminated and the file is released.	Notification that the named link has been loaded. LINK has
	finished loading all modules and searching  all  libraries
	needed to generate the named link.------r	An error has been detected while reading the named file.r	An error has been detected while writing the name file.	LINK could not create the overlay file on  the  disk.  The
	user could be over quota, or the disk  could  be  full  or
	have errors.	Notification that the LINK module LNKMAP has completed the
	writing of the map file.  The map is now closed.	The code to handle symbols longer than six characters  has
	not  been  completed.   This  code  will be available in a
	future release.	LINK needs more memory and is expanding to  the  specified
	amount.   In  future  loads of the same programs, the user
	can run LINK more efficiently by requesting this amount of
	memory at the beginning of the load with the /CORE switch.	LINK is entering the  completion  stages  of  the  loading
	process.   These  stages  include the creation of save and
	symbol files  and,  if  required,  the  execution  of  the
	contents of memory.	Incorrect code was generated by the  F40  compiler  for  a
	data statement in the form
	     DATA A(I),I=1,4/1,2,3,4/
	as opposed to a data statement in the form
	     DATA (A(I),I=1,4)/1,2,3,4/	LINK is now reading the low and/or high  segment  overflow
	files backwards in order to do all remaining code  fixups.
	This  process  may  cause  considerable   disk   overhead.
	Note  that the message occurs only if the  load   was  too
	large to fit entirely in memory.	The FORTRAN compiler generates different  output  for  the
	KA10 and the KI10 processors (e.g., double precision code)
	and the user cannot load this mixture. He should recompile
	the appropriate programs.	LINK has completed its task of loading the user's  program
	and  other  required programs.  Control is either returned
	to  the  monitor  or  given  to  the  user's  program  for
	execution.	Output from the F40 and FORTRAN compilers cannot  be  used
	together in  the same load.  The user should decide  which
	compiler he  wants  and  then  recompile  the  appropriate
	program with that compiler.	Output from the F40  compiler  cannot  be  used  with  the
	overlay  facility.   The user should recompile his program
	with the FORTRAN compiler.@@@)@7	LINK cannot  find  the  return  instructions  in  the  F40
	compiled subroutine.	The user  gave  a  /FORSE  switch  while  loading  FORTRAN
	compiled code.        While in the final stages of  processing  the  root  link,
        LINK discovered that the overlay handler's request for the
        FUNCT. subroutine had not  been  satisfied.  This  request
        is usually satisfied while searching the default libraries
        (e.g.  FORLIB), but for some reason  no  library  searched
        contained the  FUNCT.  entry  point.  If  this  error  was
        allowed to pass, the overlay  handler  would  call  itself
        recursively  at  runtime  in  an attempt to read in FUNCT.
        The user should determine why no  library  that  contained
        FUNCT.   was  searched,  then  re-try the load.  Note that
        this condition will occur unless  the  main  program  from
        some  language that supports overlays has been loaded into
        the root.	The user is trying  to  set  the  beginning  of  the  high
	segment below the end of the last page of the low segment.
	The user can either specify a /SET:.HIGH. switch or in the
	case of MACRO,  reassemble  the  module.  (Note  that  the
	setting of the beginning of the high segment below  400000
	will fail on all KI10 monitors previous to 5.07 and on all
	KA10 monitors.)	The user has more global  symbols  than  can  fit  in  the
	maximum  hash table (about 50P in size) LINK can generate.
	Possible action is to increase the maximum allowable  size
	of the hash table.				An attempt was made to expand the blank COMMON area.  Once
	a  COMMON  area  is  defined, the size cannot be expanded.
	The user should load the module  with  the  largest  blank
	COMMON  area  first  or  specify  the larger area with the
	/COMMON switch before loading either module.	There is not enough memory in  the  system  to  initialize
	LINK.	The data mode specified for a device is illegal,  such  as
	dump mode for the terminal.  The user should respecify the
	correct device.	The OPEN or INIT monitor call  failed  for  the  specified
	device. The device could be in use by another user.CCCCC	The input file either was generated by a  translator  that
	LINK does not recognize (e.g., a non-supported translator)
	or is not in proper binary format (e.g., is  an  ASCII  or
	saved file).	The  INCREMENTAL  keyword  for  the  /MAP  switch  is  not
	implemented.  The switch is ignored.	LINK attempted to do  I/O  (LOOKUP,  ENTER  monitor calls)
	for a channel that has not been set up.r	An error occurred when reading the overlay file.	An incorrect link item type 11 was seen.	An  already-defined  symbol  has  been  given   a   second
	"partial" definition. The user should examine the usage of
	the named symbol.	The LINK symbol table routine was called with a 0  as  the
	symbol name.	An incorrect link item type 11 was seen.	The current symbol pointer  does  not  point  to  a  valid
	symbol triplet.  This can occur if an extended symbol does
	not terminate  properly.	An internal error occurred in the switch tables  built  by
	the SCAN module.^_
	while loading the  specified  file,  LINK  encountered  an
	ascii text block.  LINK began processing the  commands  in
	this text block and adding them  to  the  current  command
	line.  A error in the command text within the  text  block
	prevented LINK from successfully combining the new command
	information with the current command line. The user should
	correct the program containing the  erroneous  ASCII  text
	block and then reload.	A number other than 1 through 20 was used in a  link  item
	type 12.	The range checking of LINK's internal  tables  and  arrays
	failed.    The   address   output  is  the  point  in  the
	appropriate LINK segment at which this occurred.	Indication that the LINK module  LNKLOD  has  started  its
	processing.	The index (link item  type  14)  on  a  MAKLIB  or  FUDGE2
	library file is not correct.  The file will be searched as
	if the index were absent.	LINK has begun its processing of the user's input.	An error occurred in the  named  link  item.   This  could
	result  from  incorrect  output  generated by a translator
	(e.g., no argument is seen on an END  block  when  one  is
	required).  The user should retranslate the module.	LINK is in the process of loading the named module.	The user has previously assigned  the  specified  name  to
	another  link.   This attempt is ignored.  The user should
	specify a different name if he wants one  associated  with
	the link.	The named link could not be found in memory.	The indicated link has not  yet  been  loaded.   This  can
	happen if the user specifies link numbers, instead of link
	names, as arguments to the /NODE  switch and then  forgets
	the  numbers.   The  /NODE  switch is ignored.  The use of
	link numbers as arguments is not recommended.	The user specified a name of a link on  the  /NODE  switch
	and LINK has not yet loaded a link  with  that  name.  The
	/NODE switch is ignored.	The user has specified the start of a new overlay link  by
	means of the /NODE  switch,  but  has  not  completed  the
	loading of the previous  overlay.  In  order  to  continue
	loading, LINKhas terminated  the  previous  overlay.  this
	action is the same as if the user  had  supplied  a  /LINK
	switch just prior to the /NODE switch.  Because  the  user
	did not supply the  /LINK  switch,  this  overlay  will be
	unnamed.	The user has given  an  existing  global  symbol  a  value
	different from its original one.  The second occurrence of
	the global symbol is in the named module.   The  currently
	defined value is used.  The user should change the name of
	the symbol or reassemble one of the files with the correct
	parameters.	Alphabetic and numeric sorting of the map file is not  yet
	implemented.   The  symbols  appear  in the order in which
	they were placed in the symbol table.	This message indicates that LINK is making inefficient use
	of memory. In future loads of the same programs, the  user
	should allocate more memory to LINK at  the  beginning  of
	the load.  Area is one of  the  following:  LC=user's  low
	segment code, HC=user's high segment code, LS=local symbol
	table,  FX=fixup area, GS=global  symbol  table,  BG=bound
	global symbols, and RT=relocation tables.	Indication that the LINK module LNKMAP has begun to  write
	a map file.	Overlay structures consisting of more than one region  are
	not yet supported.	The current value of MAXCOR  is  too  small  for  LINK  to
	operate.   In  future  loads of this program, the user can
	save LINK time by setting MAXCOR to this new expanded size
	at the beginning of the load.	The user attempted to set MAXCOR to a value so large  that
	the  low  segment  would  be greater than the start of the
	high segment. The value of n is usually 256P.	The user specified the /MAXCOR  switch  with  an  argument
	that is below the minimum size LINK requires  as  its  low
	segment.  The switch is  ignored.   The  minimum  size  is
	dependent  upon  the code already loaded.  The user should
	respecify the switch.	The user attempted to move LINK backwards from its current
	position on the path to a position beyond the  root  link.
	For example, if LINK is positioned after the  fourth  link
	in a  path, the  largest  negative  number  the  user  can
	specify as an argument to the /NODE switch is -3.	The user's program was too  large  to  load  into  memory.
	thus, LINK created a saved file  on disk and cleared  user
	memory. The user can perform a GET or RUN operation on the
	program to load it into  memory.  If  the  loaded  program
	image is still too big  the  user  must  either  employ  a
	bigger machine or obtain a larger core limit.	The user's program was too large to load into  memory  and
	LINK  created  a  saved  file  on  disk.  It automatically
	executes the program by  performing  a  RUN  monitor call.
	however, the saved file  remains on disk and the user must
	delete it, if he wishes.	The end block (type 5) has not been  seen  for  the  named
	module.   This  can happen if two name blocks (type 6) are
	seen without an intervening end block, or if  the  end  of
	the  file  was  seen  before the end block.  Although this
	message is not fatal, usually fatal errors follow.	The user has specified a device that does not exist in the
	system.   The  user can re-edit the input files to correct
	the device name or type control-C to abort the load.	The user issued a switch that is not implemented  in  this
	version of LINK.JJJJJJ^_
	A device other than a disk was specified  for  the overlay
	file. The user must specify a disk for this file.PPPP	The standard released version of LINK includes the  LNKF40
	module that loads F40 code.  However, the installation has
	removed it by loading a dummy version of LNKF40  and  thus
	LINK is unable to handle F40  compiler  output.  The  user
	should request his installation to load a version of  LINK
	with the real LNKF40 module.	The internal symbols in the overlay handler could  not  be
	referenced.   This  is  either an internal error or a user
	error if the user supplied his own overlay handler.r	An error has occurred while writing the overlay file.	Indication that the  LINK  module  LNKOV2  has  begun  its
	second phase of writing the overlay file.	The last address allocated  by  the  specified  module  is
	greater  than  512P. The user should modify the modules of
	his load list to reduce the  program  size  to  less  than
	512P.  This  error condition is usually caused by the user
	dimensioning arrays too large.	While processing the named file, LINK encountered  an  end
	of  file  before  the  word count of the current block was
	exhausted.______	The requested feature is not yet available.	The relocation counter table is a fixed length and  cannot
	be  expanded  in  the  current  version   of  LINK.   This
	restriction will be eliminated in a future release.	The user has given a global symbol as an  address  to  the
	/SET switch, and  the  symbol  is currently undefined. The
	user should load the module that defines the symbol.	LINK's internal tables have been deleted  and  memory  has
	been reclaimed. This occurs near the end of loading.	LINK is expanding the global symbol table  either  to  the
	next prime number as requested by the user (via /HASHSIZE)
	or to its next expansion of about 50%.  In future loads of
	this program,  the  user can save LINK time by setting the
	hash table to this new expanded size at the  beginning  of
	the load.	This is the response to the /REQUEST switch.	LINK's space allocator received some words  that  did  not
	fit into the area to which they were to be returned.	An internal LINK error.  LINK's hashing algorithm  failed.
	A symbol already exists in  the  location  in  which  LINK
	needs to place the new symbol.  The error may disappear if
	the user loads the files in a different order.	An internal LINK inconsistency.  LINK  cannot  locate  the
	TITLE  triplets  in order to  store  the  lengths  of  the
	control sections.  The  loading  process  continues.   Any
	maps requested by the user will not contain the lengths of
	the control sections.	The user has loaded SIMULA procedures or classes without a
	main program. Execution will be terminated  because  of  a
	missing start address and undefined symbols.	The user has defined a non-COMMON  symbol  with  the  same
	name  as  a  COMMON  symbol.  The user should decide which
	symbol  definition  he  wants.   If  he  uses  the  COMMON
	definition, the COMMON area should be loaded first.	LINK has completed the  scanning  and  processing  of  the
	current  command  line and is ready to accept the input on
	the next line.	The named subroutine is not in a  successor  on  the  same
	path  as  the  calling  link, but is in another path.  The
	user should reconstruct his overlay  structure  and  place
	the  subroutine on the correct path.  Otherwise, a call to
	an undefined subroutine will occur at run time.r	An error has occurred on  the  save  file.   The  file  is
	closed  at  the end of the last data that was successfully
	output.        The user has attempted to set the  current  value  of  the
        named relocation counter below its initial value by giving
	of a /SET switch. The attempt is ignored.	Alphabetic and numeric sorting of the symbol table is  not
	yet implemented.  The symbols appear in the order in which
	they were placed in the symbol table.	LINK is rearranging the symbol table, and if required,  is
	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  according  to
	the  user's  request  via  the /SYMSEG, /SYMBOL, or /DEBUG
	switch.	LINK item type 13 (LVAR) is neither  implemented  in  LINK
	nor supported by DEC.  The TWOSEG pseudo-op in  the  MACRO
	language should be used.	The /NOINITIAL switch was placed  in  the  command  string
	after  the  first file specification.  Because this switch
	was not first in the command string, LINK's initial symbol
	table was loaded.	An attempt was made to expand a COMMON area.  The  largest
	occurrence  of  the  COMMON  area  of a given name must be
	linked first.  Once defined, the size cannot  be  expanded
	although  new  COMMON  areas  of  different  names  can be
	defined.  The user  should  load  the  largest  occurrence
	first, or use the /COMMON switch.	When LINK produces the index for the map it has found more
	program names than actually exist.  The symbol table is in
	error.	The named symbol was referenced in a  .ASSIGN  pseudo  op,
	but  the  symbol  is  undefined.  The .ASSIGN pseudo op IS
	ignored.  The user should load the module that defines the
	named symbol.	Extraction of the symbols from a MACRO Universal  file  is
	not  yet  implemented.   This  code  may be available in a
	future release of LINK.	Bits 0-3 of the first word of the  link  item  contain  an
	unknown  symbol code.  Either the translator is generating
	incorrect code or the binary file is bad.  The user should
	recompile the file.	The user has given a global symbol as  the  start  address
	and  the  symbol  is currently undefined.  The user should
	load the module that defines the symbol.	A reference to the named subroutine has  occurred  in  the
	specified link, and LINK has not yet loaded the referenced
	subroutine.  If this subroutine is required for execution,
	the user should reload and include the required modules on
	the path on which they were referenced.	The user gave a switch without  specifying  the  necessary
	arguments. For example, he gave the  /REQUIRE  switch  but
	did not give any symbol names.  The user should  respecify
	the switch.	One of 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.

	3.  The RENAME monitor call following a LOOKUP monitor call
	    failed.	The file requested by the user was not  found.   The  user
	should respecify the correct filename.	The directory does not exist on the named file  structure,
	or the project-programmer number given was incorrect.	The user does not have the correct  privileges  to  access
	the named file.	The directory on the 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 monitor call following a
	LOOKUP monitor call.	The user specified an illegal sequence  of  monitor  calls
	(e.g., a RENAME without a preceding LOOKUP or ENTER, or  a
	LOOKUP after an ENTER).	One of the following conditions occurred:

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

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

	3.  A  software-detected  data  inconsistency  error   was
	    detected while reading the UFD RIB or file RIB.	The named file is not a saved file.	The system cannot supply enough memory to use  as  buffers
	or to read in a program.	The  device  indicated  by  the  user  is  currently   not
	available.	The device specified by the user  does  not  exist.	The  machine  does  not  have  a  two-register  relocation
	capability.	There is no room on the file structure for the named file,
	or  the  user's  quota  on  the  file  structure  would be
	exceeded if the file were placed on the structure.	The user cannot write on the specified device  because  it
	is write-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 time.	Because of the user's quota or the available space on  the
	device,  the total number of blocks requested could not be
	allocated and a partial allocation was given.	The block required by LINK is not available for allocation.	The user attempted to  supersede  an  existing  directory.	The user attempted to delete  a  directory  that  was  not
	empty.	The required sub-file directory in the specified path  was
	not found.	A LOOKUP and ENTER monitor call was performed  on  generic
	device DSK and the search list is empty.	An attempt was made to create a subfile  directory  nested
	deeper  than  the maximum level allowed.	No file structure in the job's search list  has  both  the
	no-create bit and the write-lock bit equal to zero and has
	the UFD or SFD specified by the default or explicit path.	A GETSEG monitor call was issued from a locked low segment
	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.	This message indicates that a  LOOKUP,  ENTER,  or  RENAME
	error  occurred which was larger in number than the errors
	LINK knows about.	This is an internal LINK error.	Incorrect code has been generated by the F40 compiler.	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 DEC.	LINK could not make the named file on the disk  (LC=user's
	low  segment code,  HC=user's high segment code,  LS=local
	symbol table).  The user could be over quota, or the  disk
	could be full or have errors.	An error  occurred  while  reading  in  the  named   area.	An error  occurred  while  writing  out  the  named  area.r	An error has occurred on the output file.  The output file
	is   closed   at  the  end  of  the  last  data  that  was
	successfully output.	the job is too large to fit into the  allowed  memory  and
	the named area is being moved to disk (LC=user low segment
	code, HC=user high segment code,  LS=local symbol  table).	The status is represented by the right half  of  the  file
	status  word.  Refer to DECsystem-10 Monitor Calls for the
	explanation of the file status bits.r	(LC=user's  low segment code, HC=user's high segment code,
	LS=local symbol table, and GS=global symbol table).Y:\\Y;(9 JZ 
**Y 5+
^~,++U E<BYZ,G,aj+""U: bUaJ,QZaj+!1b7W $V+ E1"+%"T0"+y$U ".0$+,7@F7`G7+,6 G+,,>,>+I,,G,"U2"E+AZ`G0"
O@F:+ $,
O@F+%4[	Please retype the incorrect parts of the file specification]
 "R6@G,&,>!*xZ	b4BI ([0BK8+IZ,+ *jD,^ "$T2bE1$	` BE@@G@@F 3B	` G,
aj+-"U:bUaJ,Q+Uaj+%"U: bUaJ,Q+Y x`j`+g  ^0d
,^(0dGBFZu`h6`1Zu,G,Z,G,V+",^+-ZQ0d,G, "
1H,~ "bU,~!#),G,+,G,+,G,+,G,+X
(Z,G,V+,G,+." N0D+ $((B{,>,G,,^,G,+/*XJ+"V3"D+56@F+7@G+5:x,L"V3"D+: G,
ZBF,@ (d BF E<B>Z,G,9
6 "F,G,9
6$U "-0$ "2$E "1B-+E
6+ , "+6 G,~,>+A G,
,C,"V $,J,"U $,J+,^,^,^,>X
00$$   ,,  ,R   `d4B]l("}, "  `d+ .+   ,,  ,R l("}, " +FEE ENTER error  FLE LOOKUP error FRE RENAME error GSE GETSEG error NED Non-existent device IFD INIT failure for device }|}|a|a|a|a| a|#}|'}|*}|-}|/}|1}|4}|7a|;a|>}|A
E}|H}|K}|Qa|Va|Xa|Za|]a|ba|ea|h}|lCNW Code not yet written at X,Y:[,[	Type CONTINUE for more information]$0 STATUS 
@ FOR  $%(B{+&:x+9LNK(2) directory full (0) Illegal file name (0) file was not found (1) no directory for project-programmer number (2) protection failure (3) file was being modified (4) rename file name already exists (5) illegal sequence of UUOs (6) bad UFD or bad RIB (7) not a SAV file (10) not enough core (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 ) Unknown cause  !6B,~ }|G,n 	d D!4D; $7 ,~(EA!5D,>! }|K,n $Q$PG+@+:Z$	d +4D !0F+[1&Q$3D+*4D
,+	, !Z@@ $+W,n 4d[Z$$ +W,n !`d+ [Z$$,
  !  D+,n  D([Pddm$jQ$hG+@  D(,~@@@@,~ 
 $ D ( D~ ( D (RD ( D7@(,~ D " B N $(  F4F.$*b!,~,n l$| !af+-X$+@,~ ! D $ DQ$	d$@@+X$+@,~+[x B! $7B,
 !\B ^x B:x7B( -7@!"Lu B \SBRB ( B " B7B( - B7B( .RB7B( /bO!$cD(+D (ahPaHX "(+FcD(7O "( 7@+P H
9$,D."7D+p Dd&pG  +@=dO $7@+T,>,W,n,^+M,W,n@@ $Q$~G !af.$,>+@,@,^ !Z`,~

,t4BZ4Dr@@!&tG+@ d&pG  +@=dl $7@+q,>,W,n,^+h,W,n!$rG+@,~,n!$pG+@,~,n6D,~6DD+zRDX$KU D,~S(D  DX$l$P+@+:X$h$. +@,~ Fd$X$+@X$l$
+@,~ Fl$+@,~:x,~,,~h$(R+@+S(D SZX*&l$p+@X$l$
,>+@+@@h$&+@+:,^SX&@@*&,~,>,t,^&l&|G,>+@+Q,^h&&X&(R6@hRHHZXH,>+@+$,^+,^Z0H,~,>,>*,,> !`d +T f,~,>! h,~ }|WINS I/O data block not set upIDM Illegal data mode for device P	6$0 H+p,^x,~6$6$/S,~ Z1DT`+CODV Overlay file must be created on a file structure4LR.,?D,? (\/(X3"+b.L(X.L(e:x,~0*+g6B(]6@(X+g/(T3"+g.L(T.L(\+^,~ ?./B5$6@B+ n".2d7+ nZ."2b7 73b+q	b1+r	d+x &$#V@0Z "7@S=u D\0J+g4La+\7@?+z@@?+g(D/$ 7ab 73d+ n	d+ n "7@S=  D\+ n }|#Z #]@@j*"n ", &
#]@!$/{X$(,3"+-/,>"$(S S Bj*d!$/|X$( X."0?D"?+.X/S."?D"?6@T Bj*d,^(B|^$(#!$/{X$(@6@S3D#a1.&*d&"6@."(B !$/{X$(@*D"7@S+3D#a+!.?@/"@.Hj+ n/W4B$.B?@,+h2"S+]3bW+$ X/SQS.j*"7Bj,~/S.BS.BX.Ba+$4J; "/7D\="./X/4$;(D|&$.(D.".D\1J.D?.D(X.D(aS(S.d(SP*%(X (X@@Q&X&*'(\+w1j+R"S,/4"R"S (6@S3D#a1.(*f@(B|&" 6@."(B"S7HS*fF Hj7@S+N.X/S2D#a..(?D(?7@T*fL Hj?@/"@*fH!&/{X&(*FR6BS Bj*fP+"!$| S Bj.X/S."?D"?1J.6@T Bj*dT,~/(B|&"6F."(B!${+.X/S77@ S*h^ah+a2" S+$,> X/SQ.Sl( j/SQ"dB #b!&gp,,^+* #b@@\*"`!$| 7BT*fk/"6@X B\*dj  "7@S=o D\!$|ZX4Bw."Q"."7FT*ds4Fw1f+w@@*"*dq "7@S=xZX."Q."ZO@K1f+w@@*"+w!${@.\/X*d."?D"?,~*d!${ j2BS;x*d,~DYLCHCASRTLSFXBGGS,> *,,^,~,> *+,> *+,> *+,> *+,> *+,> *7@V,9+,> *+,> *+5d }|#c2d(s+0!&(n!YaB+0 `F.(S!0d+![6@/(SXHXZ(s/& F(s1D+,,>,>Z[."/F,e,^,^[@@SX& .(0D*& ,~ (e/"4"4 B(e (a.*(a,~,>,> 
(e,\+,^,^+0,>,;,^,~ "(7@S=b; \/X0$@+O,>#f,e ,@ *,\,""@.B(X.B(e7@(5,~+,D++I+I+++J+++.B(5+K7 7,~.B7 (X."Q"@@ $?*",~ \ D(\ D(X"$@.d\.$ D(S@@ D(a "@ B(e0J,~:(a>(e,~,> *,e,^,~,> *+X,> *+X,> *+X,> *+X,> *+X,> *+X,> *+X,> *+X4Da2"(S2b(X,u1$@+q .&2F(X+q G&? *(XQ@@.&*&  D&?".F(aA$?4DaSD.D(s6@(n+v/(SZB(n,~ }|#f ((n+xQY  `F.(S!1d+}`f+w/(SXB ,~`H+ /(SXH/(S.(SXB ,~/(S!/(SXB .(SYH,~,c *+ ,c *+ ,c *+ ,c *+ ,c *+ ,c *+ ,c *+ ,c *+ ,c *+ 7@(s,~@@(s (n.(S ZD(nR`ZB(j7B(n+ ".(SZZD(nR` (j@1b+  Z 5F XB + 5H  XFZB(j+ XFXB + 7(jZ4H )  [.$ Z0D+ "R`  .D @@+ #!.(e3D(a1"@+ 4 G$? (a D(X F(aA"? B(e "(j1 Z0D+ 0R`Q.&@@*& 7B(j,~ ZD(j[,e+ 4,> *, G1:,^,~,> *+ 9,> *+ 9,> *+ 9,> *+ 9,> *+ 9,> *+ 9,> *+ 9,> *+ 97D(n,~Q+ KQZ4Da.(S0D+ I[+a,> *, G,^,~,> *+ N,> *+ N,> *+ N,> *+ N,> *+ N,> *+ N,> *+ N,> *+ N+"7DS+ bQ.$@@*%X \,>7@S= ` D\,^@@S@@X@@\@@a@@e@@n@@s,~ $6@S3"S= gZS@@Q.&*' BS;S7@S= l B\,~7@U+ q6@6+ u,"%+w7@z7@V+!6@7+ ~@@?,"	+w b/UD"?4B q.2,>/"Q2,!J,^2 bD"?/", f 2.Y/U B6+w,~.Z/V/"?3"+! D"?,>/"Q3,!A,^3 cD"?/", f+w7@T+! X Y/T/T6@57@6+!,!+w X/T3d+! +!# &3" &3,+#i0J1J+,#i+#i7@5+"B,!+w+! 7@7+a X.\/W.[/V."6@T."@3b7+aGN B7 & D#k@0,~7@5+"B,> 8+!$7@6+"E,> 8 `X/`S."(BD"?4B!-,>.`0/"Q`0,d#o,^.B`0.`S/", f,^+w,^,~Z2d: D:[(D|*[/&[/1.T/$Q@j,~,>#p }|#qZ2d: D:[(D|,[/&[/1.T/$Q@l,~,>#t }|#tZ2d< D<[(D|.[/&[/3.V/$Q@n,~,>#w }|#xZ2d; D;[(D|6[/&[/2.U/$Q@v,~,>#{ }|#{Z3d:+!W D:(D|*[(D|
[/&[/1.T/$Q@J,~,>#p }|#~Z3d:+!b D:(D|,[(D|
[/&[/1.T/$Q@L,~,>#t }|$Z3d<+!m D<(D|.[(D|[/&[/3.V/$Q@N+"r,>#w }|$Z3d;+!x D;(D|6[(D|[/&[/2.U/$Q@V,~,>#{ }|$$
$  B@@ $ D6d@0D+"   D	d`d+"!$Lu D $ D DX$K D!$K8 D!$~ D Z/V(D} D ",{,"#,>Z
LD*?4J" /* ,!A .V.* J3O@7 ,^4D"x, f+"x,>#w }|$,~6@+"7 
$  B@@ $ D6d@0D+".   D	d`d+"/!$Lu D $ D DX$H9 D!$K8 D!$~ D Y/U(D} D ",{,"@ b/UD"?4B$,>/",!J,^2 bD"?/", f Y/U.2 B6+"x,>#{ }|$,~6B+"E 
$,> 8+"I6@*6B,~ 
$",> 87B+ B`@@ $ D,d$%!$Lu D $ D DXd$& D!$K8 D!$~ D `)(D} D "`,{,d$' `X/`S B`5 $(D|(D1$@ $@/",>7@m?Z",d#o,^4B"a B`0.`SZ`SQ@@.$/"*$, f,"x,w1: `X/`S.`0 B`5,^,~,>#p }|$(,~,>#t }|$.,~7D,~  	fafEl:x,~7D,~  	fafEl:x,~7@.,~,>,>#Y,"z,^,^4Bad"?G"?+!A $,
 B,~@@.Z..VZ.$[..VZ3d73&3,~/$.&2$32f7+# . B.@@.+# ".[4Ba.VZ.$2d7+#Z4F$3Q.VR`/V!B..V[4B$4.VZ2$3+#
 /VQZXD..VZ`YFPBZ..VZQB[..VZ."XBZ.4Ba.VZXD.Z[ .V/3,# $,a+##&#)#+#######I#K#O,>!"GB,^/&+#Z.XF!& +#,[.QF!&@+#,.H!&`!(cH+#F7@W+#F,>,>,>,>,>,>,>,>   ,$8+#5+ ,^,^ (ar`+#=ar+#C.*7l(+#C`l+#=al+#9+#C `f `r X(`f@`r@P(3H(g!(GH,^,^,^,^,^,^Bf`f`,~!&BF,~ af@+#T H,~6&af+#TXH6@YH,~6&af+#T^:@QH_:@PH,~,>  D$5,^,~EXP Expanding low segment to CEF Core expansion failed- jMOV Moving low segment to expand area p4(+H]AZW Allocating zero words;RUC Returning unavailable core!!"MSS MAXCOR set too small, expanding to !.!7OLC Error outputting area LCOHC Error outputting area HCOLS Error outputting area LSOAS Error outputting area ASILC Error inputting area LCIHC Error inputting area HCILS Error inputting area LSIAS Error inputting area AS+PLS Area LS overflowing to DSKELS Error creating overflow file for area LS -
	PAS Area AS overflowing to DSK Y/U B6+"xEAS Error creating overflow file for area AS - PLC Area LC overflowing to DSKPHC Area HC overflowing to DSK"j"nKJ"f"hELC Error creating overflow file for area LC -
	EHC Error creating overflow file for area HC -
 ".+#SFU Symbol table fouled up7 A+$S4T$w,$K+$<.
@!?1N+$D4B$?=p$;7 q+%6,~Q
 (ab`:x:x,~7 A+$>[.W2T+$> ad+$@ `dad+$@ }|$x ar+$N }|$x[
Z2JFj @&*@4J$|1*@,~/*@+$Q,>q@@q,>,>,>,>"@S,>@ @(B/".B@,% /W4B$_ x &
$|` %@@ @.$&$$$,X?,>?XB?7Bp+$m,>.W   ar+$k `dad+% }|$xZ,$:,^Q C?*|$c,^Z,^.$&$$$,d,^,^,^,^,^q @$A&"2// BA+$8 &}|%@ESN Extended symbol not expected9
$CRGS Rehashing Global symbol table from  to d2+$kISN Illegal symbol name `B B."%
4B%6@@2"@3"@+% B@,~ }|%x}h~_X{h}_h~Xu_8zh{_HyX#|_H'w+~]x/|83~^x7{X;z_?~HC|_8G}	8K{	_XO~
HTL Symbol hash table too largeab+% Z,>[,%#,^+%(,> $,=d%!,^(b%$ $/$	&$4D ,=d%& +(b%) $/$	&$4D  ",=d%+ +,> ",,^, "+,> ",,^, "+ %5+OY:^8w,~