HP 3000 Manuals HP 3000 Manuals
Language Subsystem Errors (3000-3999)
Language subsystem errors usually indicate errors in an input relocatable
object file. The relocatable object file may have been corrupted after
compilation, or there may be a compiler error. Save the corrupt version
of the file in case you need it when reporting the error. Recreate the
file and retry the command. If the error recurs, document the steps that
produced it and contact your System Manager.
------------------------------------------------------------------
3001
MESSAGE ILLEGAL SYMBOL INDEX IN FIXUP RECORD
CAUSE A "fixup request" record in a relocatable object
file indicates a reference to a symbol, but the
symbol index is outside the range of indices for
the symbol table in that relocatable object file.
(This problem can arise if a source file compiles
with errors and the compiler does not purge the
resulting relocatable object file.) This message
is followed by another line that indicates the
relocatable object file and subspace offset which
require the fixup.
ACTION This is a compiler error. Record the steps that
produced this error and report the problem to your
System Manager.
------------------------------------------------------------------
3002
MESSAGE !: SYMBOL ! HAS INVALID STRING INDEX
CAUSE An entry in the symbol table of the named
relocatable object file contains an invalid pointer
to the symbol name.
ACTION This is a compiler error. Record the steps that
produced this error and report the problem to your
System Manager.
------------------------------------------------------------------
3003
MESSAGE NO $BSS$ SUBSPACE DEFINED
CAUSE HP Link Editor/XL allocates space for all
uninitialized common blocks in a subspace named
$BSS$. This subspace must be defined in one of the
input files, and is normally defined in
NRT0.LIB.SYS.
ACTION Check that the NRT0.LIB.SYS file is present on your
system and that it has not been overwritten with
some other file. Also ensure that you do not have
a file equate for NRT0.LIB.SYS. If the problem
persists, document the steps that produced this
error and report the problem to your System
Manager.
------------------------------------------------------------------
3004
MESSAGE CAN'T FIND SUBSPACE FOR !
CAUSE HP Link Editor/XL automatically defines three
symbols for programs: etext, edata and end. These
symbols are placed at the end of the code,
initialized data, and uninitialized data subspaces,
respectively. The $DATA$ and $BSS$ subspaces must
be defined in one of the input files, and are
normally defined in NRT0.LIB.SYS.
ACTION Check that the NRT0.LIB.SYS file is present on your
system and that it has not been overwritten with
some other file. Also ensure that you do not have
a file equate for NRT0.LIB.SYS. If the problem
persists, document the steps that produced this
error and report the problem to your System
Manager.
------------------------------------------------------------------
3005
MESSAGE NO $UNWIND_END$ SUBSPACE DEFINED
CAUSE HP Link Editor/XL generates descriptors for all
long branch, import and export stubs that it
creates. These descriptors are required for
unwinding the stack during a stack trace or a
non-local escape operation. The $UNWIND_END$
subspace must be defined in one of the input files,
and is normally defined in NRT0.LIB.SYS.
ACTION Check that the NRT0.LIB.SYS file is present on your
system and that it has not been overwritten with
some other file. Also ensure that you do not have
a file equate for NRT0.LIB.SYS. If the problem
persists, document the steps that produced this
error and report the problem to your System
Manager.
------------------------------------------------------------------
3006
MESSAGE FIRST INIT POINTER IS NOT CODE
CAUSE In order to generate an executable file that the
loader can accept, the subspace records for the
"code" space must precede those for the "data"
space. Normally, the declarations contained in the
NRT0.LIB.SYS file ensure that this happens.
ACTION Check that the NRT0.LIB.SYS file is present on your
system and that it has not been overwritten with
some other file. Also ensure that you do not have
a file equate for NRT0.LIB.SYS. If the problem
persists, document the steps that produced this
error and report the problem to your System
Manager.
------------------------------------------------------------------
3008
MESSAGE TOO MANY LOADABLE SPACES
CAUSE The loader rejects an executable file that contains
more than two loadable spaces (a $TEXT$ space for
code and a $PRIVATE$ space for data). If a program
attempts to declare any other loadable space, HP
Link Editor/XL issues this error message.
ACTION This is a compiler error. Record the steps that
produced this error and report it to your System
Manager.
------------------------------------------------------------------
3009
MESSAGE LOADABLE SPACE MISMATCH
CAUSE HP Link Editor/XL has found two relocatable files
that declare the same space as both a loadable and
an unloadable space.
ACTION This is a compiler error. Record the steps that
produced this error and report it to your System
Manager.
------------------------------------------------------------------
3010
MESSAGE PRIVATE SPACE MISMATCH
CAUSE HP Link Editor/XL found more that one relocatable
module that declares the same space as both private
and non-private.
ACTION This is a compiler error. Record the steps that
produced this error and report it to your System
Manager.
------------------------------------------------------------------
3012
MESSAGE ILLEGAL ARGUMENT COMBINATION (!,!)
CAUSE A parameter relocation stub cannot be built to
transfer the arguments.
ACTION This is a compiler error. Record the steps that
produced this error and report the problem to your
System Manager.
------------------------------------------------------------------
3013
MESSAGE SUBSPACE LENGTH NOT EQUAL INIT LENGTH
CAUSE A relocatable object module contains a subspace
with a non-zero initialization length but a larger
subspace length.
ACTION This is a compiler error. Record the steps that
produced this error and report the problem to your
System Manager.
------------------------------------------------------------------
3014
MESSAGE !: UNSUPPORTED SYMBOL TYPE (!) FOR UNSAT SYMBOL
CAUSE A relocatable object module contains an unsatisfied
symbol with an illegal symbol type. The valid
symbol types for unsatisfied symbols are: CODE,
DATA, MILLICODE, STORAGE, ABSOLUTE, MILLI_EXT, and
NULL.
ACTION This is a compiler error. Record the steps that
produced this error and report the problem to your
System Manager.
------------------------------------------------------------------
3015
MESSAGE !: UNSUPPORTED SYMBOL TYPE (!) FOR UNIVERSAL SYMBOL
CAUSE A relocatable object module contains a universal
symbol with an illegal symbol type. The valid
symbol types for universal symbols are: CODE,
DATA, PRI_PROG, SEC_PROG, ENTRY, MILLICODE,
ABSOLUTE, MILLI_EXT, MODULE, and NULL.
ACTION This is a compiler error. Record the steps that
produced this error and report the problem to your
System Manager.
------------------------------------------------------------------
3016
MESSAGE FIXUP HAS INVALID EXPRESSION SELECTOR
CAUSE A relocatable object module contains a corrupt
"fixup request" record. The one or two lines that
follow this message gives the file and subspace
that require the fixup, and the symbol which is
referenced by that location.
ACTION This is a compiler error. Record the steps that
produced this error and report the problem to your
System Manager.
------------------------------------------------------------------
3017
MESSAGE FIXUP HAS INVALID FIELD SELECTOR
CAUSE A relocatable object module contains a corrupt
"fixup request" record. The one or two lines that
follow this message gives the file and subspace
that require the fixup, and the symbol which is
referenced by that location.
ACTION This is a compiler error. Record the steps that
produced this error and report the problem to your
System Manager.
------------------------------------------------------------------
3018
MESSAGE FIXUP HAS INVALID FORMAT SELECTOR
CAUSE A relocatable object module contains a corrupt
"fixup request" record. The one or two lines that
follow this message gives the file and subspace
that require the fixup, and the symbol which is
referenced by that location.
ACTION This is a compiler error. Record the steps that
produced this error and report the problem to your
System Manager.
------------------------------------------------------------------
3019
MESSAGE DATA ADDRESS IS OUT OF RANGE FOR SHORT LOAD OR
STORE
CAUSE A load or store instruction is attempting to reach
a memory location that is not reachable through a
single instruction. (Normally, compilers always
generate a two-instruction sequence for loading or
storing data, unless the location is guaranteed to
be within the range of a single instruction.) The
two lines that follow this message give the file
and subspace offset of the load or store
instruction, and the symbol which is being
referenced.
ACTION This is a compiler error. Record the steps that
produced this error and report it to your System
Manager.
------------------------------------------------------------------
3020
MESSAGE TARGET OF CONDITIONAL BRANCH IS OUT OF RANGE
CAUSE A conditional branch instruction is attempting to
reach a memory location that is not reachable
through a single instruction. Normally, HP Link
Editor/XL replaces single-instruction branches with
a chained branch when necessary. The two lines
that follow this message give the file and subspace
offset of the branch instruction, and the symbol
which is being referenced.
ACTION This is a compiler error. Record the steps that
produced this error and report it to your System
Manager.
------------------------------------------------------------------
3021
MESSAGE TARGET OF UNCONDITIONAL BRANCH IS OUT OF RANGE
CAUSE An unconditional branch instruction is attempting
to reach a memory location that is not reachable
through a single instruction. Normally, HP Link
Editor/XL replaces single-instruction branches with
a chained branch when necessary. The two lines
that follow this message give the file and subspace
offset of the branch instruction, and the symbol
which is being referenced.
ACTION This is a compiler error. Record the steps that
produced this error and report it to your System
Manager.
------------------------------------------------------------------
3022
MESSAGE TARGET OF ABSOLUTE BRANCH IS OUT OF RANGE
CAUSE An absolute branch instruction is attempting to
reach a memory location that is not reachable
through a single instruction. Normally, HP Link
Editor/XL replaces single-instruction branches with
a chained branch when necessary. The two lines
that follow this message give the file and subspace
offset of the branch instruction, and the symbol
which is being referenced.
ACTION This is a compiler error. Record the steps that
produced this error and report it to your System
Manager.
------------------------------------------------------------------
3024
MESSAGE FIXUP REFERS TO INVALID SYMBOL
CAUSE A "fixup request" record indicates that a reference
is being made to a symbol whose symbol type is not
valid for the fixup.
ACTION This is typically a compiler error. Document the
steps that produced this error and report the
problem to your System Manager.
------------------------------------------------------------------
3027
MESSAGE INVALID FIXUPS EXIST
CAUSE When HP Link Editor/XL encounters one or more
problems with a "fixup request" record, it prints
this summary message at the end of the link
operation.
ACTION Refer to the "action" description for the
previously listed error messages. Once you have
resolved those problems, this message goes away.
------------------------------------------------------------------
3028
MESSAGE !: NOT A VALID LIBRARY (INVALID MAGIC NUMBER)
CAUSE The named file has the correct filecode but
contains an incorrect "magic number" in its library
header record. This usually indicates that the
relocatable library file has been corrupted, or
that a non-library file has been created with an
NMRL filecode.
ACTION Verify that you have specified a relocatable
library file, that it is the correct one and that
its name is spelled correctly. It the file and
filecode are correct, replace or rebuild the file.
------------------------------------------------------------------
3029
MESSAGE !: CORRUPT LIBRARY FILE (INCORRECT HEADER CHECKSUM)
CAUSE The named file has the correct filecode but
contains an incorrect "checksum" in its library
header record. This usually indicates that the
relocatable library file has been corrupted, or
that a non-library file has been created with an
NMRL filecode.
ACTION Verify that you have specified a relocatable
library file, that it is the correct one and that
its name is spelled correctly. It the file and
filecode are correct, replace or rebuild the file.
------------------------------------------------------------------
3030
MESSAGE !: MISSING LIBRARY SYMBOL TABLE
CAUSE The named relocatable library file has no symbol
table. This usually indicates that the relocatable
library file has been corrupted, or that a
non-library file has been created with an NMRL
filecode.
ACTION Verify that you have specified a relocatable
library file, that it is the correct one and that
its name is spelled correctly. It the file and
filecode are correct, replace or rebuild the file.
------------------------------------------------------------------
3031
MESSAGE !: NOT A VALID OBJECT FILE (INVALID MAGIC NUMBER)
CAUSE The named file has the correct filecode but
contains an incorrect "magic number" in its header
record. This usually indicates that the
relocatable object file has been corrupted, or that
a non-relocatable object file has been created with
an NMOBJ filecode.
ACTION Verify that you have specified a relocatable object
file, that it is the correct one and that its name
is spelled correctly. It the file and filecode are
correct, recreate the file.
------------------------------------------------------------------
3032
MESSAGE !: NOT A VALID OBJECT FILE (INVALID VERSION ID)
CAUSE The named file has the correct filecode but
contains an incorrect "version id" in its header
record. This usually indicates that the
relocatable object file has been corrupted, or that
a non-relocatable object file has been created with
an NMOBJ filecode.
ACTION Verify that you have specified a relocatable object
file, that it is the correct one and that its name
is spelled correctly. It the file and filecode are
correct, recreate the file.
------------------------------------------------------------------
3033
MESSAGE !: CORRUPT OBJECT FILE (INCORRECT HEADER CHECKSUM)
CAUSE The named file has the correct filecode but
contains an incorrect "checksum" in its header
record. This usually indicates that the
relocatable object file has been corrupted, or that
a non-relocatable object file has been created with
an NMOBJ filecode.
ACTION Verify that you have specified a relocatable object
file, that it is the correct one and that its name
is spelled correctly. It the file and filecode are
correct, recreate the file.
------------------------------------------------------------------
3034
MESSAGE !: NOT A VALID OBJECT FILE (INVALID SYSTEM ID)
CAUSE The named file has the correct filecode but
contains an incorrect "system id" in its header
record. This usually indicates that the
relocatable object file has been corrupted, or that
a non-relocatable object file has been created with
an NMOBJ filecode.
ACTION Verify that you have specified a relocatable object
file, that it is the correct one and that its name
is spelled correctly. It the file and filecode are
correct, recreate the file.
------------------------------------------------------------------
3035
MESSAGE MISSING SYMBOL EXTENSION RECORD: ! (!)
CAUSE A relocatable object file has requested HP Link
Editor/XL to perform type checking, but it does not
contain the required symbol extension records that
provide the type checking information.
ACTION This message indicates a compiler error. Record
the steps that produced the error and report the
problem to your System Manager.
------------------------------------------------------------------
3036
MESSAGE FIXUP HAS A SELECTOR MISMATCH
CAUSE An invalid fixup request was found in a relocatable
object file during the fixup translation in the
linker.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3037
MESSAGE FIXUP IS NOT A PROCEDURE CALL
CAUSE A fixup request record in a relocatable object file
is invalid.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3038
MESSAGE BAD UNWIND DESCRIPTOR
CAUSE A corrupt unwind descriptor was found in a
relocatable object file.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3039
MESSAGE BAD RECOVER DESCRIPTOR
CAUSE A corrupt recover descriptor was found in a
relocatable object file.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3040
MESSAGE UNUSED FIXUP
CAUSE A fixup request was encountered that was left
unused. This typically means that an invalid fixup
request exists in the relocatable object file.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3041
MESSAGE ILLEGAL COMBINATION OF RELOCATABLE SYMBOLS
CAUSE A fixup request record in a relocatable object file
is invalid.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3042
MESSAGE EXPRESSION STACK UNDERFLOW
CAUSE A fixup request record in a relocatable object file
is invalid.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3043
MESSAGE INVALID FIXUP: "!"
CAUSE A fixup request record in a relocatable object file
is invalid.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3044
MESSAGE INVALID FRAME SIZE: "!"
CAUSE A fixup request record in a relocatable object file
is invalid.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3045
MESSAGE FIXUP APPLIED TO INSTRUCTION: "!"
CAUSE A fixup request record in a relocatable object file
is invalid.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3046
MESSAGE INVALID LOADER FIXUP NEEDED
CAUSE The linker has determined that a loader fixup needs
to be generated, but the target of the loader fixup
is invalid. It is illegal to have initialized code
pointers point into data. Make sure that the code
does not contain code pointers which are
initialized to point into data (it is possible to
make this error when writing in assembly).
ACTION If the code does not contain initialized code
pointers which point into data, or the program
consists of only high-level source language (eg.
Pascal, COBOL, etc.), then this is a compiler
error. Record the steps that produced the error
and report the problem to your System Manager.
------------------------------------------------------------------
3047
MESSAGE INVALID ALIGNMENT OF DATA
CAUSE The alignment specified in a fixup request record
in a relocatable object file is invalid.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3048
MESSAGE DIVISION BY 0 IN AN EXPRESSION
CAUSE A fixup request in a relocatable file contains a
DIV expression that has an invalid (0) divisor.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3049
MESSAGE TRY-RECOVER STACK UNDERFLOW
CAUSE A pop was attempted on an empty try-recover stack.
ACTION This is a compiler error. Record the steps that
produced the error and report the problem to your
System Manager.
------------------------------------------------------------------
3100
MESSAGE !: NOT A VALID LIBRARY/PROGRAM FILE (CORRUPT FILE
ID)
CAUSE The named file has the correct filecode but
contains a corrupted field in its header record.
This usually indicates that the file has been
corrupted, or that an invalid file has been created
with a filecode which HP Link Editor/XL recognizes.
ACTION Verify that you have entered the correct file and
that its name is spelled correctly. It the file
and filecode are correct, replace or rebuild the
file.
------------------------------------------------------------------
3101
MESSAGE !: NOT A VALID OBJECT FILE (CORRUPT FILE ID)
CAUSE The named file has the correct filecode but
contains a corrupted field in its header record.
This usually indicates that the file has been
corrupted, or that an invalid file has been created
with a filecode which HP Link Editor/XL recognizes.
ACTION Verify that you have specified a relocatable object
file, that it is the correct one and that its name
is spelled correctly. It the file and filecode are
correct, replace or rebuild the file.
------------------------------------------------------------------
3102
MESSAGE !: NOT A VALID PROGRAM FILE (CORRUPT FILE ID)
CAUSE The named file has the correct filecode but
contains a corrupted field in its header record.
This usually indicates that the file has been
corrupted, or that an invalid file has been created
with a filecode which HP Link Editor/XL recognizes.
ACTION Verify that you have entered the correct file and
that its name is spelled correctly. It the file
and filecode are correct, replace or rebuild the
file.
------------------------------------------------------------------
3103
MESSAGE !: MORE OBJECT MODULES EXPECTED IN THIS OBJECT FILE
CAUSE This relocatable object file contains a series of
relocatable object modules and one of this series
of relocatable object modules is missing. This
usually indicates that the file has been corrupted.
ACTION Verify that you have included the correct file and
that you have spelled the name correctly. If the
spelling is correct, replace or rebuild the file.
------------------------------------------------------------------
3104
MESSAGE HEAP ALLOCATION ERROR
CAUSE This message usually indicates that HP Link
Editor/XL attempted to allocate heap space and
system resource limitations caused the allocation
to fail.
ACTION If this error persists, document the steps that
produced this problem and report the problem to
your System Manager.
------------------------------------------------------------------