Google
 

Trailing-Edge - PDP-10 Archives - bb-d549g-sb - lnkmsg.man
There are 11 other files named lnkmsg.man in the archive. Click here to see a list.











                              APPENDIX B

                            LINK MESSAGES



This appendix lists all of LINK's messages.  (The  messages  from  the
Overlay Handler, which have the OVL prefix, are given in Chapter 5.)



B.1  LIST OF MESSAGES

The following pages list LINK's messages.  For each message, the  last
three  letters  of the 6-letter code, the level, the severity, and its
medium-length message are given in boldface.  Then, in lightface type,
comes the long message.

When a message is issued,  the  three  letters  are  suffixed  to  the
letters LNK, forming a 6-letter code of the form LNKxxx.

The level of a message determines whether it will  be  issued  to  the
terminal,  the  log  file,  or  both.  You can use the /ERRORLEVEL and
/LOGLEVEL switches to control message output.  For  some  messages  an
asterisk  (*) is given for the level or severity.  This means that the
value is variable, and depends on the conditions  that  generated  the
message.

The severity  of  a  message  determines  whether  the  load  will  be
terminated  when  the message is issued.  Table B-1 lists the severity
codes used in LINK, along with their meanings.  The  /SEVERITY  switch
provides a means for lowering the severity that is considered fatal.

The severity also determines the first character on the  message  line
printed  to  the  terminal.   This character can then be detected with
Batch's error facility.  For all informational messages, the character
is [.  Warnings use %, and fatal errors use ?.








                                 B-1
                            LINK MESSAGES


                              Table B-1
                            Severity codes


  Code                             Meaning


   1-7      Informational;   messages  of  this  severity  generally
            indicate LINK's progress through the load.

  8-15      Warning;  LINK is able to recover by itself and continue
            the load.

    16      Warning if timesharing, but fatal and stops the load  if
            batch.

    20      Fatal;  LINK can only partially recover and continue the
            load.   The  loaded program may be incorrect.  Undefined
            symbols cause this action.

    24      This is for file access errors.  Under  batch,  this  is
            fatal  and stops the load.  Under timesharing, this is a
            warning,  and  LINK  prompts  for   the   correct   file
            specification if possible.

    31      Always fatal;  LINK stops the load.



The /VERBOSITY switch determines whether the  medium-length  and  long
messages  are  issued.   If  you  use /VERBOS:SHORT, only the 6-letter
code,  the  level,  and  the  severity  are  issued.    If   you   use
/VERBOS:MEDIUM,  the medium-length message is also issued.  If you use
/VERBOS:LONG, the code, level, severity,  medium-length  message,  and
long message are issued.

Those portions of the medium-length messages enclosed in braces ({ and
}) are optional, and are only printed in appropriate circumstances.

Those portions  of  the  medium-length  messages  enclosed  in  square
brackets  are  filled  in  at  run-time  with  values pertinent to the
particular  error.   Table  B-2  describes  each  of  these  bracketed
quantities.











                                 B-2
                            LINK MESSAGES


                              Table B-2
                       Special Message Segments

  [area]       The name of one of LINK's internal memory  management
               areas.

  [date]       The date on which LINK was run.

  [decimal]    A decimal number, such as a node number.

  [device]     A device name.

  [file]       A file specification.

  [label]      An internal label in LINK.

  [memory]     A memory size, such as 17P.

  [name]       The name of the  loaded  program  or  a  node  in  an
               overlaid program.

  [octal]      An octal number, such as a symbol value.

  [reason]     The reason for a file  access  failure,  one  of  the
               messages from Table B-3.

  [switch]     The name of a switch associated with the error.

  [symbol]     The name of a symbol, such as a subroutine or  common
               block name.

  [type]       The type or attributes associated with a symbol.



Whenever possible, LINK attempts  to  indicate  the  module  and  file
associated  with  an  error.   This  information represents the module
currently being processed by LINK, and may not always  be  the  actual
module  containing  the  error.   For  instance,  if  LINK  detects  a
multiply-defined symbol, either value may be the  incorrect  one.   In
this  case, LINK reports only the second (and subsequent) redefinition
and the module containing it.












                                 B-3
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


ABT    31   31   Load aborted due to  %LNKTMA  errors,  max.  /ARSIZE:
                 needed was [decimal]

                 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.

AIC    31   31   Attempt to increase size of  {blank  common}  {common
                 [symbol]} from [decimal] to [decimal]
                 {Detected in module [symbol] from file [file]}

                 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.

AMP     8    8   ALGOL main program not loaded

                 You loaded ALGOL procedures,  but  no  main  program.
                 The  missing start address and undefined symbols will
                 terminate execution.

ANM    31   31   Address not in memory

                 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.

ARL     8    8   Ambiguous request in link [decimal] {name [name]} for
                 [symbol] defined in links [decimal], [decimal], ...

                 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



                                 B-4
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


                 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.

AZW    31   31   Allocating zero words

                 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.

B4R     8    8   Bad F40 produced REL file
                 {Detected in module [symbol] from file [file]}

                 Either the compiler produced incorrect  code  or  the
                 .REL  file  was  incorrectly  modified.  Two possible
                 causes for the error are:  a table is too long  (more
                 than  218 words);  or a table that should have paired
                 words has an odd length.  LNKB4R is usually  followed
                 by a fatal error.

CCD    31   31   CPU conflict
                 {Detected in module [symbol] from file [file]}

                 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.

CLF     1    1   Closing log file, continuing on file [file]

                 You have changed the log file specification.  The old
                 log  file is closed;  further log entries are written
                 in the new log file.








                                 B-5
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


CMC    31   31   Cannot mix COBOL-68 and COBOL-74 compiled code
                 {Detected in module [symbol] from file [file]}

                 You cannot use COBOL-68 and  COBOL-74  files  in  the
                 same  load.  Compile all COBOL programs with the same
                 compiler and reload.

CMF    31   31   COBOL module must be loaded first
                 {Detected in module [symbol] from file [file]}

                 You are loading a mixture of COBOL-compiled files and
                 other  files.   Load  one of the COBOL-compiled files
                 first.

CMX    31   31   Cannot  mix  Extended  FORTRAN  compiled  code   with
                 FORTRAN compiled code
                 {Detected in module [symbol] from file [file]}

                 You cannot load  modules  produced  by  FORTRAN  with
                 modules  produced  by  Extended FORTRAN.  Compile all
                 FORTRAN modules the same way, then reload.

CNW    31   31   Code not yet written at [label]

                 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.

CSF     1    1   Creating saved file

                 LINK is generating your executable (EXE) file.

DEB    31    1   [Name] execution

                 LINK is beginning  program  execution  at  the  named
                 debugger.

DLT    38    1   Execution deleted

                 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.








                                 B-6
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


DNS     8    8   Device not specified for switch [switch]

                 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).

