HP 3000 Manuals HP 3000 Manuals
User Errors (1000-1499)
User errors result from entering incorrect commands or from using the
commands incorrectly. User errors cause the command that you entered to
fail. You must correct the cause of the error and re-enter the command.
------------------------------------------------------------------
1001
MESSAGE PROGRAM ENTRY POINT "!" NOT FOUND
CAUSE HP Link Editor/XL could not find an entry point for
the procedure.
ACTION Check to make sure an outer block is present in the
link or 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.
------------------------------------------------------------------
1002
MESSAGE ATTEMPT TO OPEN FILE "!" FAILED
CAUSE HP Link Editor/XL cannot open the named file for
reading.
ACTION Be sure that you typed the file's name (and group
and account) correctly. If the file exists, be
sure you have the required capabilities to read
this file. If the named file is either
NRT0.LIB.SYS, XL0.LIB.SYS, or MILLI.LIB.SYS, one of
these required files is missing from your system.
In this case, contact your System Manager.
------------------------------------------------------------------
1003
MESSAGE ATTEMPT TO CREATE FILE "!" FAILED
CAUSE HP Link Editor/XL cannot create the named file for
writing.
ACTION Be sure that you have the required capabilities for
creating files in the group and account.
------------------------------------------------------------------
1004
MESSAGE DUPLICATE SYMBOL "!" IN "!"
CAUSE HP Link Editor/XL found two relocatable object
modules that define the same symbol. (The error
message names the file that contains the second
definition.)
ACTION Be sure that you have not linked the same module
twice. Also ensure that two source files have not
declared the same procedure name, outer block,
global variable or BLOCK DATA subprogram. If two
files have declared the same symbol, go back to one
of the source files, change the name of the symbol,
then recompile.
------------------------------------------------------------------
1005
MESSAGE FOUND ! DUPLICATE SYMBOL(S)
CAUSE This message summarizes the number of duplicate
symbols originally detected and listed by error
message 1004.
ACTION Take the appropriate "action" for each duplicate
symbol that was identified by error message 1004.
------------------------------------------------------------------
1006
MESSAGE UNSATISFIED SYMBOLS:
CAUSE A relocatable object module that is being linked
has referenced an undefined symbol. This may
simply be a misspelled name, or it may indicate
that an object module was mistakenly omitted from
the LINK command. A list of the unsatisfied
symbols follows this message. A missing outer
block causes the symbol _start to be listed as
unresolved. Symbols followed by "(DATA)" indicate
a global variable that was not defined; other
symbols indicate undefined millicode or absolute
symbols. Undefined "code" symbols are not reported
as an error, but are passed to the loader for
run-time binding to executable libraries.
ACTION Either correct the use of the symbol in the source
program or include the missing module in the list
of modules to be linked together. An undefined
millicode symbol probably indicates that the
library MILLI.LIB.SYS is either missing or
incompatible with your system release or that you
have used a file equate for this file.
------------------------------------------------------------------
1010
MESSAGE FOUND ! TYPE CHECKING ERROR(S)
CAUSE One or more type checking mismatches are errors.
(Depending on the value of the PARMCHECK option of
the LINK and ADDXL commands, type checking
mismatches are either warnings or errors.) Not all
of the type mismatches (warning numbers 1502-1507)
may actually be errors; this message indicates the
number that are errors.
ACTION Check your source code and recompile, or request a
lower type checking level using the PARMCHECK
option.
------------------------------------------------------------------
1021
MESSAGE INDIRECT FILES NESTED TOO DEEPLY (MAXIMUM DEPTH IS
10)
CAUSE An indirect file may contain a reference to another
indirect file. You can use up to ten levels of
indirect files.
ACTION Check for an indirect file that references itself,
or for a set of indirect files that contains a
chain of circular references.
------------------------------------------------------------------
1022
MESSAGE RL FILE "!" MUST HAVE FILECODE NMRL
CAUSE A file that was included in the RL= list as part of
a LINK command has an incorrect filecode. This
usually indicates that the wrong file was named in
the LINK command.
ACTION Enter the correct file name.
------------------------------------------------------------------
1023
MESSAGE OBJECT FILE "!" MUST HAVE FILECODE NMOBJ OR NMRL
CAUSE A file that was included in the FROM= list as part
of a LINK command has an incorrect filecode. This
usually indicates that the wrong relocatable object
file was named in the LINK command.
ACTION Enter the correct file name.
------------------------------------------------------------------
1024
MESSAGE INDIRECT FILE "!" MUST BE AN ASCII FILE
CAUSE A file that you are using as an indirect file is a
binary file rather than an ASCII file.
ACTION Check that you have spelled the name of the
indirect file correctly.
------------------------------------------------------------------
1025
MESSAGE EXPECTED FILECODE NMPRG OR NMXL FOR TO= FILE
CAUSE You tried to LINK into an existing translated file.
ACTION Use a different filename for the TO= keyword of the
LINK command, or, purge the existing output file
and try the LINK command again.
------------------------------------------------------------------
1042
MESSAGE INCOMPATIBLE NUMBER OF ARGUMENTS: ! (!, !)
CAUSE The named procedure is referenced in one source
file and defined in another source file, but the
type checking information indicates that the two
declarations are incompatible.
ACTION Check the source code and correct the
incompatibility, or request a lower type checking
level through the PARMCHECK parameter of the LINK
or ADDXL command (so this error is reported as a
warning).
------------------------------------------------------------------
1043
MESSAGE INCOMPATIBLE PACKING: ! (!, !)
CAUSE The named procedure or global variable is
referenced in one source file and defined in
another source file, but the type checking
information indicates that the two declarations are
incompatible. If the symbol refers to a procedure
and the incompatibility is with its parameters, the
parameter number is listed on the following line.
ACTION Check the source code and correct the
incompatibility, or request a lower type checking
level through the PARMCHECK parameter of the LINK
or ADDXL command (so this error is reported as a
warning).
------------------------------------------------------------------
1044
MESSAGE INCOMPATIBLE ALIGNMENT: ! (!, !)
CAUSE The named procedure or global variable is
referenced in one source file and defined in
another source file, but the type checking
information indicates that the two declarations are
incompatible. If the symbol refers to a procedure
and the incompatibility is with its parameters, the
parameter number is listed on the following line.
ACTION Check the source code and correct the
incompatibility, or request a lower type checking
level through the PARMCHECK parameter of the LINK
or ADDXL command (so this error is reported as a
warning).
------------------------------------------------------------------
1045
MESSAGE INCOMPATIBLE MODE: ! (!, !)
CAUSE The named procedure or global variable is
referenced in one source file and defined in
another source file, but the type checking
information indicates that the two declarations are
incompatible. If the symbol refers to a procedure
and the incompatibility is with its parameters, the
parameter number is listed on the following line.
ACTION Check the source code and correct the
incompatibility, or request a lower type checking
level through the PARMCHECK parameter of the LINK
or ADDXL command (so this error is reported as a
warning).
------------------------------------------------------------------
1046
MESSAGE INCOMPATIBLE STRUCTURE: ! (!, !)
CAUSE The named procedure or global variable is
referenced in one source file and defined in
another source file, but the type checking
information indicates that the two declarations are
incompatible. If the symbol refers to a procedure
and the incompatibility is with its parameters, the
parameter number is listed on the following line.
ACTION Check the source code and correct the
incompatibility, or request a lower type checking
level through the PARMCHECK parameter of the LINK
or ADDXL command (so this error is reported as a
warning).
------------------------------------------------------------------
1047
MESSAGE INCOMPATIBLE TYPE: ! (!, !)
CAUSE The named procedure or global variable is
referenced in one source file and defined in
another source file, but the type checking
information indicates that the two declarations are
incompatible. If the symbol refers to a procedure
and the incompatibility is with its parameters, the
parameter number is listed on the following line.
ACTION Check the source code and correct the
incompatibility, or request a lower type checking
level through the PARMCHECK parameter of the LINK
or ADDXL command (so this error is reported as a
warning).
------------------------------------------------------------------
1100
MESSAGE "ENTRY=" NAME IS LONGER THAN 132 CHARACTERS
CAUSE HP Link Editor/XL restricts the names for symbols
in library symbol tables to 132 characters, but you
entered an entry point name that exceeds this
limit.
ACTION Give the entry point a name that contains 132
characters or less.
------------------------------------------------------------------
1101
MESSAGE "LSET=" NAME IS LONGER THAN 132 CHARACTERS
CAUSE HP Link Editor/XL restricts the names for symbols
in library symbol tables to 132 characters, but you
entered a locality set name that exceeds this
limit.
ACTION Give the locality set a name that contains 132
characters or less.
------------------------------------------------------------------
1102
MESSAGE "MODULE=" NAME IS LONGER THAN 132 CHARACTERS
CAUSE HP Link Editor/XL restricts the names for symbols
in library symbol tables to 132 characters. You
entered a module name that exceeds this limit.
ACTION Give the module a name that contains 132 characters
or less.
------------------------------------------------------------------
1103
MESSAGE NO CURRENT ! IS OPEN; YOU MUST SPECIFY A "FROM"
FILE
CAUSE Certain library maintenance commands let you omit
the FROM= file and use a currently active file
instead. In this case, you omitted the FROM= file,
but no default file is established.
ACTION Either open a default file and enter the same
command, or re-enter the command using the FROM=
parameter.
------------------------------------------------------------------
1104
MESSAGE NO CURRENT RELOCATABLE LIBRARY IS OPEN; YOU MUST
SPECIFY AN RL FILE
CAUSE Certain library maintenance commands let you omit
the RL= file and use a currently active relocatable
library instead. In this case, you omitted the RL=
parameter, but no relocatable library file was
selected as the currently active relocatable
library.
ACTION Either use the RL or BUILDRL command to establish a
currently active relocatable library, or re-enter
the command using the RL= parameter.
------------------------------------------------------------------
1105
MESSAGE NO CURRENT ! IS OPEN; YOU MUST SPECIFY A "TO" FILE
CAUSE Certain library maintenance commands let you omit
the TO= file and use a currently active file
instead. In this case, you omitted the TO= file,
but no default file is established.
ACTION Either open a default file and enter the same
command, or re-enter the command using the TO=
parameter.
------------------------------------------------------------------
1106
MESSAGE NO CURRENT EXECUTABLE LIBRARY IS OPEN; YOU MUST
SPECIFY AN XL FILE
CAUSE Certain library maintenance commands let you omit
the XL= file and use a currently active executable
library instead. In this case, you omitted the XL=
parameter, but no executable library file was
selected to be the currently active executable
library.
ACTION Either use the XL or BUILDXL command to establish a
currently active executable library, or re-enter
the command using the XL= parameter.
------------------------------------------------------------------
1107
MESSAGE "RL=" FILES MAY NOT BE SPECIFIED WITHOUT ALSO
SPECIFYING THE MERGE OPTION
CAUSE The ADDRL and ADDXL commands allow you to specify
relocatable libraries to resolve external
references only when you request the MERGE option.
ACTION Re-enter the command using the MERGE option.
------------------------------------------------------------------
1108
MESSAGE "UNSAT=" NAME IS LONGER THAN 132 CHARACTERS
CAUSE HP Link Editor/XL restricts the names for entries
in library symbol tables to 132 characters. You
have given an UNSAT procedure a name that exceeds
this limit.
ACTION Give the UNSAT procedure a name that contains 132
characters or less.
------------------------------------------------------------------
1109
MESSAGE ! IS NOT A LEGAL VALUE FOR PARMCHECK. IT MUST BE IN
THE RANGE [0..3]
CAUSE You have used an illegal value for the PARMCHECK
parameter to the LINK or ADDXL command.
ACTION Re-enter the command using a value between 0 and 3
for the PARMCHECK parameter.
------------------------------------------------------------------
1110
MESSAGE ATTEMPT TO ADD MODULE(S) BEYOND LIBRARY LIMIT (!)
CAUSE You have exceeded the limit for object modules in a
relocatable or executable library. (HP Link
Editor/XL sets the limit to 2000 for relocatable
libraries and 500 for executable libraries if you
do not specify a limit when you build the library.)
ACTION Build a new library file using a larger limit, copy
the contents of the old library into the new
library, then add the object modules that produced
this "overflow" condition.
------------------------------------------------------------------
1111
MESSAGE SYMBOL "!", ENCOUNTERED IN "!", WAS PREVIOUSLY
DEFINED
CAUSE When adding modules to a library, HP Link Editor/XL
encountered a new definition for a previously
defined symbol.
ACTION Check that you have not added the same module
twice. Also ensure that two source files have not
declared the same procedure name or BLOCK DATA
subprogram.
------------------------------------------------------------------
1112
MESSAGE ATTEMPT TO OPEN/CREATE FILE "!" FAILED
CAUSE Certain HP Link Editor/XL commands attempt to open
or create a file to serve as an input source or an
output destination. In this case, HP Link
Editor/XL either tried to open a file that doesn't
exist, or tried to create a new file but found a
file with that name already exists.
ACTION Consult the section of the manual that describes
the command you are using and determine whether or
not the named file should exist.
------------------------------------------------------------------
1113
MESSAGE "TO=" FILE "!" IS THE SAME AS "FROM=" FILE "!".
THEY MUST BE UNIQUE
CAUSE Certain HP Link Editor/XL commands accept both
FROM= and TO= files. In this case, you have named
the same file for both parameters.
ACTION Determine which file you want to be your FROM= file
and which file you want to be your TO= file. Then
ensure that their names are distinct.
------------------------------------------------------------------
1114
MESSAGE "! IS NOT A LEGAL VALUE FOR PRIVLEV. IT MUST BE IN
THE RANGE [0..3]"
CAUSE You have used an illegal value for the PRIVLEV
parameter of the LINK or ADDXL commands.
ACTION Re-enter the command using a value between 0 and 3
for the PRIVLEV parameter.
------------------------------------------------------------------
1115
MESSAGE "! IS NOT A LEGAL VALUE FOR XLEAST. IT MUST BE IN
THE RANGE [0..3]"
CAUSE You have used an illegal value for the XLEAST
parameter of the LINK or ADDXL commands.
ACTION Re-enter the command using a value between 0 and 3
for the XLEAST parameter.
------------------------------------------------------------------
1116
MESSAGE LINK FAILED
CAUSE When HP Link Editor/XL encounters an error during
the linking process, it prints this "summary"
message as its last message before terminating.
ACTION Refer to the "action" description for the
previously listed error messages. Once you have
resolved those problems, this message goes away.
------------------------------------------------------------------
1117
MESSAGE LIMIT FOR A LIBRARY MUST BE IN THE RANGE
[1..400000]
CAUSE When you build a relocatable or executable library,
you must specify how many object modules that
library can contain. In this case, you have
specified a number outside of this range.
ACTION Re-enter the BUILDRL or BUILDXL command and use a
number between 1 and 400000 for the maximum number
of object modules.
------------------------------------------------------------------
1118
MESSAGE ! IS NOT A LEGAL VALUE FOR THE NMSTACK PARAMETER.
IT MUST BE A POSITIVE INTEGER
CAUSE An option to the LINK command lets you specify a
NMSTACK value. This number must be a positive
integer.
ACTION Re-enter the LINK command using a valid number for
the NMSTACK parameter.
------------------------------------------------------------------
1119
MESSAGE ! IS NOT A LEGAL VALUE FOR THE NMHEAP PARAMETER. IT
MUST BE A POSITIVE INTEGER
CAUSE An option to the LINK command lets you specify a
NMHEAP value. This number must be a positive
integer.
ACTION Re-enter the LINK command using a valid number for
the NMHEAP parameter.
------------------------------------------------------------------
1120
MESSAGE ONE OF { ENTRY, LSET, MODULE } MUST BE SPECIFIED
CAUSE The syntax for the PURGERL and PURGEXL commands
requires that you specify which object modules you
want to delete by either their entry point name,
their module name, or their locality set name. You
have omitted this parameter.
ACTION Re-enter the PURGERL or PURGEXL command and specify
which modules you want to delete.
------------------------------------------------------------------
1121
MESSAGE FILE "!" IS NOT A VALID "FROM=" FILE FOR ADDXL.
LEGAL INPUT IS EITHER A RELOCATABLE OBJECT FILE OR
A RELOCATABLE LIBRARY
CAUSE The ADDXL command adds relocatable object modules
and relocatable libraries to an executable library.
You entered a file that does not have the correct
filecode (NMOBJ or NMRL) for one of these files.
ACTION Re-enter the command and provide the name of a
relocatable object file or a relocatable library
file for the FROM= file.
------------------------------------------------------------------
1122
MESSAGE SPECIFIED ENTRY WAS NOT FOUND IN THE RELOCATABLE
LIBRARY
CAUSE You used a HIDERL or a REVEALRL command and the
symbol cannot be found in the relocatable library.
ACTION Be sure you have linked together all the
relocatable libraries that the program file
requires. Also verify that you have spelled the
name correctly (entries in symbol tables are case
sensitive).
------------------------------------------------------------------
1123
MESSAGE INDIRECT INPUT FILE "!" MUST BE AN ASCII FILE
CAUSE A file that you used as an indirect file is a
binary file rather than an ASCII file.
ACTION Create your indirect files using a text editor and
save them as ASCII files. If you have followed
this procedure, check that you have spelled the
name of the indirect file correctly.
------------------------------------------------------------------
1124
MESSAGE EXPECTED FILECODE ! FOR FILE "!"
CAUSE The input or output file you used with the link
editor command does not have the correct filecode.
ACTION Be sure you have spelled the file's name correctly.
If you have, check the description for the command
you are using to be sure you are using the correct
file as your input source or output destination.
------------------------------------------------------------------
1125
MESSAGE MISSING OPEN QUOTE FOR REDO/DO STRING
CAUSE You specified a search string for the REDO/DO
command that included a closing quote (either ' or
") but omitted the corresponding opening quote.
ACTION Re-enter the REDO/DO command, placing quotes at
both ends of the search string.
------------------------------------------------------------------
1126
MESSAGE MISSING CLOSE QUOTE FOR REDO/DO STRING
CAUSE You specified a search string for the REDO/DO
command that included an opening quote (either ' or
") but omitted the corresponding closing quote.
ACTION Re-enter the REDO/DO command, placing quotes at
both ends of the search string.
------------------------------------------------------------------
1127
MESSAGE SEARCH STRING SPECIFIED FOR REDO/DO IS INVALID
CAUSE A search string for a DO or REDO command must be
enclosed between a matching set of opening and
closing quotes. You may use either a single quote
mark (') or double quotes ("), but you can't mix
the two.
ACTION Re-enter the REDO/DO command, using the same
quotation marks at both ends of the search string.
------------------------------------------------------------------
1128
MESSAGE REDO/DO NUMBER IS OUT OF RANGE OF REDO STACK
CAUSE The DO and REDO commands accept either a search
string or an integer parameter that identifies an
entry on the redo stack. In this case, the number
you supplied does not correspond to any of the
values on the redo stack.
ACTION Use the LISTREDO command to verify the command
number you wish to repeat.
------------------------------------------------------------------
1129
MESSAGE NO MATCH ENCOUNTERED FOR REDO/DO SEARCH STRING
CAUSE The string pattern that you attempted to match on
the redo stack does not exist.
ACTION Use the LISTREDO command to help you select the
command you want to repeat.
------------------------------------------------------------------
1130
MESSAGE REDO/DO CANNOT BE THE FIRST COMMAND ENTERED
CAUSE You entered a DO or REDO command as the first
command within a HP Link Editor/XL session. As no
commands currently exist on the redo stack, the DO
and REDO commands are illegal.
ACTION Enter another HP Link Editor/XL command to initiate
the current session.
------------------------------------------------------------------
1131
MESSAGE NO HELP FOUND FOR COMMAND "!"
CAUSE You requested help with a command that does not
exist.
ACTION Verify that you have spelled the command correctly
and that the command is a valid HP Link Editor/XL
command (or the word "help").
------------------------------------------------------------------
1132
MESSAGE ATTEMPT TO REDO FAILED
CAUSE You have edited the response from a REDO command,
but the resulting command is invalid. The link
editor ignores the edited command.
ACTION Refer to the description of the REDO command in the
MPE XL Commands Reference Manual, then use the
supported conventions for editing commands.
------------------------------------------------------------------
1133
MESSAGE ENTRY NAME SPECIFIED BUT NOT FOUND
CAUSE You have used the ENTRY= option with the LINK
command to request an alternate entry point, but HP
Link Editor/XL failed to find the requested symbol.
ACTION Check that the specified symbol is spelled
correctly (case sensitive) and that the module that
defines this symbol is included in the files you
are linking together. Current compilers can't
generate secondary entry points.
------------------------------------------------------------------
1134
MESSAGE "!" IS NOT A VALID "XL=" FILENAME
CAUSE You have supplied a filename for the XL= option of
the LINK command which does not conform to the
syntax of a valid filename.
ACTION Check that the specified filename is of the right
form. The account, group, and file names must all
be valid lengths, and they must contain legal
characters.
------------------------------------------------------------------
1135
MESSAGE ATTEMPT TO WRITE TO FILE LINKLIST FAILED. FILE MAY
BE FULL
CAUSE When attempting to write to a file specified as the
LINKLIST file in a file equation, the end of file
was encountered.
ACTION Exit HP Link Editor/XL and increase the size of the
LINKLIST file.
------------------------------------------------------------------
1137
MESSAGE FILE "!" HAS A CORRUPT FILE END
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 the HP Link Editor/XL
recognizes.
ACTION Verify that you have entered the correct file and
that you have spelled the name correctly. If the
file name is correct, replace or rebuild the file.
------------------------------------------------------------------
1138
MESSAGE FILE "!" HAS A CORRUPT STRING AREA
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 you have spelled the name correctly. If the
file name is correct, replace or rebuild the file.
------------------------------------------------------------------
1139
MESSAGE FILE "!" HAS A CORRUPT SYMBOL TABLE
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 you have spelled the name correctly. If the
file name is correct, replace or rebuild the file.
------------------------------------------------------------------
1140
MESSAGE FILE "!" HAS A CORRUPT IMPORT TABLE
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 you have spelled the name correctly. If the
file name is correct, replace or rebuild the file.
------------------------------------------------------------------
1141
MESSAGE FILE "!" HAS A CORRUPT MODULE
CAUSE The named file has the correct filecode but
contains a corrupted field in its module directory.
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 you have spelled the name correctly. If the
file name is correct, replace or rebuild the file.
------------------------------------------------------------------
1142
MESSAGE THE OUTPUT FILE IS FULL
CAUSE A listing file, to which HP Link Editor/XL tried to
write, is full.
ACTION Exit HP Link Editor/XL and check the limit of the
listing file. If it is full, recreate the file
with a larger limit.
------------------------------------------------------------------
1143
MESSAGE ILLEGAL CAPABILITY SPECIFICATION
CAUSE You do not have the capability you specified on the
CAP= keyword of the LINK command. (USER
capabilities are not sufficient.)
ACTION Either have your System Manager give you the
capability you need, or do not specify that
capability on the CAP= keyword.
------------------------------------------------------------------
1144
MESSAGE ATTEMPT TO OPEN LKEDCAT.PUB.SYS FAILED
CAUSE HP Link Editor/XL cannot open its error message
catalog, LKEDCAT.PUB.SYS.
ACTION Check to be sure LKEDCAT.PUB.SYS exists. If not,
contact your System Manager.
------------------------------------------------------------------
1145
MESSAGE LIBRARY "!" IS CORRUPT. USE EITHER A CLEANRL OR A
CLEANXL COMMAND TO CLEAN THE LIBRARY
CAUSE The library contains errors.
ACTION If this is a relocatable library, use the CLEANRL
command to clean it. If it is an executable
library, use the CLEANXL command.
------------------------------------------------------------------
1146
MESSAGE LIBRARY "!" IS CORRUPT
CAUSE The library contains errors.
ACTION Re-create the library.
------------------------------------------------------------------
1147
MESSAGE OPERATION ON THIS OBJECT MODULE (!) REQUIRES SM
CAPABILITY
CAUSE The relocatable object module executes at privilege
level 0.
ACTION You must have SM capability to use ADDXL or to link
this module.
------------------------------------------------------------------
1148
MESSAGE THIS LIMIT HAS TO BE >= THE CURRENT NUMBER OF
MODULES (!) OR <= MAX MODULE LIMIT (400000)
CAUSE You have used an illegal value for the LIMIT
parameter of the CLEANRL or CLEANXL command.
ACTION Re-enter the command using a value which is greater
than or equal to the number of modules already
existing in the library, and less than or equal to
the maximum modules allowed (400000)
------------------------------------------------------------------
1149
MESSAGE THE STRING TABLE IN FILE ! DOES NOT HAVE ENOUGH
SPACE FOR THE STRING !
CAUSE While doing an ALTPROG command using the XL=,
ENTRY=, or UNSAT= keywords, the file you tried to
alter does not have enough room in its string table
to hold the new string.
ACTION Use the :RUN command to override the attributes
stored in the program file. Or, link the program
file again with the desired keyword specified on
the LINK command.
------------------------------------------------------------------
1150
MESSAGE ! IS NOT A LEGAL VALUE FOR THE PRI PARAMETER. IT
MUST BE IN THE RANGE 100-255 OR ONE OF [AS, BS, CS,
DS, ES]
CAUSE While doing an ALTPROG or LINK command you
specified an invalid value for the PRI= keyword.
ACTION Redo the LINK or ALTPROG command this time
specifying a value for the PRI= keyword which is
between 100 and 255 inclusive, or the values AS,
BS, CS, DS, ES.
------------------------------------------------------------------
1151
MESSAGE ! IS NOT A LEGAL VALUE FOR THE MAXPRI PARAMETER. IT
MUST BE IN THE RANGE 100-255 OR ONE OF [AS, BS, CS,
DS, ES]
CAUSE While doing an ALTPROG or LINK command you
specified an invalid value for the MAXPRI= keyword.
ACTION Redo the LINK or ALTPROG command this time
specifying a value for the MAXPRI= keyword which is
between 100 and 255 inclusive, or the values AS,
BS, CS, DS, ES.
------------------------------------------------------------------
1154
MESSAGE THE ! FIELD DOES NOT EXIST IN PROGRAM FILE !. THE
FIELD WAS NOT CHANGED.
CAUSE While doing an ALTPROG command you specified a
keyword which changes a field in the program file
which does not exist in the program file you
specified. This can only happen if you are trying
to alter the PRI or MAXPRI fields in a program file
built with an older link editor.
ACTION If the fields are necessary for your application,
you must link the application with this link
editor. Otherwise, if the fields are not relevant
to you do not specify them on the ALTPROG command
line.
------------------------------------------------------------------