HP 3000 Manuals HP 3000 Manuals
Numbered Error Messages ( 1241 - 1738 )
---------------------------------------------------------------------------------------
1241 MESSAGE Line range "line_range" contains no lines.
CAUSE Part of the current program was saved or resaved to a BASIC
SAVE file using the line range list option. The range of lines
selected did not contain any lines. For example, you might
have typed:
SAVE "save_filename",SUB A/20
when the current program was:
20 PRINT B
30 SUB A
ACTION The line range option with SAVE to a BASIC SAVE file is
restricted to saving MAIN and individual procedures and
multi-line functions. If you wish to save individual parts of
the current program using the line range option, SAVE or RESAVE
to an ASCII file using the SAVE LIST or RESAVE command.
---------------------------------------------------------------------------------------
1242 MESSAGE Line number is not first line of subunit in line range
"line_range".
CAUSE Part of the current program was saved or resaved to a BASIC
SAVE file using the line range list option. The range of lines
selected did not specify an entire main, procedure, or
function. For example, you might have typed:
SAVE "save_filename",20
when the current program was:
10 PRINT A
20 PRINT B
ACTION The line range option with SAVE to a BASIC SAVE file is
restricted to saving MAIN and individual procedures and
multi-line functions. If you wish to save individual parts of
the current program using the line range option, SAVE or RESAVE
to an ASCII file using the SAVE LIST or RESAVE command.
---------------------------------------------------------------------------------------
1243 MESSAGE Line number is not last line of subunit in line range
"line_range".
CAUSE Part of the current program was saved or resaved to a BASIC
SAVE file using the line range list option. The range of lines
selected did not specify an entire main, procedure, or
function. For example, you might have typed:
SAVE "save_filename",10
when the current program was:
10 PRINT A
20 PRINT B
ACTION The line range option with SAVE to a BASIC SAVE file is
restricted to saving MAIN and individual procedures and
multi-line functions. If you wish to save individual parts of
the current program using the line range option, SAVE or RESAVE
to an ASCII file using the SAVE LIST or RESAVE command.
---------------------------------------------------------------------------------------
1245 MESSAGE No SAVE/RESAVE done, program contains no lines.
CAUSE There are no lines in the current program to be saved.
ACTION Enter a program line in the interpreter prior to doing a SAVE
or RESAVE.
---------------------------------------------------------------------------------------
1246 MESSAGE No SAVE/RESAVE done, default file does not exist.
CAUSE The current program has been saved or resaved, but no file name
has been specified either for the current program or in the
command.
ACTION Use the NAME command to name the current program and then do a
SAVE or RESAVE.
ACTION Specify the name of the file to which the current program is to
be saved as par of the SAVE or RESAVE command.
---------------------------------------------------------------------------------------
1247 MESSAGE RESAVE file must be of type BASIC SAVE, BASIC DATA, or ASCII
CAUSE The current program has been saved to a file which has no file
code and is not an ASCII file or has a file code other than
BSVXL or BDTXL.
ACTION Correct the spelling of the name of the current program in the
interpreter using the NAME command and then do a SAVE or
RESAVE.
ACTION Choose another filename to which to save the current program.
Use SAVE LIST "filename", SAVE BDATA "filename" or SAVE
"filename" to save the current program to the alternative
filename.
---------------------------------------------------------------------------------------
1248 MESSAGE File type given doesn't match the type of the file
named/implied.
CAUSE The current program has been resaved using the LIST option to a
file that is not an ASCII file or using the BDATA option to a
file that does not have a BSVXL file code.
ACTION Use RESAVE LIST to resave the current program to an ASCII file.
Use RESAVE BDATA to store the current program to a file that
has a BSVXL file code.
---------------------------------------------------------------------------------------
1249 MESSAGE No RESAVE done, unable to purge the old file.
CAUSE The RESAVE command failed either because of simultaneous file
access by two users or because of a serious file system
problem.
ACTION Retry the command. If it does not work a second time, use SAVE
to save the current program. Try to purge the old file using
the PURGE command and then rename the newly created file with
the RENAME command. If this does not work correctly, contact
your System Administrator.
---------------------------------------------------------------------------------------
1250 MESSAGE Execution label specified is not in the current program unit.
CAUSE This is a substitute message for error number 3: The parameter
to the RUN command specifying the line on which execution is to
begin is not present in the current program. For example, if
the current program has no lines then RUN; Label
will generate this error.
ACTION Be certain that the line label specified exists in the current
program.
---------------------------------------------------------------------------------------
1253 MESSAGE Line number is invalid or missing, GET terminated.
CAUSE This occurs in the interpreter only. During the GET of an
ASCII file a line in the file has been encountered which does
not begin with a numeric literal that should correspond to a
line number.
ACTION Use the SYSTEMRUN command from within BASIC to run an editor.
Change the line displayed during the GET so that it begins with
a numeric literal. Save the new version, exit the editor, and
use the GET command to make the ASCII file the current program
file.
---------------------------------------------------------------------------------------
1254 MESSAGE Line number would be illegal if renumbered, GET terminated.
CAUSE A GET of a program would result in a line number beyond the
maximum line number in the interpreter, 999999.
ACTION Check the last line number and the range of the lines to be
included in the current program prior to using GET. The
RENUMBER command can create additional space in the interpreter
by reducing the range of the program line numbers before using
GET.
---------------------------------------------------------------------------------------
1260 MESSAGE Found 11th named COMMON area in subunit "subunit_name", only 10
are allowed.
CAUSE More than the maximum number of COMMON areas have been declared
in the current MAIN, procedure, or function. The
"subunit_name" is either MAIN or the name of the procedure or
function in which the error occurred.
ACTION Delete one of the named COMMON areas in the specified subunit.
If the variables have to be declared in a COMMON, add them to
one of the named COMMON areas that are already declared or pass
them to the procedure or function as parameters.
---------------------------------------------------------------------------------------
1261 MESSAGE Not enough memory available for the existing COMMON
declarations.
CAUSE The total COM area declared in the current main, procedure, or
function exceeds the maximum space allocatable to common
declarations but is less than the total amount of space
allocatable to all declarations.
ACTION Reduce the number of declarations in the COM area to include
only those absolutely necessary for all procedures or functions
that include that COM area. All variables not required in all
can either be declared locally or passed as parameters.
---------------------------------------------------------------------------------------
1262 MESSAGE Unable to allocate enough memory for the COMMON variables.
CAUSE HP Business BASIC/XL was unable to allocate enough memory for
the COMMON variables.
ACTION Reduce the number of declarations in the common areas. Reduce
the size of the common area.
---------------------------------------------------------------------------------------
1270 MESSAGE Arrays need to be of the same type.
CAUSE The type of the floating point numeric argument to the matrix
built-in functions, CSUM, INV, MUL, RSUM, and TRN must be the
same as the type of the numeric target of the MAT assignment
statement in which the built-in occurs. Both of the arguments
to the DOT operation must be the same numeric type.
ACTION Coerce the argument prior to performing the built-in operation
or coerce the result after the assignment.
---------------------------------------------------------------------------------------
1271 MESSAGE Wrong type for inverse.
CAUSE The array that is the argument for the INV matrix built-in
function is not of type SHORT DECIMAL, DECIMAL, SHORT REAL or
REAL.
ACTION Correct the type of the argument so that it is one of the
floating point types supported in HP Business BASIC/XL.
---------------------------------------------------------------------------------------
1272 MESSAGE Could not purge the temporary save file, system error
#"error_number".
CAUSE During execution of one of the statements or commands that
requires the creation of a temporary BASIC SAVE file, a file
was created and could not be purged following use. The
statements requiring creation of a BASIC SAVE file for this
purpose are COMPILE, COMPGO, and COMPLINK.
ACTION Note the return value of "error_number" and report the problem
to your System Administrator. If you see this error message,
check the contents of your temporary file space with the
:LISTFTEMP command from within HP Business BASIC/XL. If you are
unable to purge the files either from within HP Business
BASIC/XL or the Command Interpreter of MPE, then log off and
log on again.
---------------------------------------------------------------------------------------
1273 MESSAGE Could not "message" while compiling, system error #
"system_error_number".
CAUSE message corresponds to the command that the interpreter could
not process when trying to run the compiler:
FILE BBCTEXT="text_filename"
FILE BBCOBJ="obj_or_rl_filename"
FILE BBCLIST="list_filename"
RESET BBCTEXT="text_filename"
RESET BBCOBJ="obj_or_rl_filename"
RESET BBCLIST="list_filename"
"system_error_number" is the error number returned from the
Command intrinsic.
ACTION These errors should only occur when the system is having
trouble performing fundamental file operations. Try to repeat
the same operation from the interpreter. If you again run into
problems, contact your System Administrator.
---------------------------------------------------------------------------------------
1274 MESSAGE Could not "message" during link, error #"error_number".
CAUSE message corresponds to a command that the interpreter could not
process when trying to link a compiled program. The
interpreter must build a stdin and stdlist file for the
linkeditor. The following commands are related to file
manipulation:
BUILD the stdlist file "stdlist_filename"
BUILD the stdin file "stdin_filename"
FILE PFILE="stdin_filename",OLDTEMP
FILE LFILE="stdlist_filename",OLDTEMP
RESET PFILE
RESET LFILE
PURGE "stdin_filename",TEMP
PURGE "stdlist_filename",TEMP
For this set of messages, "error_number" is the error number
returned from the command intrinsic indicating the system error
encountered.
The interpreter must also enter command information into the
stdin file. The following messages reflect possible file
system problems encountered:
FOPEN the stdin file
FWRITE to the stdin file
FCLOSE the stdin file
For this set of messages, "error_number" is the file system
error number.
ACTION These errors should only occur when the system is having
trouble performing fundamental file operations. Try to repeat
the same operation from the interpreter. If you again run into
problems, contact your System Administrator.
CAUSE message corresponds to a problem encountered when trying to run
the linkeditor to link the program. The problem can either be
the result of a problem with the program or with the system.
If the message is only: system run of linkeditor then try to
repeat the error. If you can do so, this indicates a system
problem and should be discussed with your System Administrator.
If the message is preceded by the output from the segmenter
explaining the problems with the program, then you should
consult the HPLink Editor/XL Reference Manual.
error_number is the JCW following the execution of the
linkeditor program.
ACTION If the segmenter or linkeditor is aborting then repeat the same
operation from the interpreter. If you again run into
problems, contact your System Administrator.
For the second class of problems, look carefully at the error
output from the segmenter or linkeditor, consult the
appropriate reference manual and fix the problem.
---------------------------------------------------------------------------------------
1275 MESSAGE Terminal does not recognize escape sequences used by BASIC for
terminal control.
CAUSE One of the HP Business BASIC/XL statements dependent on
terminal interactions, such as FORM statements, CURSOR
statements, or KEY statements, is being used on a terminal that
does not return the correct escape sequences when queried or on
a system on which the configuration file, HPBBCNFG.PUB.SYS,
specifies that the terminal is not compatible with BASIC's
terminal-specific features.
ACTION If you are working on a terminal that is compatible with HP
Business BASIC/XL's terminal-specific features, check the
configuration file.
ACTION If you are working on a terminal that is not compatible with HP
Business BASIC/XL's terminal-specific features, you will not be
able to use these features.
---------------------------------------------------------------------------------------
1276 MESSAGE Invalid KEY number. Must be between 1 and 8.
CAUSE The value of a numeric literal or a numeric expression
corresponding to one of the keys specified in an ON KEY, OFF
KEY, or PRESS KEY statement is not within the range [1,8].
ACTION Correct the value of the numeric literal or, if it is an
expression, perform run-time checking of the value of the
numeric variable or numeric expression prior to using that
value in the statement.
---------------------------------------------------------------------------------------
1277 MESSAGE File is not a BKEY file.
CAUSE The name of the file specified in the GET KEY or RESAVE KEY
statement does not have a BKEY file code.
ACTION Be certain that the file to which you are trying to resave keys
does not exist or has a BKEY format.
ACTION Be certain that the file from which you are trying to obtain
key definitions using the GET KEY statement has a BKEY format.
---------------------------------------------------------------------------------------
1278 MESSAGE Invalid PRIORITY number. Must be between 1 and 15
CAUSE When this occurs in the interpreter, this syntax error occurs
because the numeric literal in the PRIORITY clause of the ON
KEY statement is not within the range [1,15].
When this occurs at run-time, the value of the numeric variable
in the PRIORITY clause of the ON KEY statement is not within
the range [1, 15].
ACTION Re-enter the line using a valid numeric literal value.
ACTION Check the value of the numeric variable before using it in the
PRIORITY clause.
---------------------------------------------------------------------------------------
1279 MESSAGE Invalid CURSOR parameter.
CAUSE One of the parameters for the position option is not within the
limits of current screen memory on the terminal being used.
CAUSE The parameter specifying the screen enhancement has an invalid
letter specified as a requested enhancement.
ACTION Be certain that the maximum value for the cursor position is
within bounds of the current screen memory.
ACTION Be certain that the screen enhancement specified is one of: h,
i, b, u, H, I, B, U, or the empty string.
---------------------------------------------------------------------------------------
1283 MESSAGE Program Analyst cannot be used if OUTPUT or SYSTEM OUTPUT are
redirected.
CAUSE The [SEND] OUTPUT [TO] or [SEND] SYSTEM OUTPUT TO statement has
been used to redirect the output to a device other than the
reserved word DISPLAY or the system file $STDLIST.
ACTION Use the INFO command to determine the device to which the
output is being sent and correctly reset the output to be
directed to DISPLAY.
---------------------------------------------------------------------------------------
1284 MESSAGE Valid arguments for ANALYST command are M, O, E, S, G, C, D and
P.
CAUSE Incorrect entry following the ANALYST command.
ACTION Re-enter the command followed by one of the valid characters
displayed. These characters select which of the ANALYST's
screens will be initially displayed.
---------------------------------------------------------------------------------------
1285 MESSAGE Program Analyst cannot be used when program contains no lines.
CAUSE The ANALYST command has been used when there is no program in
the interpreter.
ACTION Only use the ANALYST when there is a program in the
interpreter.
---------------------------------------------------------------------------------------
1286 MESSAGE Program Analyst can run on HP-supported terminals only.
CAUSE The ANALYST command has been used from a terminal that HP
Business BASIC/XL does not recognize as fully supporting
features such as CURSOR and ON KEY.
ACTION Use a different terminal. Also check to see if a configuration
file that specifies that the terminal is not HP-supported has
been used.
---------------------------------------------------------------------------------------
1287 MESSAGE Program Analyst cannot be run in batch mode.
CAUSE An ANALYST command has been encountered by the interpreter
while in batch mode.
ACTION Remove the ANALYST command from the stream file.
---------------------------------------------------------------------------------------
1288 MESSAGE Program Analyst cannot be used while program is running.
CAUSE An ANALYST command has been used while a program was paused
(either by the PAUSE statement or by an unhandled error).
ACTION Issue the STOP command before the ANALYST command.
---------------------------------------------------------------------------------------
1289 MESSAGE Program Analyst cannot be used with VERIFY errors in program.
CAUSE The ANALYST command was used when the program in the
interpreter contained structural errors. Some examples are a
WHILE without ENDWHILE or an ELSE without IF.
ACTION Modify the program so that there are no VERIFY errors.
---------------------------------------------------------------------------------------
1291 MESSAGE No VPLUS Form open.
CAUSE A Forms I/O statement has been used when no form is currently
active.
ACTION Be sure that the OPEN FORM statement is executed before any
Forms I/O operation is attempted.
---------------------------------------------------------------------------------------
1292 MESSAGE Bad form name "formname".
CAUSE The string in quotes was used in a OPEN FORM statement, but is
not a valid form name.
ACTION Check the syntax and correct the program.
---------------------------------------------------------------------------------------
1293 MESSAGE "filename" is not a forms file.
CAUSE The filename in quotes is an existing file, but not a VPLUS
forms file.
ACTION Use the correct filename for the forms file.
---------------------------------------------------------------------------------------
1294 MESSAGE Normal Input and Output cannot occur when a VPLUS form is open.
CAUSE A PRINT, DISP, INPUT, or similar operation has been executed
while a VPLUS form is active.
ACTION If a form has been left active inadvertently, then insert a
CLOSE FORM statement. Otherwise, use the READ FORM and WRITE
FORM statements.
---------------------------------------------------------------------------------------
1295 MESSAGE Problem with reading from or writing to the terminal.
CAUSE A VPLUS error occurred while the program was reading from or
writing to a terminal.
ACTION Check the hardware connection.
---------------------------------------------------------------------------------------
1296 MESSAGE Too many items specified in WRITE FORM or READ FORM.
CAUSE More items have been specified in a WRITE FORM or READ FORM
statement than the declared in the FORM.
ACTION Check the FORM specification or the FORM I/O statement.
---------------------------------------------------------------------------------------
1297 MESSAGE Form field not big enough for item "num".
CAUSE The value of the item specified in the WRITE FORM will overflow
the declared type for the FORM.
ACTION Correct the range or length of the item specified in the FORM.
ACTION Correct the value of the item in the WRITE FORM statement.
---------------------------------------------------------------------------------------
1298 MESSAGE Form field not big enough for item "num", subitem "array
element num"
CAUSE The value of the array element used in this item number
specified in the WRITE FORM statement will overflow the
declared type for the FORM.
ACTION Correct the range or length of the item specified in the FORM.
ACTION Correct the value of the array element for the item in the
WRITE FORM statement.
---------------------------------------------------------------------------------------
1299 MESSAGE String not big enough for form field for item "num".
CAUSE The string item used in the WRITE FORM statement cannot fit
into the FORM field.
ACTION Correct the string length in the FORM specification or correct
the string item in the WRITE FORM statement.
---------------------------------------------------------------------------------------
1340 MESSAGE NLS not installed.
CAUSE Native Language Support is not supported on your system.
ACTION You must log on as MANAGER.SYS and run the utility program,
LANGINST.PUB.SYS to install native languages on your system.
Please refer to the Native Language Programmer's Guide for more
information about installing native languages.
---------------------------------------------------------------------------------------
1341 MESSAGE 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 utility program,
LANGINST.PUB.SYS to add the language number to the
configuration file. Please refer to the Native Language
Programmer's Guide for more information about adding native
languages on your system.
---------------------------------------------------------------------------------------
1342 MESSAGE Illegal language specification for LEX.
CAUSE The language number specified in the LEX function is less than
-1.
ACTION Make sure that the language number is greater than or equal to
-1.
---------------------------------------------------------------------------------------
1356 MESSAGE Error in calculating new break limit for BREAK...WHEN...BY
statement.
CAUSE An arithmetic error overflow or underflow occurred while trying
to calculate the next multiple value to BREAK the report.
ACTION Verify the value specified on the BY clause. It is approaching
the limit of real for OPTION REAL, or approaching the limit of
decimal for OPTION DECIMAL.
---------------------------------------------------------------------------------------
1400 MESSAGE Uninitialized variable or array element used (!).
CAUSE When OPTION NOINIT is on, numeric variables are not initialized
to zero. Referencing the uninitialized variable will result in
a run time error in the interpreter.
ACTION Initialize the variable or array element or take out OPTION
NOINIT. OPTION INIT is the default.
---------------------------------------------------------------------------------------
1403 MESSAGE Undeclared variable "name" found in subunit "name".
CAUSE When OPTION DECLARE is on, implicit variable declaration is
illegal.
ACTION Either declare the variable or take out OPTION DECLARE. OPTION
NO DECLARE is the default.
---------------------------------------------------------------------------------------
1404 MESSAGE Single line function and current subunit have the same name.
CAUSE A single-line function and the current subunit have the same
name.
ACTION Change the single-line function name or the current function
name.
---------------------------------------------------------------------------------------
1411 MESSAGE Parameter to DATE$ must be >= -2.
CAUSE The native language number specified in the call to DATE$ is
less than -1.
ACTION Correct the native language number.
---------------------------------------------------------------------------------------
1413 MESSAGE Parameter to TIME$ must be >= -1.
CAUSE The native language number specified in the call to TIME$ is
less than -1.
ACTION Correct the native language number.
---------------------------------------------------------------------------------------
1414 MESSAGE Language parameter to UPC$ or LWC$ must be >= -1.
CAUSE The native language number specified in the call to UPC$ or
LWC$ is less than -1.
ACTION Correct the native language number in the second parameter.
---------------------------------------------------------------------------------------
1415 MESSAGE The form specified does not exist.
CAUSE The form name specified in the OPEN FORM statement does not
exist in the forms file. For example,
10 OPEN FORM "MAIN: form1.test"
The form name, MAIN, does not exist in "form1.test".
ACTION Check the form name and the form file name.
---------------------------------------------------------------------------------------
1416 MESSAGE Field data reformatting (finishing) failed. ( VPLUS
#"error-num" )
CAUSE An error occurred while processing specifications defined for
the final phase of fields editing. Please refer to Data Entry
and Forms Management System VPLUS/3000 for a detailed
description of the "error-num" returned in VFINISHFORM
intrinsic.
ACTION Please read the ACTION section regarding "error-num" returned
in VFINISHFORM intrinsic.
---------------------------------------------------------------------------------------
1417 MESSAGE CURSOR positioning failed. ( VPLUS #"error-num" )
CAUSE An error occurred in CURSOR positioning. Please refer to Data
Entry and Forms Management System VPLUS/3000 for a detailed
description of "error-num" returned in VPLACECURSOR intrinsic.
ACTION Please read the ACTION section regarding the "error-num"
returned in VPLACECURSOR intrinsic.
---------------------------------------------------------------------------------------
1418 MESSAGE Incompatible version of VPLUS installed.
CAUSE A current version of VPLUS is not installed.
ACTION Please consult the system manager.
---------------------------------------------------------------------------------------
1419 MESSAGE Field initialization data errors detected. ( VPLUS
#"error-num" )
CAUSE An error occurred in data initialization. Please refer to Data
Entry and Forms Management System VPLUS/3000 for a detailed
description of "error-num" returned in the VINITFORM intrinsic.
ACTION Please read the ACTION section regarding "error-num" returned
in the VINITFORM intrinsic.
---------------------------------------------------------------------------------------
1420 MESSAGE Field editing data errors detected. ( VPLUS #"error-num" )
CAUSE An error occurred in data editing. Please refer to Data Entry
and Forms Management System VPLUS/3000 for a detailed
description of "error-num" returned in the VFIELDEDITS
intrinsic.
ACTION Please read the ACTION section regarding "error-num" returned
in the VFIELDEDITS intrinsic.
---------------------------------------------------------------------------------------
1421 MESSAGE "error-num" (HPDERR "error-message").
CAUSE An error occurred in one of the HPDialog routines. Please
refer to the HPDialog Reference Manual for a detailed
description of "error-num" returned.
ACTION Please read the ACTION section regarding "error-num" returned
in HPDialog intrinsic routines.
---------------------------------------------------------------------------------------
1490 MESSAGE VERIFY command not allowed while program is running.
CAUSE A VERIFY command has been used while a program was suspended
(either by the PAUSE statement or by an unhandled error).
ACTION Issue a STOP command to stop your program.
---------------------------------------------------------------------------------------
1491 MESSAGE FORMATTED option to LIST not allowed while program is running.
CAUSE A LIST command with the FORMATTED option has been used while
the program was suspended (either by the PAUSE statement or by
an unhandled error).
ACTION Issue a STOP command to stop your program.
---------------------------------------------------------------------------------------
1492 MESSAGE XREF command not allowed while program is running.
CAUSE An XREF command has been used while the program was suspended
(either by the PAUSE statement, by hitting HALT key, or by an
unhandled error).
ACTION Issue a STOP command to stop your program.
---------------------------------------------------------------------------------------
1496 MESSAGE GETHEAP failure in library.
CAUSE This is a heap management problem. The system does not have
enough memory to run the program. The most probable case is
that the program is too big or too many variables are used in
the program.
ACTION Break the program up into smaller subprograms or use fewer
variables.
ACTION You need to do garbage collection by saving the program in
ASCII format and GET the program again in the interpreter.
---------------------------------------------------------------------------------------
1497 MESSAGE RTNHEAP failure in library.
CAUSE This is a heap management problem due to an internal problem.
ACTION Further investigation of this problem is required. Please
contact your Hewlett-Packard representative.
---------------------------------------------------------------------------------------
1498 MESSAGE Catastrophic program error.
CAUSE This is an internal problem.
ACTION Further investigation of this problem is required. Please
contact your Hewlett-Packard representative.
---------------------------------------------------------------------------------------
1499 MESSAGE Catastrophic error in heap management (unable to return heap
space).
CAUSE This is a heap management problem due to internal problems.
ACTION Further investigation of this problem is required. Please
contact your Hewlett-Packard representative.
---------------------------------------------------------------------------------------
1500 MESSAGE Internal consistency check #"num" failed. Report the problem
to HP.
CAUSE This is an internal problem.
ACTION Further investigation of this problem is required. Please
contact your Hewlett-Packard representative.
---------------------------------------------------------------------------------------
1502 MESSAGE WARNING "warning message".
CAUSE This warning message is generated by the SYSTEM statement or
":" as a system command. When the STATUS clause is specified
in the SYSTEM statement, you will not see the warning message.
ACTION None.
---------------------------------------------------------------------------------------
1503 MESSAGE WARNING 1503: Default STACKsize from program "prog-name".
CAUSE The stacksize specified in the SYSTEMRUN statement was less
than 512.
ACTION None. The default stacksize is used to run the program.
---------------------------------------------------------------------------------------
1504 MESSAGE WARNING 1504: Default DLsize from program "prog-name".
CAUSE The dlsize specified in the SYSTEMRUN statement was less than
zero.
ACTION None. The default dlsize is used to run the program.
---------------------------------------------------------------------------------------
1505 MESSAGE WARNING 1505: Default MAXDATA from program "prog-name".
CAUSE The maximum stack area value, MAXDATA, specified in the
SYSTEMRUN statement is less than or equal to zero.
ACTION None. The default configuration maximum is used to run the
program.
---------------------------------------------------------------------------------------
1506 MESSAGE WARNING 1506: DLsize rounded up to next 128 word multiple in
program "prog-name".
CAUSE The dlsize specified in the SYSTEMRUN statement was not a
multiple of 128.
ACTION None. The new dlsize value is used to run the program.
---------------------------------------------------------------------------------------
1507 MESSAGE WARNING 1507: MAXDATA decreased to configuration maximum in
program "prog-name".
CAUSE The maximum stack area value, MAXDATA, specified in the
SYSTEMRUN statement is larger than configured maximum for your
system.
ACTION None. MAXDATA is decreased to the configured maximum.
---------------------------------------------------------------------------------------
1508 MESSAGE WARNING 1508: MAXDATA increased to DLsize + globsize +
STACKsize in program "prog-name".
CAUSE The maximum stack area value, MAXDATA, specified in the
SYSTEMRUN statement is smaller than the minimum required to run
the program.
ACTION None. MAXDATA is increased to run the program.
---------------------------------------------------------------------------------------
1509 MESSAGE WARNING 1509: "parm-name" was specified more than once, last
value taken.
CAUSE A parameter to the SYSTEMRUN statement was specified more than
once.
ACTION None. Only the last value for that particular parameter is
used. The rest are ignored.
---------------------------------------------------------------------------------------
1511 MESSAGE WARNING 1511: Extra semicolon ignored.
CAUSE An extra delimiter has been entered in the SYSTEMRUN statement.
ACTION None. The extra semicolon is ignored.
---------------------------------------------------------------------------------------
1536 MESSAGE WARNING 1536: The spelling of that "string" was corrected
CAUSE This is a HELP command warning in the interpreter.
ACTION The spelling of the "string" entered in the HELP command is
corrected to the topic that is closest in spelling to the
"string" entered. Help information is provided on the
corrected topic.
---------------------------------------------------------------------------------------
1539 MESSAGE WARNING 1539: The spelling of that "string" was truncated
CAUSE This is a HELP command warning in the interpreter.
ACTION None.
---------------------------------------------------------------------------------------
1564 MESSAGE UnSAVEd source modifications will be lost. Do you really want
to EXIT? Y
CAUSE In the interpreter, the EXIT command was issued before a
program that was modified had been saved.
ACTION Save the program first or press the return key to exit without
saving the modifications.
---------------------------------------------------------------------------------------
1602 MESSAGE Modify command found at or past continuation character. Try
again
CAUSE A line was modified at or past the continuation character, "&".
ACTION Redo the modification.
---------------------------------------------------------------------------------------
1603 MESSAGE Line "linenum" is busy and cannot be changed.
CAUSE A "linenum" is busy if one of the following condition is true:
The line made a call which has not returned.
The line was interrupted with the halt key before it finished
executing.
ACTION Change or modify the line when it has finished execution.
---------------------------------------------------------------------------------------
1605 MESSAGE Line "linenum" secured and cannot be modified.
CAUSE The line number specified is secured and cannot be modified. A
secured line cannot be listed, only an asterisk is displayed.
ACTION Re-enter the line.
---------------------------------------------------------------------------------------
1608 MESSAGE TRACE VARS list can only be used in a program or when PAUSEd.
CAUSE A TRACE VARS list is not allowed in COMMAND mode.
ACTION Use TRACE VARS list in a program.
---------------------------------------------------------------------------------------
1733 MESSAGE The formal parameter space request for "proc_name",
"num_bytes", exceeds the maximum value available of
"limit_num_bytes" bytes.
CAUSE During processing of the EXTERNAL and INTRINSIC, the formal
parameter space for the definition exceeds the maximum value
allowable.
ACTION Reduce the number of formal parameters to the external, or
redefine the intrinsic file definition so that fewer parameters
are required.
---------------------------------------------------------------------------------------
1734 MESSAGE Unable to close intrinsic file "intr_file_name.
CAUSE An invalid file system value was returned when trying to close
the intrinsic file, "intr_file_name".
ACTION This is a file system problem that might be circumvented by
terminating all processes that reference the file.
---------------------------------------------------------------------------------------
1735 MESSAGE Error reading intrinsic file "intr_file_name".
CAUSE There is either invalid parameter information in the intrinsic
file for the parameter or a file system problem.
ACTION Rebuild the intrinsic file.
---------------------------------------------------------------------------------------
1736 MESSAGE Parameter #parm_num to procedure proc_name is invalid as a
formal parameter.
CAUSE The formal parameter obtained from the intrinsic file is not a
type that is supported in HP Business BASIC/XL. The types
supported in HP Business BASIC/XL are 16 bit integer, 32 bit
integer, 32 bit IEEE floating point, 64 bit IEEE floating
point, and string.
ACTION If possible, define the intrinsic as an external and use a
formal parameter that has the same size as that in the
intrinsic file.
---------------------------------------------------------------------------------------
1737 MESSAGE Error reading intrinsic file "intr_file_name" while processing
procedure information for proc_name.
CAUSE There is either invalid procedure information in the intrinsic
file or a file system problem.
ACTION Rebuild the intrinsic file.
---------------------------------------------------------------------------------------
1738 MESSAGE Type mismatch for parameter #parm_num, formal parameter type is
formal_parm_type while actual parameter type is
actual_parm_type.
CAUSE The type of the formal and actual parameters do not match.
ACTION Correct the actual parameter number parm_num so that it is
formal_parm_type type.
---------------------------------------------------------------------------------------