DRC     8    8   Decreasing relocation counter [symbol]  from  [octal]
                 to [octal]
                 {Detected im module [symbol] from file [file]}

                 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.

DSC    31   31   Data store to common  [symbol]  not  in  link  number
                 [decimal]
                 {Detected in module [symbol] from file [file]}

                 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.

DSL    31    *   Data store to location [octal]  not  in  link  number
                 [decimal]
                 {Detected in module [symbol] from file [file]}

                 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.











                                 B-7
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


DSO    31   31   Data statement overflow
                 {Detected in module [symbol] from file [file]}

                 Incorrect  code  has  been  generated  by   the   F40
                 compiler.  This message is not expected to occur.  If
                 it does, please notify your  Software  Specialist  or
                 send a Software Performance Report (SPR) to DIGITAL.

DUZ    31   31   Decreasing undefined symbol count below zero

                 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.

EAS    31   31   Error creating area AS overflow file [reason] [file]

                 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.

ECE    31   31   Error creating EXE file [reason] [file]

                 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.

EGD     1    1   Emergency GETSEG done

                 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.

EHC    31   31   Error creating area HC overflow file [reason] [file]

                 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.

EIF    31   31   Error for input file Status [octal] for file [file]

                 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.





                                 B-8
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


ELC    31   31   Error creating area LC overflow file [reason] [file]

                 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.

ELF     1    1   End of log file

                 LINK has finished writing your log file.  The file is
                 closed.

ELN     7    1   End of link number [decimal] {name [name]}

                 The link is loaded.

ELS    31   31   Error creating area LS overflow file [reason] [file]

                 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.

EMS     1    1   End of MAP segment

                 The map file is completed and closed.

EOE    31   31   EXE file output error Status [octal] for file [file]

                 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.

