HP 3000 Manuals HP 3000 Manuals
Numbered Error Messages ( 1739 - 2103 )
---------------------------------------------------------------------------------------
1739 MESSAGE The dimensionality of formal and actual parameter #parm_num do
not match.
CAUSE Scalar formal parameter and array actual parameter or vice
versa do not match, or formal and actual array parameters do
not have the same number of dimensions.
ACTION Correct actual parameter number parm_num so that it is the same
dimensionality as the formal parameter.
---------------------------------------------------------------------------------------
1740 MESSAGE Actual parameter #parm_num to be passed by reference is not a
variable.
CAUSE A literal or an expression actual parameter is being passed
where the formal parameter specifies that a variable by
reference is required.
ACTION Assign the value of the literal or expression to a variable of
the type and dimensionality that corresponds to that of the
formal parameter. Substitute the variable for the literal or
expression that is parameter number parm_num.
---------------------------------------------------------------------------------------
1741 MESSAGE Missing actual parameter without default value specified for
formal parameter #parm_num of type parm_type.
CAUSE A required parameter in the call is missing. When HP Business
BASIC/XL attempts to provide the default value, none is
present. The error will occur when a parameter is missing:
CALL Ext(A,,B)
For example, the error will occur when three parameters are
required and only two are provided:
CALL Need_three(A,B)
Normally, HP Business BASIC/XL will provide the defaults that
allow the externals to be called by using the information
present in the intrinsic file.
ACTION Add the default parameter to the definition in the intrinsic
file. Supply the actual parameter, parm_num, of type
parm_type.
---------------------------------------------------------------------------------------
1742 MESSAGE Invalid formal parameter type for parameter #parm_num:
parm_type.
CAUSE The actual parameter number parm_num does not have a type that
corresponds to one of the HP Business BASIC/XL data types.
ACTION Change the definition in the intrinsic file or use the default
by leaving out the actual parameter in the actual parameter
list.
---------------------------------------------------------------------------------------
1743 MESSAGE Non-numeric or non-scalar actual parameter #parm_num cannot be
passed by value.
CAUSE The actual parameter number parm_num is either non-numeric or
is not a scalar parameter.
ACTION Only scalar numeric values can be passed by value. Alter the
actual parameter so that it is a scalar.
---------------------------------------------------------------------------------------
1744 MESSAGE The actual parameter space requested for the call to proc_name
exceeds the maximum value of num_words at parameter #parm_num.
CAUSE The space allocated by the interpreter for parameter space was
exhausted when loading parameter number parm_num during the
call to proc_name.
ACTION Reduce the number of actual parameters for the call to
proc_name.
---------------------------------------------------------------------------------------
1745 MESSAGE The structure of the HP Business BASIC/XL string array actual
parameter is incompatible with the formal parameter #parm_num.
CAUSE An HP Business BASIC/XL string array was passed to a non-HP
Business BASIC/XL external.
ACTION Assign the element of the string array to a scalar string.
---------------------------------------------------------------------------------------
1746 MESSAGE Actual parameter #parm_num to be passed by anyvar is not a
variable.
CAUSE The intrinsic file specifies that formal parameter parm_num for
the call to the intrinsic must be a variable passed by
reference.
ACTION Assign the value of the literal or expression to a variable.
Substitute that variable for the literal or expression that is
parameter number parm_num.
---------------------------------------------------------------------------------------
1747 MESSAGE The type of the value returned by function func_name,
function_return_type, has no equivalent type in Business
BASIC/XL.
CAUSE function_return_type is not a valid HP Business BASIC/XL data
type that can be returned by a function.
ACTION Use the CALL statement to call the function without a return
value.
---------------------------------------------------------------------------------------
1748 MESSAGE The type or dimensionality of formal and actual parameter
#parm_num do not match.
CAUSE Either the type or dimensionality of the formal and actual
parameters do not match.
ACTION Check formal parameter number parm_num to be certain that the
corresponding actual parameter in the call has both the same
type and dimensionality.
---------------------------------------------------------------------------------------
1749 MESSAGE ALIAS name provided, alias_name, exceeds the maximum length of
max_length characters.
CAUSE The length of an alias name is too long.
ACTION Reduce the length of the alias name.
---------------------------------------------------------------------------------------
1750 MESSAGE Formal parameter #parm_num of type parm_type to procedure
proc_name has no corresponding Business BASIC/XL data type and
no default value.
CAUSE An error occurred while processing the definition of the
intrinsic proc_name, specifically while looking up information
for formal parameter number parm_num. HP Business BASIC/XL
will not be able to call proc_name because the data type of the
formal parameter has no corresponding type and no default value
is supplied.
ACTION Redefine the external proc_name in a new intrinsic file and
supply the default.
Define the external proc_name in an EXTERNAL statement and
supply the appropriate formal parameters.
---------------------------------------------------------------------------------------
1751 MESSAGE A BYTE type array parameter is an invalid data type for formal
parameter #parm_num.
CAUSE An external definition contained a BYTE type parameter. For
example,
EXTERNAL A(BYTE VALUE(A(*))
BYTE keywords are not allowed.
ACTION Remove the BYTE keyword from the list of formal parameters.
---------------------------------------------------------------------------------------
1752 MESSAGE BYTE type is an invalid data type for formal parameter
#parm_num to an Business BASIC/XL external.
CAUSE BYTE type formal parameters are not valid in an HP Business
BASIC/XL external definition.
ACTION Remove the BYTE keyword form the list of formal parameters.
---------------------------------------------------------------------------------------
1753 MESSAGE A scalar BYTE reference parameter is an invalid data type for
formal parameter #parm_num.
CAUSE A reference parameter of type BYTE is invalid. For example,
EXTERNAL PASCAL A(BYTE A)
ACTION Change the external's definition so that parameter number
parm_num is passed by value.
---------------------------------------------------------------------------------------
1754 MESSAGE Array formal parameter #parm_num by value is invalid.
CAUSE Only scalar formal parameters can be passed by value.
ACTION Remove the VALUE form the definition of the formal parameter
number parm_num in the formal parameter list.
---------------------------------------------------------------------------------------
1755 MESSAGE String or BYTE string formal parameter #parm_num by value is
invalid.
CAUSE An external definition has a string parameter passed by value.
For example,
EXTERNAL PASCAL A(VALUE A$)
EXTERNAL PASCAL B(BYTE VALUE A$)
ACTION Remove the VALUE keyword from the definition of the formal
parameter number parm_num.
---------------------------------------------------------------------------------------
1756 MESSAGE Intrinsic filename "intr_file_name" exceeds the maximum
filename length of max_file_name_length characters.
CAUSE An invalid filename has been provided.
ACTION Correct the name of the file.
---------------------------------------------------------------------------------------
1757 MESSAGE Formal parameter #parm_num passed by value to procedure
proc_name has incorrect default size of num_bytes bytes.
CAUSE The information for the default size supplied in the intrinsic
file contains an error.
ACTION Rebuild the intrinsic file.
---------------------------------------------------------------------------------------
1758 MESSAGE Formal parameter #parm_num passed by reference to procedure
proc_name has incorrect default size of num_bytes bytes.
CAUSE The information for the default size supplied in the intrinsic
file contains an error.
ACTION Rebuild the intrinsic file.
---------------------------------------------------------------------------------------
1759 MESSAGE Unable to lead procedure proc_name when searching in library
list beginning with xl_name.
CAUSE The entry point name specified does not exist in any of the
libraries in the library list.
ACTION Check the spelling of the external. Use the linkeditor to
check the names of the entry points in the libraries.
---------------------------------------------------------------------------------------
1760 MESSAGE Procedure or function proc_name not found in intrinsic file
"intr_file_name".
CAUSE The intrinsic entry does not exist in the intrinsic file,
intr_file_name.
ACTION Check the entries in the intrinsic file to be certain that the
entry exists.
---------------------------------------------------------------------------------------
1761 MESSAGE EXTENSIBLE value provided exceeds the valid range of
lower_bound to upper_bound.
CAUSE The value following the EXTENSIBLE keyword is not within the
bounds of lower_bound to upper_bound.
ACTION Change the definition so that the value is within the specified
range.
---------------------------------------------------------------------------------------
1762 MESSAGE External procedure proc_name has been previously defined.
CAUSE The procedure or function name to be used to call the external,
proc_name, is not unique in the main, procedure, or function.
Calls to the procedure or function will be ambiguous.
ACTION Change the spelling of one of the names of the procedures in
the external or intrinsic definitions.
---------------------------------------------------------------------------------------
1763 MESSAGE External name provided, proc_name, exceeds the maximum length
of max_num_characters .
CAUSE The external name length is too long.
ACTION Shorten the name so that it is less than max_num_characters in
length.
---------------------------------------------------------------------------------------
1764 MESSAGE Intrinsic intr_name parameter parm_num by reference has invalid
address type specification of address_type.
CAUSE Parameter number parm_num of the intrinsic intr_name has an
invalid address type specified in the intrinsic file.
ACTION Rebuild the intrinsic file.
---------------------------------------------------------------------------------------
1765 MESSAGE External proc_name has an entry point name, ent_point_name,
returned from the intrinsic file, that exceeds the maximum of
max_num_chars characters.
CAUSE The entry point name is too long.
ACTION Rebuild the intrinsic file using a shorter entry point name.
---------------------------------------------------------------------------------------
1766 MESSAGE The actual parameter space request for the call to proc_name of
num_words words exceeds the maximum value of max_num_words
words.
CAUSE An ANYPARM call requires num_words words of parameter space
when only max_num_words words are available.
ACTION Each actual parameter in the call to the ANYPARM procedure
requires two words of actual parameter space. Reduce the
number of actual parameters to the call.
---------------------------------------------------------------------------------------
1800 MESSAGE WARNING 1800: No closing quotation mark found!.
CAUSE A string literal had no closing quotation mark.
ACTION None. The interpreter will insert the missing quotation mark.
---------------------------------------------------------------------------------------
1801 MESSAGE WARNING 1801: String too long; re-enter from item "item-no"
CAUSE A string that is longer than the declared string variable was
entered.
ACTION Re-enter a string that is within the declared length or modify
the program to extend the declared string length.
---------------------------------------------------------------------------------------
1802 MESSAGE WARNING 1802: Input too long. Please re-enter.
CAUSE A string that is longer than the declared string variable in
the INPUT statement has been entered.
ACTION Re-enter a string that is within the declared length or modify
the program to extend the declared string length.
---------------------------------------------------------------------------------------
1804 MESSAGE WARNING 1804: The file "filename" did not previously exist
CAUSE A file that did not previously exist has been resaved.
ACTION None. The program will be saved with the SAVE command, rather
than the RESAVE command.
---------------------------------------------------------------------------------------
1805 MESSAGE MESSAGE 1805: Statement not implemented in HPBB ( at character
"char-num")
CAUSE The program uses an unimplemented feature.
ACTION Do not use the unimplemented feature.
---------------------------------------------------------------------------------------
1806 MESSAGE WARNING 1806: Name at character "number" too long. Name
Truncated.
CAUSE The identifier specified is longer than 64 characters.
ACTION None. The identifier is truncated to 64 characters.
---------------------------------------------------------------------------------------
1807 MESSAGE WARNING 1807: Bad numeric input; re-enter from item "item-no"
CAUSE The value entered does not match the type of the numeric
variable in the INPUT statement.
ACTION Re-enter the correct numeric value.
---------------------------------------------------------------------------------------
1809 MESSAGE WARNING 1809: The PROTECT word "string" was truncated to
"string".
CAUSE The lockword specified is longer than 8 characters.
ACTION None. The new lockword is truncated to 8 characters.
---------------------------------------------------------------------------------------
1811 MESSAGE WARNING 1811: COMMON area name too long, truncated to
"string".
CAUSE The common name specified is longer than nine characters.
ACTION None. The new name is truncated to nine characters.
---------------------------------------------------------------------------------------
1812 MESSAGE WARNING 1812: This statement is not compilable.
CAUSE This is a warning message issued by the interpreter command,
CWARNINGS, that lists statements that are not compilable. Any
statement that modifies an HP Business BASIC/XL program at run
time or requires the interpreter environment cannot be
compiled.
This warning occurs with the following statements:
COMMAND GET MERGE SCRATCH DEFAULT GETSUB RESAVE SECURE DELETE
LINK
ACTION The following change will prevent the execution of a
non-compilable statement in a compiled program:
100 GET "abc"
change to
100 IF INTERPRETED THEN GET "abc"
---------------------------------------------------------------------------------------
1813 MESSAGE WARNING 1813: This statement is not compilable. (generates no
code)
CAUSE This is a warning message generated by the interpreter command,
CWARNINGS, that lists statements that cause compiler warnings.
These statements are primarily for debugging and the compiler
does not generate any code for them.
ACTION None.
---------------------------------------------------------------------------------------
1814 MESSAGE WARNING 1814: Only one copy of subunit "name" will be saved.
CAUSE Multiple copies of a subunit were saved under the same name.
For example
> SAVE FILEX, SUB A, SUB B, SUB A ( SUB A is entered twice )
> SAVE FILEX, 10/100, SUB B ( SUB B is already saved in 10/100
)
ACTION None. Only one copy of subunit will be saved.
---------------------------------------------------------------------------------------
1815 MESSAGE WARNING 1815: The file contains invalid (SECUREd) program
lines.
CAUSE A program that has secured program lines in ASCII or in BASIC
DATA format has been saved. These secured lines will cause
syntax error during GET because only an "asterisk" is stored
for each secured statement.
ACTION When program lines are secured, always save the program in
BASIC SAVE format.
---------------------------------------------------------------------------------------
1816 MESSAGE WARNING 1816: Renumbering line ignored when GETting a BASIC
SAVE file.
CAUSE A line was renumbered during a BASIC SAVE GET.
ACTION None. You are allowed to renumber program lines only when
getting a BASIC DATA or an ASCII file.
---------------------------------------------------------------------------------------
1817 MESSAGE WARNING 1817: Unable to do a required purge of the temporary
file.
CAUSE A temporary file was created and could not be purged following
its use.
ACTION None. This is just a warning.
---------------------------------------------------------------------------------------
1818 MESSAGE WARNING 1818: NLS not installed, unable to open native message
catalog.
CAUSE Native Language Support is not installed on your system.
ACTION You must log on as MANAGER.SYS and run the LANGINST program to
add languages to the configuration file. Please refer to the
Native Language Programmer's Guide for more information about
installing native languages.
---------------------------------------------------------------------------------------
1819 MESSAGE WARNING 1819: Native language "num" is not configured
CAUSE The specified native language is not configured.
ACTION You must log on as MANAGER.SYS and run the LANGINST program to
add the language number to the configuration file. Please
refer to the Native Language Programmer's Guide for more
information about installing native languages.
---------------------------------------------------------------------------------------
1820 MESSAGE WARNING 1820: Error message text is now inaccessible.
CAUSE The message catalog file, HPBBCAT.PUB.SYS, is inaccessible.
ACTION Exit Business BASIC and find out what is wrong with
HPBBCAT.PUB.SYS.
---------------------------------------------------------------------------------------
1821 MESSAGE WARNING 1821: Recommend that you exit Business BASIC and retry.
CAUSE The message catalog is inaccessible. This message is an
additional message to warning 1820.
ACTION Exit Business BASIC and find out what is wrong with
HPBBCAT.PUB.SYS.
---------------------------------------------------------------------------------------
1822 MESSAGE WARNING 1822: Unable to open message catalog for native
language "num".
CAUSE The message catalog for the native language number num is not
available.
ACTION None. The default message catalog file, HPBBCAT.PUB.SYS, for
language number 0 is used instead.
---------------------------------------------------------------------------------------
1823 MESSAGE It is recommended that you VERIFY and then RESAVE this program.
CAUSE This warning message is generated if you have an old file
version. This does not mean the file cannot be read. It is a
suggestion.
ACTION VERIFY and RESAVE the program.
---------------------------------------------------------------------------------------
1830 MESSAGE WARNING 1830: Programs cannot be RUN with this amount of
subunit space.
CAUSE The amount of space available on the system is not sufficient
to run HP Business BASIC/XL.
ACTION Consult your system manager.
---------------------------------------------------------------------------------------
1831 MESSAGE WARNING 1831: RLINIT, RLFILE, and LOCALITY apply to MPE/XL
only.
CAUSE These compiler options apply to a native mode program on MPE/XL
only and will be ignored on other systems.
ACTION None.
---------------------------------------------------------------------------------------
1832 MESSAGE WARNING 1832: USLINIT applies only to MPE/V systems.
CAUSE COPTION USLINIT applies to MPE/V system only and is ignored on
MPE/XL system.
ACTION None.
---------------------------------------------------------------------------------------
2001 MESSAGE VERIFY is needed on subunit "name".
CAUSE A program containing a poorly formed program unit has been
saved. The interpreter issues a warning message and marks the
program unit as noncompilable.
ACTION Use the VERIFY command in the interpreter to find and correct
the problem.
---------------------------------------------------------------------------------------
2004 MESSAGE An expression is not allowed here.
CAUSE A parameter to the compiler options contains an expression.
ACTION Only use numbers or quoted strings for parameters in compiler
options.
---------------------------------------------------------------------------------------
2005 MESSAGE ERROR, HALT, or KEY statement found while NO ERROR HANDLING
option in effect.
CAUSE When COPTION NO ERROR HANDLING is used, ON ERROR, ON HALT, or
ON KEY statements cause a compile time error.
ACTION Take out the COPTION or do not use the ON ERROR, ON KEY, or ON
HALT statements.
---------------------------------------------------------------------------------------
2006 MESSAGE Parameter on "coption name" option is out of range.
CAUSE A numeric parameter to a compiler option is outside of it's
legal range. For example, a parameter of the LINES option is
outside the range of [0..9999].
ACTION Change the value to be the legal range for the compiler option.
---------------------------------------------------------------------------------------
2008 MESSAGE Error creating process: "error-num "
CAUSE The CREATEPROCESS intrinsic failed with error-num.
ACTION Please refer to the MPE XL Intrinsics Reference Manual for the
error numbers returned in the CREATEPROCESS intrinsic, or
consult your system manager.
---------------------------------------------------------------------------------------
2009 MESSAGE Error "error-num" in COMMAND intrinsic: "error-msg"
CAUSE The COMMAND intrinsic failed.
ACTION Please refer to the MPE XL Intrinsics Reference Manual for
error numbers returned in the COMMAND intrinsic, or consult
your system manager.
---------------------------------------------------------------------------------------
2010 MESSAGE Couldn't open input file.
CAUSE The input file specified for the compiler could not be opened.
Probable causes are that the file does not exist or it is
opened in a conflicting mode.
ACTION Check the compiler input file.
---------------------------------------------------------------------------------------
2011 MESSAGE Number of dimensions for array "name" not known in subunit
"name"
CAUSE The number of dimensions for the array name cannot be
determined at compile time.
ACTION Use the interpreter to explicitly dimension the array, specify
the exact number of asterisks in an array parameter, or access
a specific array element.
---------------------------------------------------------------------------------------
2012 MESSAGE Total space needed for variables is too big.
CAUSE The number or size of variables in the program exceeds the
limit.
ACTION Reduce the number or size of variables in the program.
---------------------------------------------------------------------------------------
2013 MESSAGE Total space needed for parameters is too big.
CAUSE The number or size of parameters to the subunit exceeds the
limit.
ACTION Reduce the number or size of parameters to the subunit.
---------------------------------------------------------------------------------------
2014 MESSAGE Total space needed for DATA is too big.
CAUSE The number or size of values in the DATA statements exceeds the
limit.
ACTION Reduce the number or size of values in the DATA statements.
---------------------------------------------------------------------------------------
2017 MESSAGE Fatal compiler error; compile terminated.
CAUSE A fatal compiler error was encountered, and the compile
terminated because of one of the following errors:
47 "Name" COMMON area does not exist.
47 Dimensions or type of COMMON variable in line "num" doesn't
match main.
1143 Can't read from file.
1499 Catastrophic error in heap management (unable to return
space).
2001 VERIFY is needed on subunit "name".
2012 Total space needed for variables is too big.
2013 Total space needed for parameters is too big.
2014 Total space needed for DATA is too big.
2011 Number of dimensions for array "name" not known in subunit
"name".
ACTION Use the interpreter to correct the problem, and recompile.
---------------------------------------------------------------------------------------
2018 MESSAGE Can't open internal communication file. File system error
"error-num".
CAUSE An HP Business BASIC/XL internal file could not be opened.
ACTION Consult your system manager or refer to the MPE XL Intrinsics
Reference Manual.
---------------------------------------------------------------------------------------
2019 MESSAGE Expression too complicated.
CAUSE The expression in the statement is too complicated, it might
cause stack overflow or code segment overflow.
ACTION The expression should be made simpler by putting parts of it
into temporary variables, and then using the variables in the
expression.
---------------------------------------------------------------------------------------
2020 MESSAGE Redimension of "array-name"() illegal because of NO REDIM
compiler option.
CAUSE When COPTION NO REDIM is used to disallow redimensioning of
arrays, any statements that attempt to change the dimension of
arrays will cause a compile time error. For example:
10 COPTION NO REDIM
20 DIM A(1,2)
30 MAT READ A(1,1) ! attempt to redim. A
ACTION Change the compiler option or change the statements so that no
redimensioning is done.
---------------------------------------------------------------------------------------
2021 MESSAGE BASIC Compiler Backend Error: [in procedure proc_name] 'Actual
backend error message.' Fatal compiler error; compile
terminated.
CAUSE A problem has been detected by one of the code generating
subsystems of the compiler. The error has occurred in either
the optimizer or the code generator itself. The procedure name
being compiled when the error occurred will be substituted for
proc_name, if it is known. In order to clarify the nature of
the error, the actual backend error message is printed as the
second line in the error message. All of these errors will
cause the compiler to abort. Serious errors will result in a
stack trace as well. The stack trace is helpful as
documentation for resolving the problem with your HP
representative.
ACTION Some of the problems can be corrected by reading the text of
the 'Actual backend error message' and rectifying the problem.
Other problems are internal compiler code generation problems
that should be reported to your HP representative.
Examples of 'Actual backend error message':
** MESSAGE Cannot open object file
obj_file_name (5209)
CAUSE The object code file specified in the
command to run the compiler cannot be
opened because the system is out of
disk space or because your disk space
limit, as set by the system
administrator, has been reached.
ACTION Make sure that a sufficient amount of
disk space exists.
** MESSAGE Invalid file code for object file
obj_file_name (5211)
CAUSE The object code file specified in the
command to run the compiler does not
have an NMOBJ or NMRL file code.
ACTION Check the file code for the file
named obj_file_name or the file
specified by you as the object code
file. BBCOBJ is the file that the
compiler uses after it has been
equated to your file.
** MESSAGE File file_name has invalid file code;
expected NMRL ( 5381 )
CAUSE The object code file specified in the
command to run the compiler does not
have an NMRL file code.
ACTION Check the file code for the file
named file_name or the file specified
by you as the object code file.
BCOBJ is the file that the compiler
uses after it has been equated to
your file. Either build an RL file
using the linkeditor or do not use
the RL compile options.
** MESSAGE File file_name has invalid record
size. Expected 128W records ( 5383 )
CAUSE The object code file specified in the
command to run the compiler is an RL
file with an NMRL file code that does
not have 128 word records.
ACTION Check the record length for the file
named file_name or the file specified
by you as the object code file.
BBCOBJ is the file that the compiler
uses after it has been equated to
your file. Build a new RL file using
the linkeditor.
---------------------------------------------------------------------------------------
2050 MESSAGE WARNING 2050: TRACE or PAUSE statement found and ignored.
CAUSE The compiler did not generate any code for a TRACE or PAUSE
statement.
ACTION None. These statements are used primarily for debugging.
---------------------------------------------------------------------------------------
2051 MESSAGE WARNING 2051: Multiple copy of subunit "sub-name" found and not
compiled.
CAUSE Multiple copies of a subunit that have the same name were found
in the program.
ACTION If a program has more than one subunit with the same name, only
the one with the lowest line number is compiled. To compile a
higher-numbered subunit, remove the lower-numbered one with the
same name.
---------------------------------------------------------------------------------------
2053 MESSAGE WARNING 2053: Noncompilable statement; run-time error will
result.
CAUSE Any statement that attempts to modify an HP Business BASIC/XL
program at run time or requires the interpreter environment
will result in a run-time error. The following statements
generate this warning.
COMMAND
GET
MERGE
SCRATCH
DEFAULT
GETSUB
RESAVE
SECURE
DELETE
LINK
ACTION The following change will prevent the execution of a
non-compilable statement in the compiled program:
100 GET "abc"is changed to 100 IF INTERPRETED THEN GET "abc"
---------------------------------------------------------------------------------------
2054 MESSAGE WARNING 2054: "array-name"() may be redimensioned despite NO
REDIM compiler option.
CAUSE A matrix operation that might cause an implicit redimensioning
of an array will generate this warning message at compile time.
For example,
10 COPTION NOREDIM
20 DIM A(4,2), B(2), C(5)
30 MAT C = MUL(A,B) ! C may be redimensioned
ACTION None, if you know exactly how the array will be redimensioned.
Otherwise, the results will be unpredictable when the array is
redimensioned. The compiler will not generate code to check
the array bounds with COPTION NOREDIM.
---------------------------------------------------------------------------------------
2055 MESSAGE WARNING 2055: Redim of "array-num"() possible; check REDIM
coption of actual parms
CAUSE The array that is passed in the actual parameter might be
redimensioned and COPTION NOREDIM is used in the caller
subroutine.
ACTION None if you know exactly how the array will be redimensioned.
Otherwise, the results will be unpredictable when the array is
redimensioned and you are not aware of the changes. The
compiler will not generate code to check the array bounds with
COPTION NOREDIM.
---------------------------------------------------------------------------------------
2056 MESSAGE WARNING 2056: [on line line_num: ]'Actual backend warning
message.'
or
WARNING 2056: in procedure proc_name: 'Actual backend warning
message.'
or
WARNING 2056: on line line_num in procedure proc_name: 'Actual
backend warning message.'
CAUSE This warning describes a non-fatal event that occurred during
program compilation. The line_num and proc_name are printed,
if available.
ACTION None, other than to be aware that the event may have an effect
on results.
Example of 'Actual backend warning message':
** MESSAGE Previous version of entry proc_name
was replaced (5080)
CAUSE The object code for the entry listed
has been replaced in the specified RL
file.
---------------------------------------------------------------------------------------
2100 MESSAGE Too many GOSUBs before a RETURN. Use MAXGOSUBS option to
increase maximum.
CAUSE Too many GOSUB statements were executed before a RETURN
statement was executed.
ACTION Use the MAXGOSUBS compiler option to increase the maximum
number of GOSUB statements allowed before a RETURN.
---------------------------------------------------------------------------------------
2101 MESSAGE An unknown arithmetic error occurred.
CAUSE This is caused by an internal problem.
ACTION Further investigation of this problem is required. Please
contact your Hewlett-Packard representative.
---------------------------------------------------------------------------------------
2103 MESSAGE Attempt to execute a noncompilable statement.
CAUSE Any statement that attempts to modify an HP Business BASIC/XL
program at run time or requires the interpreter environment
will result in run-time error. The following statements
generate this message.
COMMAND
GET
MERGE
SCRATCH
DEFAULT
GETSUB
RESAVE
SECURE
DELETE
LINK
ACTION The following change will prevent the execution of a
non-compilable statement in the compiled program:
100 GET "abc" is changed to 100 IF INTERPRETED THEN GET "abc"
---------------------------------------------------------------------------------------