EOI    31   31   Error on input Status [octal] for file [file]

                 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.

EOO    31   31   Error on output Status [octal] for file [file]

                 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.






                                 B-9
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


EOV    31   31   Error creating overlay file [reason] [file]

                 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.

ESN    31   31   Extended symbol not expected

                 Long symbol names (more than six characters) are  not
                 implemented.   This message is not expected to occur.
                 If it does, please notify your Software Specialist or
                 send a Software Performance Report (SPR) to DIGITAL.

EXP     3    1   Expanding low segment to [memory]

                 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.

EXS     1    1   EXIT segment

                 LINK is in the last stages of  loading  your  program
                 (for   example,   creating   EXE  and  symbol  files,
                 preparing for execution if requested).

FCD    31   31   F40 confused about data statements
                 {Detected in module [symbol] from file [file]}

                 You are loading incorrect F40-compiled code caused by
                 a source statement of the form

                 DATA A(I),I=1,4/1,2,3,4/

                 instead of the form

                 DATA (A(I),I=1,4)/1,2,3,4/

                 This message is not expected to occur.  If  it  does,
                 please  notify  your  Software  Specialist  or send a
                 Software Performance Report (SPR) to DIGITAL.

FCF     1    1   Final code fixups

                 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.




                                 B-10
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


FEE     *    *   ENTER error [reason] [file]

                 See Table B-3 for the list of possible long messages.

FIN     1    1   LINK finished

                 LINK is finished.  Control is passed to the  monitor,
                 or to the loaded program for execution.

FLE     *    *   LOOKUP error [reason] [file]

                 See Table B-3 for the list of possible long messages.

FOV    31   31   Cannot overlay F40 compiled code
                 {Detected in module [symbol] from file [file]}

                 You cannot  load  F40-compiled  code  in  an  overlay
                 structure.  Recompile with the FORTRAN compiler.

FRE     *    *   RENAME error [reason] [file]

                 See Table B-3 for the list of possible long messages.

FSF     8    8   FORTRAN subroutine not in  expected  format,  /MIXFOR
                 fixup not done
                 {Detected in module [symbol] from file [file]}

                 LINK cannot find  a  return  from  this  F40-compiled
                 subroutine.   This  message is not expected to occur.
                 If it does, please notify your Software Specialist or
                 send a Software Performance Report (SPR) to DIGITAL.

FSI     8    8   FORTRAN requires FOROTS, /FORSE switch ignored

                 You   gave   the   /FORSE   switch   while    loading
                 FORTRAN-compiled  code.   LINK ignored the switch and
                 will use the FORTRAN run-time system.

FSN    31   31   FUNCT. subroutine not loaded

                 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.




                                 B-11
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


GSE     *    *   GETSEG error [reason] [file]

                 See Table B-3 for the list of possible long messages.

HCL    31   31   High segment code not allowed in an overlay link
                 {Detected in module [symbol] from file [file]}

                 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.

HSL    31   31   Attempt to set high segment origin too low
                 {Detected in module [symbol] from file [file]}

                 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.

HTL    31   31   Symbol hash table too large

                 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.

I4D    31   31   Illegal F40 data code [octal]
                 {Detected in module [symbol] from file [file]}

                 Incorrect  code  has  been  generated  by   the   F40
                 compiler.  This message is not expected to occur.  If
                 it does, please notify your  Software  Specialist  or
                 send a Software Performance Report (SPR) to DIGITAL.

I4S    31   31   Illegal F40 sub-block [octal]
                 {Detected in module [symbol] from file [file]}

                 Incorrect  code  has  been  generated  by   the   F40
                 compiler.  This message is not expected to occur.  If
                 it does, please notify your  Software  Specialist  or
                 send a Software Performance Report (SPR) to DIGITAL.







                                 B-12
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


I4T    31   31   Illegal F40 table entry [octal]
                 {Detected in module [symbol] from file [file]}

                 Incorrect  code  has  been  generated  by   the   F40
                 compiler.  This message is not expected to occur.  If
                 it does, please notify your  Software  Specialist  or
                 send a Software Performance Report (SPR) to DIGITAL.

IAS    31   31   Error inputting  area  AS  Status  [octal]  for  file
                 [file]

                 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.

ICB     8    8   Invalid chain REL block (type 12) link number [octal]
                 {Detected in module [symbol] from file [file]}

                 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.

IDM    31   31   Illegal data mode for device [device]

                 You specified an illegal combination  of  device  and
                 data  mode  (for  example,  terminal  and dump mode).
                 Respecify a legal device.

IHC    31   31   Error inputting  area  HC  Status  [octal]  for  file
                 [file]

                 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.

ILC    31   31   Error inputting  area  LC  Status  [octal]  for  file
                 [file]

                 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.





                                 B-13
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


ILS    31   31   Error inputting  area  LS  Status  [octal]  for  file
                 [file]

                 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.

IMA     8    8   Incremental maps not yet available

                 The INCREMENTAL keyword for the /MAP:  switch is  not
                 implemented.  The switch is ignored.

IMI    31   31   Insufficient memory to initialize LINK

                 LINK needs more memory than is available.

IMM     *    1   [Decimal] included modules missing {from file [file]}

                 You have requested with the  /INCLUDE:   switch  that
                 the  named modules (if any) be loaded.  Specify files
                 containing these modules.

INS    31   31   I/O data block not set up

                 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.

IOV    31   31   Input error for overlay file Status [octal] for  file
                 [file]

                 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.

IPO    31   31   Invalid polish operator [octal]
                 {Detected in module [symbol] from file [file]}

                 You are attempting  to  load  a  file  containing  an
                 invalid  REL block type 11 (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.




                                 B-14
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


IPX    31   31   Invalid psect index {for psect [symbol]}
                 {Detected in module [symbol] from file [file]}

                 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.

IRB    31   31   Illegal REL block type [octal]
                 {Detected in module [symbol] from file [file]}

                 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.

IRC    31   31   Illegal relocation counter
                 {Detected in module [symbol] from file [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.

IRR     8    8   Illegal request/require block
                 {Detected in module [symbol] from file [file]}

                 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.

ISD     8    8   Inconsistent symbol definition for symbol [symbol]
                 {Detected in module [symbol] from file [file]}

                 The named symbol either has a partial definition  and
                 an   explicit   definition,   or   has   two  partial
                 definitions.  Later resolution of partial definitions
                 may result in a multiply-defined global symbol.

                 A partial definition is one  in  which  a  symbol  is
                 defined in terms of other undefined symbols.  If your
                 code has A=:B  +3 and A=:7, then either B   will have
                 to be 4 or A will be multiply-defined.







                                 B-15
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


ISN    31   31   Illegal symbol name [symbol]
                 {Detected in module [symbol] from file [file]}

                 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.

ISO    31   31   Invalid polish store operator [octal]
                 {Detected in module [symbol] from file [file]}

                 You are attempting  to  load  a  file  containing  an
                 invalid  REL  block type 11 (polish).  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.

ISP    31   31   Incorrect symbol pointer

                 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.

ISS     8    8   Insufficient  space  for  symbol  table  after  psect
                 [symbol] -- table truncated

                 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.

IST    31   31   Inconsistency in switch 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.








                                 B-16
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


ITB    31   31   Invalid text in ASCII block from file [file]

                 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.

IUU     *   31   Illegal user UUO at PC [octal]

                 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.

IVC    31   31   Index validation check failed at address [octal]

                 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.

LDS     1    1   LOAD segment

                 The LINK module LNKLOD is beginning its processing.

LFB     1    1   LINK log file begun on [date]

                 LINK is  creating  your  log  file  as  a  result  of
                 defining the logical name LOG:.

LFC     1    1   Log file continuation

                 LINK is continuing your log file as a result  of  the
                 /LOG switch.

LFI     1    1   Log file initialization

                 LINK is beginning your log file as a  result  of  the
                 /LOG switch.








                                 B-17
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


LII     8    1   Library index inconsistent, continuing

                 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.

LIN     1    1   LINK initialization

                 LINK is beginning its processing by initializing  its
                 internal tables and variables.

LMN     6    1   Loading module [symbol]

                 LINK is loading the named module.

LNA     8    8   Link name [name]  already  assigned  to  link  number
                 [decimal]

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

LNL     8    8   Link number [decimal] not loaded

                 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.

LNM    31   31   Link number [decimal] not in memory

                 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.

LNN     8    8   Link name [name] not assigned

                 The name you gave with the /NODE switch  is  not  the
                 name of any loaded link.  The switch is ignored.

LNS    31    8   Low segment data base not same size

                 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.




                                 B-18
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


LSM     8    8   /LINK  switch  missing  while  loading  link   number
                 [decimal] -- assumed

                 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).

LSS    31    1   {No} Library search symbols (entry points)
                 {[symbol]        [octal]
                   . . .           . . . }

                 The listed symbols and  their  values  (if  any)  are
                 those that are library search entry points.

MDS     8    8   Multiply-defined global symbol [symbol]
                 {Detected  in  module  [symbol]  from  file   [file]}
                 Defined value = [octal], this value = [octal]

                 The named module contains  a  new  definition  of  an
                 already defined global symbol.  The old definition is
                 used.  Make the definitions consistent and reload.

MEF    31   31   Memory expansion failed

                 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.

MOV     1    1   Moving low segment to expand area [area]

                 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.

MPS     1    1   MAP segment

                 The LINK module LNKMAP is writing a map file.








                                 B-19
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


MRN     1    1   Multiple regions not yet implemented

                 The REGION keyword for the /OVERLAY:  switch  is  not
                 implemented.  The argument is ignored.

MSN     8    8   Map sorting not yet implemented

                 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.

MSR    31   31   /MIXFOR switch required to mix F40 and FORTRAN code
                 {Detected in module [symbol] from file [file]}

                 You must use the /MIXFOR switch to load a mixture  of
                 modules  compiled  by  F40  and FORTRAN.  The /MIXFOR
                 switch must precede any file specifications.

MSS     8    8   /MAXCOR: set too small, expanding to [memory]

                 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.

MTB     8    8   /MAXCOR: too big, [memory] used

                 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.

MTS     8    8   /MAXCOR: too small, at least [memory] is required

                 LINK needs more space than you gave with the /MAXCOR:
                 switch.   Give  a  new /MAXCOR:  switch with at least
                 the required size.

NBR    31   31   Attempt to position to node before the root

                 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.)

NEB     8    8   No end block seen
                 {Detected in module [symbol] from file [file]}

                 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



                                 B-20
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


                 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.

NED    31   24   Non-existent device [device]

                 You gave a device that does not exist on this system.
                 Correct your input files and reload.

NPS     8    8   Non-existent  psect  [symbol]  specified  for  symbol
                 table

                 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.

NSA    31    1   No start address

                 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.

OAS    31   31   Error outputting area  AS  Status  [octal]  for  file
                 [file]

                 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.

OEL     8    8   Output  error  on  log  file,   file   closed,   load
                 continuing {Status [octal] for file [file]}

                 An error has occurred on the output file.  The output
                 file   is   closed  at  the  end  of  the  last  data
                 successfully output.  The status  is  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.

OEM     8    8   Output  error  on  map  file,   file   closed,   load
                 continuing Status [octal] for file [file]

                 An error has occurred on the output file.  The output
                 file   is   closed  at  the  end  of  the  last  data
                 successfully output.  The status  is  represented  by



                                 B-21
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


                 the right half of the file status word.  Refer to the
                 DECsystem-10 Monitor Calls for the explanation of the
                 file status bits.

OES     8    8   Output  error  on  symbol  file,  file  closed,  load
                 continuing Status [octal] for file [file]

                 An error has occurred on the output file.  The output
                 file   is   closed  at  the  end  of  the  last  data
                 successfully output.  The status  is  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.

OEX     8    8   Output  error  on  XPN  file,   file   closed,   load
                 continuing Status [octal] for file [file]

                 An error has occurred on the output file.  The output
                 file   is   closed  at  the  end  of  the  last  data
                 successfully output.  The status  is  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.

OFD    31   31   OPEN failure for device [device]

                 An OPEN or INIT monitor call for the specified device
                 failed.   The  device  may  be  under  another user's
                 control.

OFN    31   31   Old FORTRAN (F40) module not available
                 {Detected in module [symbol] from file [file]}

                 LINK  handles  F40-compiled  code  with  its   LNKF40
                 module.   Your  installation  has substituted a dummy
                 version of LNKF40.  You can either recompile with the
                 FORTRAN  compiler,  or  request  your installation to
                 reload LINK with the real LNKF40 module.

OFS    31   31   Overlay file must be created on a file structure

                 Specify a disk device for the overlay file.

OHC    31   31   Error outputting area  HC  Status  [octal]  for  file
                 [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



                                 B-22
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


                 bits.

OHN    31   31   Overlay handler not loaded

                 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.

OLC    31   31   Error outputting area  LC  Status  [octal]  for  file
                 [file]

                 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.

OLS    31   31   Error outputting area  LS  Status  [octal]  for  file
                 [file]

                 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.

OMB    31   31   /OVERLAY switch must be first

                 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.)

ONS     8    1   Overlays not supported in this version of LINK

                 LINK handles overlays  with  its  LNKOV1  and  LNKOV2
                 modules.   Your  installation  has  substituted dummy
                 versions of these.   You  should  request  that  your
                 installation  rebuild  LINK  with the real LNKOV1 and
                 LNKOV2 modules.








                                 B-23
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


OOV    31   31   Output error for overlay file Status [octal] for file
                 [file]

                 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.

OS2     1    1   Overlay segment phase 2

                 LINK's module LNKOV2 is writing your overlay file.

OSL     8    8   Overlaid program symbols must be in low segment

                 You have  specified  /SYMSEG:HIGH  or  /SYMSEG:PSECT:
                 when   loading   an   overlay   structure.    Specify
                 /SYMSEG:LOW or /SYMSEG:DEFAULT.

PAS     1    1   Area AS overflowing to disk

                 The load is too large to fit into the allowed  memory
                 and the ALGOL symbol table is being moved to disk.

PBI     8    8   Program break [octal] invalid
                 {Detected in module [symbol] from file [file]}

                 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.

PCL     8    8   Program too complex to load, saving as file [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 has saved your program as an EXE  file  on  disk



                                 B-24
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


                 and  cleared  your user memory.  You can use a GET or
                 RUN command to load the EXE file.

PCX     8    1   Program too complex to load  and  execute,  will  run
                 from file [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.

PEF    31    8   Premature end of file from file [file]

                 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.

PHC     1    1   Area HC overflowing to disk

                 The load is too large to fit into the allowed  memory
                 and your high-segment code is being moved to disk.

PLC     1    1   Area LC overflowing to disk

                 The load is too large to fit into the allowed  memory
                 and your low-segment code is being moved to disk.

PLS     1    1   Area LS overflowing to disk

                 The load is too large to fit into the allowed  memory
                 and your local symbol tables are being moved to disk.






                                 B-25
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


POT     1    1   Plotting overlay tree

                 LINK is creating your overlay tree file.

POV     8    8   Psects [symbol] and  [symbol]  overlap  from  address
                 [octal] to [octal]

                 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.

PTL    31   31   Program too long
                 {Detected in module [symbol] from file [file]}

                 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.

PUF    31   31   PAGE. UUO failed, error code was [octal]

                 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.

RBS    31   31   REL block type [octal] too short
                 {Detected in module [symbol] from file [file]}

                 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.

RED     1    1   Reducing low segment to [memory]

                 LINK is reclaiming memory by  deleting  its  internal
                 tables.






                                 B-26
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


RER     *    1   {No} Request external  references  (inter-link  entry
                 points)
                 {[symbol]        [octal]
                   . . .           . . .}

                 The  listed  symbols  and  their  values   (if   any)
                 represent  subroutine  entry  points  in  the current
                 link.

RGS     1    1   Rehashing  global  symbol  table  from  [decimal]  to
                 [decimal]

                 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.

RLC    31    1   Reloc ctr.       initial value   current value
                 {[symbol]        [octal]         [octal]
                   . . .           . . .           . . .}

                 The listed symbols and values represent  the  current
                 placement of psects in your address space.

RME    31    *   REMAP error{, high segment origin may be incorrect}

                 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.

RUM    31   31   Returning unavailable memory

                 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.

SFU     8    8   Symbol table fouled up

                 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.




                                 B-27
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


SIF    31   31   Symbol insert failure, non-zero hole found

                 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.

SMP     8    8   SIMULA main program not loaded

                 You loaded some SIMULA procedures or classes, but  no
                 main  program.   Missing  start address and undefined
                 symbols will terminate execution.

SNC    31   31   Symbol [symbol] already defined, but not as common
                 {Detected in module [symbol] from file [file]}

                 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.

SNL     1    1   Scanning new command line

                 LINK is ready to process the next command line.

SNP     8    8   Subroutine [symbol] in link number [decimal]  not  on
                 path  for  call  from  link  number  [decimal]  {name
                 [name]}

                 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.

SNS    31   31   SITGO not supported
                 {Detected in module [symbol] from file [file]}

                 LINK does not support the .REL file  format  produced
                 by  the  SITGO  compiler.  Load your program by using
                 SITGO.

SOE    31   31   Saved file  output  error  Status  [octal]  for  file
                 [file]

                 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.



                                 B-28
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


SRB     8    8   Attempt to  set  relocation  counter  [symbol]  below
                 initial value of [octal]
                 {Detected in module [symbol] from file [file]}

                 You cannot use the /SET:  switch  to  set  the  named
                 relocation  counter  below  its  initial  value.  The
                 attempt is ignored.

SRP    31   31   /SET: switch required for psect [symbol]
                 {Detected in module [symbol] from file [file]}

                 Relocatable psects are  not  implemented;   you  must
                 specify   an   explicit   absolute  origin  with  the
                 /SET:PSECT:  switch for the named psect.

SSN     8    8   Symbol table sorting not yet implemented

                 Alphabetical or numerical sorting of the symbol table
                 is  not implemented.  The symbols appear in the order
                 they are found.

SST     1    1   Sorting 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,  /SYFILE,  or
                 /DEBUG switch.

STC     1    1   Symbol table completed

                 The symbol table has been sorted and moved  according
                 to the /SYMSEG, /SYFILE, or /DEBUG switch.

T13    31   31   LVAR REL block (type 13) not implemented
                 {Detected in module [symbol] from file [file]}

                 REL block type 13 (LVAR) is obsolete.  Use the  MACRO
                 pseudo-op TWOSEG.

TDS     8    8   Too late to delete initial symbols

                 LINK has already loaded the initial symbol table.  To
                 prevent  this  loading,  place  the /NOINITIAL switch
                 before the first file specification.









                                 B-29
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


TMA    31    8   Too many ambiguous requests in link  [decimal]  {name
                 [name]}, use /ARSIZE:[decimal]
                 {Detected in module [symbol] from file [file]}

                 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.

TTF     8    8   Too many titles found

                 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.

UAR     8    8   Undefined assign for [symbol]
                 {Detected in module [symbol] from file [file]}

                 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.

UGS     *    1   {No} Undefined global symbols
                 {[symbol]        [octal]
                   . . .           . . .}

                 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.

UNS    31   31   Universal file REL block  (type  777)  not  supported
                 from file [file]

                 Extraction of symbols from a MACRO universal file  is
                 not implemented.





                                 B-30
                            LINK MESSAGES
Code   Lev  Sev                         Message                       


URC    31    1   Unknown radix-50 symbol code [octal] [symbol]
                 {Detected in module [symbol] from file [file]}

                 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.

USA     8    8   Undefined start address [symbol]

                 You gave an undefined  global  symbol  as  the  start
                 address.  Load a module that defines the symbol.

USC    31    8   Undefined subroutine [symbol] called from link number
                 [decimal] {name [name]}

                 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.

USI     8   16   Undefined symbol [symbol] illegal in switch [switch]

                 You have specified an undefined symbol  to  a  switch
                 that  can  only  take  a  defined symbol or a number.
                 Specify the correct switch value.

UUA     8    8   Undefined /UPTO: address [symbol]

                 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.

VAL    31    1   Symbol [symbol] [octal] [type]

                 LINK has printed the specified symbol, its value  and
                 its attributes as requested.

XCT    31    1   [Name] execution

                 LINK is beginning execution of your program.

ZSV     8    8   Zero switch value illegal

                 You omitted required  arguments  for  a  switch  (for
                 example,  /REQUIRE  with  no symbols).  Respecify the
                 switch.




                                 B-31
                            LINK MESSAGES


B.2  INDEXED MESSAGES

Table B-3 lists the indexed messages issued  with  the  LINK  messages
LNKFEE, LNKFLE, LNKFRE, and LNKGSE.  The medium-length messages in the
table are substituted for the [reason] field in the main messages.

The level and severity of these messages depend on the particular file
access  error.   Thus,  each  indexed  message  includes the level and
severity actually assigned to the main message.

The number in the index column and in parentheses in the medium-length
is  the octal error code returned by the LOOKUP, RENAME, ENTER, RUN or
GETSEG UUOs.  See the Monitor Calls manual for a complete  description
of these codes.








































                                 B-32
                            LINK MESSAGES
Idx    Lev  Sev                         Message                       


  0    31   31   (0) Illegal file name

                 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.

  0    31   24   (0) file was not found

                 The named file was not found.   Specify  an  existing
                 file.

  1    31   24   (1) no directory for project-programmer number

                 The named directory does not exist on the named  file
                 structure, or the project-programmer number given was
                 incorrect.

  2    31   24   (2) protection failure

                 You do not have sufficient access privileges  to  use
                 the named file.

  2    31   31   (2) directory full

                 The directory on the DECtape  has  no  room  for  the
                 file.   Delete some files from the DECtape or specify
                 another device.

  3    31   24   (3) file was being modified

                 Another job is currently modifying  the  named  file.
                 Try accessing the file later.

  4    31   24   (4) rename file name already exists

                 The named file already exists, or  a  different  file
                 was  specified  on the ENTER monitor call following a
                 LOOKUP monitor call.









                                 B-33
                            LINK MESSAGES
Idx    Lev  Sev                         Message                       


  5    31   31   (5) illegal sequence of UUOs

                 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.

  6    31   31   (6) bad UFD or bad RIB

                 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.

  7    31   31   (7) not a saved file

                 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.

 10    31   31   (10) not enough memory

                 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.









                                 B-34
                            LINK MESSAGES
Idx    Lev  Sev                         Message                       


 11    31   31   (11) device not available

                 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.

 12    31   31   (12) no such device

                 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.

 13    31   31   (13) not two reloc reg.  capability

                 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.

 14    31   24   (14) no room or quota exceeded

                 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.

 15    31   24   (15) write lock error

                 The  named  device  is   write-locked.    Specify   a
                 write-enabled   device   or   ask   the  operator  to
                 write-enable the named device.

 16    31   31   (16) not enough monitor table space

                 There is not enough internal monitor table space  for
                 the named file.  Try the load at a later time.








                                 B-35
                            LINK MESSAGES
Idx    Lev  Sev                         Message                       


 17     1    1   (17) partial allocation only

                 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.

 20    31   31   (20) block not free on allocation

                 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.

 21    31   31   (21) can't supersede (enter) an existing directory

                 You have attempted to supercede the named directory.

 22    31   31   (22) can't delete (rename) a non-empty directory

                 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.

 23    31   24   (23) SFD not found

                 One of the sub-file directories in the named path was
                 not found.

 24    31   24   (24) search list empty

                 A LOOKUP or  ENTER  monitor  call  was  performed  on
                 generic device DSK:  and the search list is empty.

 25    31   24   (25) SFD nested too deeply

                 You have attempted to  create  a  sub-file  directory
                 nested deeper than the maximum level allowed.









                                 B-36
                            LINK MESSAGES
Idx    Lev  Sev                         Message                       


 26    31   24   (26) no-create on for specified SFD path

                 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.

 27    31   24   (27) segment not on swap space

                 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.

 30    31   24   (30) can't update file

                 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).

 31    31   24   (31) low segment overlaps high segment

                 The end of the low segment is above the beginning  of
                 the high segment.

 32    31   31   (32) RUN not allowed when not logged in

                 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.

 33    31   31   (33) file still has outstanding ENQ/DEQ locks

                 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.



                                 B-37
                            LINK MESSAGES
Idx    Lev  Sev                         Message                       


 34    31   31   (34) bad EXE file directory format

                 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.

 35    31   31   (35) EXE format files must have .EXE extension

                 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.

 36    31   31   (36) EXE file directory is too big

                 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.

 37    31   31   (37) network capability exceeded for TSK:

                 The  monitor's  ability  to  accept  another  network
                 connection has been exceeded.

 40    31   31   (40) task is not available

                 The named task is not available.  Specify an existing
                 task name.

 41    31   31   (41) undefined network node for TSK:

                 You have specified  a  network  node  that  does  not
                 exist.   Wait  for  the node to come up or specify an
                 existing network node.

 42    31   31   ([decimal]) Unknown cause

                 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



                                 B-38
                            LINK MESSAGES
Idx    Lev  Sev                         Message                       


                 notify your Software Specialist or  send  a  Software
                 Performance Report (SPR) to DIGITAL.



















































                                 B-39