HP 3000 Manuals HP 3000 Manuals
Numbered Error Messages ( 1119 - 1240 )
---------------------------------------------------------------------------------------
1119 MESSAGE One of "S", "P", or "G" must come after "LIB=".
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1120 MESSAGE Missing keyword "NEW" after STDLIST specification.
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1121 MESSAGE Unrecognized keyword.
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1122 MESSAGE Out of system resources for program "{program_name}".
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1123 MESSAGE Program "{program_name}" does not exist.
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1124 MESSAGE Invalid program "{program_name}".
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1125 MESSAGE Entrypoint name does not exist or is invalid for program.
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1126 MESSAGE Increased MAXDATA is larger than configuration MAXDATA.
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1127 MESSAGE Hard load error for program "{program_name}".
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1128 MESSAGE Specified $STDIN could not be opened for program
"{program_name}".
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1129 MESSAGE Specified $STDLIST could not be opened for program
"{program_name}".
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1130 MESSAGE Could not activate new process for program "{program_name}".
CAUSE This occurs during execution of the :RUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1131 MESSAGE One of "BS", "CS", "DS", or "ES" must come after "PRI=".
CAUSE This occurs during execution of the MPE :RUN command or the HP
Business BASIC/XL SYSTEMRUN command.
ACTION See the appropriate operating system reference manual for more
information.
---------------------------------------------------------------------------------------
1132 MESSAGE In a job, the WAIT statement must specify a time limit.
CAUSE In your job, a WAIT statement does not specify a time limit.
ACTION Specify a value for the WAIT of less than 1.157920892373161E+74
seconds.
---------------------------------------------------------------------------------------
1133 MESSAGE The string specified is too long.
CAUSE 1. The string given in the COPTION TITLE="string" or COPTION
TITLESUB="string" command is too long.
2. The string given in the COPTION COPYRIGHT="string" command
is too long.
3. The string, Image$, given in a "PRINT USING Image$;Value"
statement is too long.
4. The set name is too long in: COPTION LOCALITY="set_name".
5. The total length of the string supplied to the SYSTEMRUN
command is too long.
ACTION 1. The TITLE string is limited to a length of 132.
2. The COPYRIGHT string is limited to a length of 268435455.
3. The maximum length of an IMAGE string is 500 characters.
4. The name is limited to 16 characters.
5. The string must be 500 characters or less. Make certain
that the string specified is within these limits.
---------------------------------------------------------------------------------------
1134 MESSAGE Only the words Yes, No, or Exit are allowed as input.
CAUSE You typed something other than Yes, Y, No, N, Exit, E or // in
response to the question "Do you want to see more on this topic
(Yes, No, Exit)?" while in HELP mode.
ACTION Answer as requested.
---------------------------------------------------------------------------------------
1135 MESSAGE SYSTEM with no parameters is not allowed from a batch job.
CAUSE The SYSTEM statement or the ":" command has been executed in
batch mode.
ACTION If you have a set of MPE commands to execute, recode the
commands to:
SYSTEM "command1"
SYSTEM "command2"
...
It may be that you have simply forgotten the "exit" command and
are running into the job's prompt character:
:job jobname,user.acct/passwd
:
:hpbb
10 print "Hi, Mom!"
run
:
:eoj
The ":" after the "run" command is read by HP Business BASIC/XL
as the HP Business BASIC/XL "SYSTEM" command. In this case,
insert an "exit" command between the"run" command and the
following ":"...
:job jobname,user.acct/passwd
:
:hpbb
10 print "Hi, Mom!"
run
exit
:
:eoj
---------------------------------------------------------------------------------------
1136 MESSAGE This BASIC program has not been PREPed with Process Handling
(PH) capability.
CAUSE The program tried to run another program (possibly with the
SYSTEMRUN command) without previously having been given the
Process Handling capability.
ACTION Re-PREP the program with CAP=PH.
---------------------------------------------------------------------------------------
1137 MESSAGE End of data on input device.
CAUSE 1. The interpreter has encountered the end of the command
input file. (The file BASCOM has been redirected.)
2. The program has read beyond the end of the file to which
BASIN has been redirected. The program is expecting more data
in the file than it should or the file doesn't contain as much
data as it should.
3. ":EOD" was typed in response to a request for input.
ACTION 1. End the command file with the "exit" command to terminate
the interpreter without an error.
2. Correct the data file or the program logic.
3. This is usually intentional.
---------------------------------------------------------------------------------------
1138 MESSAGE Error {error_number} in reading input.
CAUSE A file system error has occurred while reading input.
ACTION Look up the error_number in the description of the fcheck
intrinsic in the MPE XL Intrinsics Reference Manual for a text
description of the problem.
---------------------------------------------------------------------------------------
1139 MESSAGE INTEGER precision overflow.
CAUSE 1. An arithmetic operation involving INTEGER operands has
produced a result which is out of the range of an INTEGER
(possibly after implicit type conversion to make both arguments
have the same type).
2. A number that is out of the INTEGER range has been
converted to an INTEGER.
3. A value that is out of the range of INTEGER has been read
into an INTEGER variable.
4. The largest possible negative integer (-2,147,483,648) has
been made into a negative number. This is the one negative
integer value which cannot be represented as a positive integer
value.
ACTION 1, 2, 3. A (SHORT) REAL or (SHORT) DECIMAL may provide a
sufficiently larger range.
4. Assign the number to a type with a larger range (REAL or
DECIMAL), then make that negative.
---------------------------------------------------------------------------------------
1140 MESSAGE REAL precision overflow.
CAUSE 1. An arithmetic operation involving REAL operands has
produced a result which is out of the range of a REAL (possibly
after implicit type conversion to make both arguments have the
same type).
2. A number that is out of the range of REAL has been
converted to a REAL.
3. A value that is out of the range of REAL has been read into
a REAL.
ACTION A DECIMAL may provide a sufficiently larger range. (Be aware
that the precision of DECIMAL differs.)
---------------------------------------------------------------------------------------
1141 MESSAGE SHORT REAL precision overflow.
CAUSE 1. An arithmetic operation involving SHORT REAL operands has
produced a result which is out of the range of a SHORT REAL
(possibly after implicit type conversion to make both arguments
have the same type).
2. A number that is out of the range of SHORT REAL has been
converted to a SHORT REAL.
3. A value that is out of the range of SHORT REAL has been
read into a SHORT REAL.
4. The value to the EXP() function is out of the range
[-87.3366 .. 88.7228].
ACTION 1, 2, 3. Use a REAL (or DECIMAL) for the type of the target
variable instead of SHORT REAL. (Be aware that the precision of
these types is different.)
4. The argument to EXP must be within the indicated range.
---------------------------------------------------------------------------------------
1142 MESSAGE Can't write to file {file_name}.
CAUSE 1. The interpreter was unable to write to the program file
while trying to do a SAVE or RESAVE.
2. The interpreter was unable to mark the indicated file as
"run only" when executing the RUN ONLY statement.
ACTION Further investigation of this problem is required. Please
contact your Hewlett-Packard representative.
---------------------------------------------------------------------------------------
1143 MESSAGE Can't read from file.
CAUSE 1. The compiler was unable to read the file containing the
program to be compiled.
2. The interpreter was unable to complete a GET SUB statement
because of an error when reading from the file containing the
subunit to GET.
3. The interpreter was unable to complete a GET statement
because of an error when reading from the file containing the
program to GET.
4. The interpreter was unable to mark the indicated file as
"run only" when executing the RUN ONLY statement.
ACTION Further investigation of this problem is required. Please
contact your Hewlett-Packard representative.
---------------------------------------------------------------------------------------
1144 MESSAGE Arithmetic overflow on exponentiation.
CAUSE An arithmetic exception was encountered during the processing
of an arithmetic expression containing an exponentiation
operator. Values of variables or literals cause the numeric
value of the intermediate result to exceed the allowable range
of the intermediate type.
ACTION Rearrange the expression so that no overflow will occur during
the evaluation.
ACTION Trap values that you know will cause this condition.
ACTION Convert values so that an intermediate type with a larger range
of values is used.
---------------------------------------------------------------------------------------
1145 MESSAGE File version does not match current HPBB version.
CAUSE The file version on the BASIC SAVE file indicates that the file
was saved by an interpreter that is a later version than the
interpreter or compiler being used.
ACTION Save an ASCII version with the SAVE LIST command from the later
version and create a version with the older interpreter. The
same file can now be used with the older compiler.
---------------------------------------------------------------------------------------
1147 MESSAGE Invalid file type: Must be BASIC SAVE file.
CAUSE The source file specified as the input file for the compiler
does not have a BSVXL file code.
ACTION If you saved the file as an ASCII file, GET the file into the
interpreter and resave it using the command:
SAVE "filename"
"filename" must not have previously existed.
---------------------------------------------------------------------------------------
1150 MESSAGE Bad decimal numeric data found.
CAUSE Some recent input operation, a read from file or database has
resulted in a decimal value being read into a variable with a
decimal type that does not have the correct format. In other
words, the value in the file has been corrupted.
ACTION Correct the value in the file or database.
---------------------------------------------------------------------------------------
1151 MESSAGE Cannot RUN a program with OPTION SUBPROGRAM in effect.
CAUSE A program in the interpreter has been run with GLOBAL OPTION
SUBPROGRAM in the main of the program.
ACTION Remove the GLOBAL OPTION SUBPROGRAM to run the program in the
interpreter. You will probably have to add calls to the
procedures and functions in the current program in the
interpreter, if you have not already done so.
ACTION If there are only procedures or functions in the current
program in the interpreter ( this means that there are no
executable statements in the main of the current program ), you
will have to compile the program and put it into an executable
library. You can use a program with the appropriate calls to
your procedures or functions from the interpreter to test your
program.
---------------------------------------------------------------------------------------
1152 MESSAGE Irrecoverable error encountered.
CAUSE The interpreter cannot recover to a consistent internal state
that guarantees that all user information is not corrupted.
You will usually see this message as the interpreter is
aborting and just prior to a stack trace indicating the
location in the code that the abort occurred and the preceding
internal procedure calls made by the interpreter.
ACTION Please copy the information that is on your screen and try to
describe the steps that immediately preceded the problem.
Submit this report to your System Administrator to forward to
the HP Service Engineer.
---------------------------------------------------------------------------------------
1153 MESSAGE WARNING 1153: Procedure name "procedure_name" is too long.
CAUSE The procedure name, function name or the alias specified in an
INTRINSIC or EXTERNAL statement or the name of the intrinsic in
the intrinsic file exceeds the maximum length of 60 characters.
This is an error rather than a warning, since processing of the
statement is interrupted and the program cannot be run. The
name returned from the intrinsic file may be displayed as
"procedure name". Note that because of the definition of the
intrinsic mechanism, the name to be called may not be the same
as either the name in the INTRINSIC statement or the specified
alias in the ALIAS clause.
ACTION Shorten the procedure name, function name or the alias name in
the INTRINSIC or EXTERNAL statement or be certain that the name
of the intrinsic in the intrinsic file is within the
appropriate bounds.
---------------------------------------------------------------------------------------
1154 MESSAGE Not enough memory available.
CAUSE Current operation has exhausted the amount of space allocated
to hold information in the interpreter. Since HP Business
BASIC does not do garbage collection of its previously used
space, you may have to do this.
ACTION If you obtained this message while entering a program in the
interpreter, try to save the current version as an ASCII
program file using the command:
SAVE LIST "filename".
If this is successful, then do a GET "filename"
If you obtained this message trying to run a program, then the
run-time data structures used to store the values of variables
could not be allocated because of space constraints. Try to
reduce the size of large arrays or eliminate unnecessary or
unused variables.
---------------------------------------------------------------------------------------
1155 MESSAGE Unable to open intrinsic file "intr_filename".
CAUSE intr_filename does not exist as specified or it is being
accessed exclusively.
ACTION Check to be certain that the file exists or that it is not
being accessed exclusively.
---------------------------------------------------------------------------------------
1157 MESSAGE Procedure "procedure" is not in the intrinsic file.
CAUSE Interpreter: The name or alias specified in the INTRINSIC
statement was not found in the intrinsic file prior to running
that main, program or function.
Compiler: The name or alias specified in the INTRINSIC
statement in the intrinsic file was not found prior to
compiling that main, program or function.
ACTION Check the name of the intrinsic file to be certain that you are
using the one that contains the correct name or alias. If this
does not work, change the name or alias to conform to the name
in the intrinsic file.
---------------------------------------------------------------------------------------
1158 MESSAGE The procedure "procedure_name" is being used where a function
is needed.
CAUSE A procedure is being called when a return value is expected,
either as a function call or with the use of the FNCALL
keyword.
ACTION Either change the procedure to a function or call the procedure
as a procedure.
---------------------------------------------------------------------------------------
1159 MESSAGE Call to procedure "procedure_name" failed.
CAUSE The call to the HP Business BASIC/XL built-in function TASKID
failed. The "procedure_name" is PROCINFO, the MPE intrinsic
called to obtain the information.
ACTION The most likely cause of this is an operating system problem.
The problem is not an HP Business BASIC/XL problem.
---------------------------------------------------------------------------------------
1167 MESSAGE Procedure "procedure_name" cannot be called as a function.
CAUSE The intrinsic file indicates that procedure_name is a
procedure, but it has been defined in the INTRINSIC statement
as having a return value.
ACTION Change the INTRINSIC definition for the procedure by removing
the type declaration for the return value.
---------------------------------------------------------------------------------------
1169 MESSAGE Command "_" ANYPARM call allowed only in PAUSEd executing
subunit with _"procedure_name" call.
CAUSE An ANYPARM external before execution of the main, procedure, or
function that contains the ANYPARM call was called before the
interpreter has scanned that routine to initialize the internal
structures required for the call.
ACTION Add a PAUSE statement at the beginning of the main, procedure,
or function that contains the call and execute the program. A
call from the interpreter can be made when the program executes
the PAUSE statement and returns control to the interpreter.
---------------------------------------------------------------------------------------
1177 MESSAGE Value for BYTE parameter # "parameter_number" exceeds range for
BYTE type.
CAUSE A BYTE parameter to an external exceeded the range of
[-256,255].
ACTION Check the value of the actual parameter to be certain that it
is within the specified range. Note that BYTE types are not
sign extended.
---------------------------------------------------------------------------------------
1180 MESSAGE Parameters out of range for the function.
CAUSE The parameters to the DAT3000$ built-in function must satisfy
the following three conditions:
1. The first parameter must be greater than or equal to one.
2. The second parameter must be less than or equal to 27.
3. The first parameter must be less than or equal to the
second parameter.
ACTION Be certain that the parameters to the DAT3000$ satisfy the
above conditions before calling the built-in function.
---------------------------------------------------------------------------------------
1181 MESSAGE Error in accessing the HELP message file.
CAUSE The interpreter was unable to open the catalog HPBBHELP.PUB.SYS
following the HELP command.
ACTION Be certain that the file HPBBHELP.PUB.SYS is present on your
system and that no one is accessing the file exclusively.
---------------------------------------------------------------------------------------
1182 MESSAGE Call to "procedure_name" has "number_formal" parameter(s);
declaration has "number_actual" parameters.
CAUSE The number of formal parameters defined in the EXTERNAL
statement or in the intrinsic file does not match the number of
actual parameters supplied for the call from the program.
ACTION Correct either the definition in the EXTERNAL statement or the
call so that the number of parameters is the same.
---------------------------------------------------------------------------------------
1183 MESSAGE Too few parameters, or missing parameter in call to
"procedure_name".
CAUSE A call to a procedure or function does not have the correct
number of actual parameters that correspond to the number of
formal parameters declared in the procedure or function header.
ACTION Correct the call to the procedure or function so that the
number of actual parameters corresponds to the number of formal
parameters defined.
---------------------------------------------------------------------------------------
1186 MESSAGE Interpreter BUILD file failure: please PURGE temp files
prefixed BBTEMP.
CAUSE Certain HP Business BASIC/XL statements and commands create a
file in the temporary file space to store information. HP
Business BASIC/XL uses the "BBTEMP" prefix as the first six
characters in the temporary filename. If you have created a
large number of files with this prefix, HP Business BASIC/XL
will be unable to process the information required.
ACTION Check the temporary file space using the command, ":listftemp"
to confirm that there are too many files with the prefix
"BBTEMP". Modify your program so that you use filenames with a
different prefix and purge those unused files prefixed with
"BBTEMP" that are in the temporary file space.
---------------------------------------------------------------------------------------
1187 MESSAGE Interpreter BUILD file failure: please check whether disk space
full.
CAUSE Certain HP Business BASIC/XL statements and commands create a
file in the temporary file space to store information. In this
case, HP Business BASIC/XL was unable to build the required
file.
ACTION Check with your System Administrator concerning the system's
available disk space. You may have also reached your account
or group disk space limits.
---------------------------------------------------------------------------------------
1189 MESSAGE FNCALL of a subprogram is not allowed.
CAUSE The name specified as a parameter to FNCALL is the name of a
procedure in the current program.
ACTION Call the procedure using the CALL statement.
---------------------------------------------------------------------------------------
1190 MESSAGE ROUND argument cannot be power rounded in the range of
decimals.
CAUSE The argument to be rounded is converted to a decimal value and
a value to be added to that value for the round is determined.
Overflow on the addition causes this error to be generated.
ACTION Check values before rounding so that overflow does not occur
during the rounding operation.
---------------------------------------------------------------------------------------
1191 MESSAGE DROUND argument cannot be digit rounded in the range of
decimals.
CAUSE The argument to be rounded is converted to a decimal value and
a value to be added to that value for the round is determined.
Overflow on the addition causes this error to be generated.
ACTION Check values before rounding so that overflow does not occur
during the rounding operation.
---------------------------------------------------------------------------------------
1192 MESSAGE Matrix is singular, cannot be inverted.
CAUSE A matrix cannot be inverted because the current values of the
individual elements are such that the matrix is singular.
ACTION Check for singularity prior to trying to invert the matrix.
---------------------------------------------------------------------------------------
1194 MESSAGE Bad data in form field for item "form_item_number".
CAUSE One of the following errors occurred when trying to assign the
value of a field to a scalar or an element of the array
specified in "form_item_number". This happened when a VPLUS
form was read with the READ FORM statement.
1. The length of a numeric value in a form field exceeded the
maximum length of a numeric literal.
2. There were illegal characters in the numeric literal in the
form field.
3. (Scalars only) The conversion of the ASCII numeric literal
in the form field to a numeric value of the appropriate type
failed.
ACTION Use internal error handling using ON ERROR statements to trap
these errors and specify recovery procedures.
---------------------------------------------------------------------------------------
1195 MESSAGE String not big enough for form field for item "form_item",
subitem "array_element_number".
CAUSE A VPLUS form was read with the READ FORM statement and the
conversion of the ASCII numeric literal in the form field to a
numeric value of the appropriate type failed. The resulting
value would have been assigned to the "array_element_number" of
the array which is number "form_item" in list of READ FORM form
items.
ACTION Use internal error handling using ON ERROR statements to trap
this error and specify recovery procedures.
---------------------------------------------------------------------------------------
1196 MESSAGE Invalid file parameters specified in user's :FILE LISTF
command.
CAUSE An error was detected in the LISTF file equation required to
build the workfile for the CAT command.
ACTION Check the LISTF file equation by using the command,
":LISTEQ"
from the interpreter. The LISTF file equation is required to
be in the following format:
FILE LISTF;REC=-68,64,F,ASCII;DISC=nnnnn,32;NOCCTL;TEMP
where nnnnn is some positive integer value reflecting the
maximum estimated number of files that will be processed when
using the CAT command. The FILE command can be set from within
the interpreter using the SYSTEM command.
---------------------------------------------------------------------------------------
1197 MESSAGE No Form file specified now or in the past.
CAUSE A form was opened without first opening a form file.
ACTION Add the name of the form file containing the desired form to
the OPEN FORM statement.
---------------------------------------------------------------------------------------
1198 MESSAGE No Form open.
CAUSE A CLEAR FORM statement for a VPLUS form was executed when no
form was open.
ACTION Add code to open the form prior to trying to clear it.
---------------------------------------------------------------------------------------
1199 MESSAGE Account or user MAXPRI= does not permit this value for PRI=.
CAUSE The account or user priority is not set as high as that
requested in the PRI clause of the SYSTEMRUN command.
ACTION Use a lower priority for the PRI clause or have your System
Administrator raise your MAXPRI value.
---------------------------------------------------------------------------------------
1203 MESSAGE Line number "line_number" does not exist.
CAUSE "line_number" specified in a command, for example,
LIST 1+10
where line number 1 is not a line in the current program.
ACTION Re-enter the command using a line number that is present in the
current program.
---------------------------------------------------------------------------------------
1204 MESSAGE Label not found in current program unit.
CAUSE The label specified in a command, for example,
LIST Label1
where Label1 is not a label on a line in the current program.
ACTION Re-enter the command using a valid label.
---------------------------------------------------------------------------------------
1211 MESSAGE Command-only statements are not allowed in a COMMAND statement.
CAUSE In the interpreter, entries can be either a command, a
statement in a program, or both. Those keywords that can only
be commands, such as LIST, cannot occur in the quoted string
literal or as the value of the string variable following the
keyword COMMAND.
ACTION Remove the command from the quoted string literal or assign a
value to the string variable that does not include the command.
---------------------------------------------------------------------------------------
1212 MESSAGE A command is not allowed here; it must be a program line.
MODIFY only accepts lines which begin with a line number. (
message #1606 )
CAUSE Use of the MODIFY command was used to change a line to a
command such as LIST or RUN.
ACTION A modified line must always begin with a line number. Make
sure that there is a line number.
---------------------------------------------------------------------------------------
1216 MESSAGE File record size too small for program line.
CAUSE The record size of the ASCII file to which the listing is being
directed at the time of a LIST, FIND, MODIFY, or CHANGE is less
than the minimum size of 22 characters.
ACTION Increase the record size of the file to greater than 22
characters.
---------------------------------------------------------------------------------------
1217 MESSAGE Not enough room to make copy or move between lines
"line_number_1" and "line_number_2".
CAUSE COPY or MOVE failed because the number of available lines
between "line_number_1" and "line_number_2" is not sufficient.
ACTION Neither MOVE nor COPY will renumber lines so that they will
automatically fit in the designated target area. If you want
to move or copy lines and the range is not sufficient, use
RENUMBER to renumber the line immediately following the
location to which the lines are targeted, "line_number_2".
Renumber to a high enough number to allow sufficient space.
---------------------------------------------------------------------------------------
1218 MESSAGE Cannot MOVE lines into a subunit which is moving.
CAUSE The actual message is: Lines are not contained in the same
subunit. During editing, an attempt is made to MOVE at least
one entire procedure or function and part of an additional one.
ACTION MOVE only entire internal procedures and functions.
---------------------------------------------------------------------------------------
1219 MESSAGE Lines "line_number_1"/"line_number_2" copied but then deleted
because of the error.
CAUSE A syntax error encountered during partially completed COPY of
lines.
ACTION Correct the syntax error and COPY again.
---------------------------------------------------------------------------------------
1220 MESSAGE Destination line, "line_number", lies within source range,
"low_range"/"high_range".
CAUSE A range of lines was moved or copied, and the destination of
one of the lines is a line number that would be in the range
["low_range","high_range"].
ACTION It is possible to obtain the same results using two moves:
1. MOVE the lines to another destination where they fit.
2. Delete the original lines.
3. MOVE the lines to the desired destination.
---------------------------------------------------------------------------------------
1221 MESSAGE Program not running.
CAUSE The CONTINUE command was entered when a program is not paused
or halted.
ACTION Be certain that the program is paused or halted before entering
CONTINUE. This can be done by entering the command: "LIST *"
to display the current line.
---------------------------------------------------------------------------------------
1227 MESSAGE Current line is not defined.
CAUSE The command: "LIST *" was used when no program is running in
the interpreter.
ACTION The "LIST *" command will only list the current line when a
program is paused or halted in the interpreter.
---------------------------------------------------------------------------------------
1228 MESSAGE Command is too long.
CAUSE The quoted string literal or the value of the string expression
following COMMAND exceeds the maximum allowed value of 500
characters.
ACTION Shorten the length of the string literal or the value of the
string expression.
---------------------------------------------------------------------------------------
1229 MESSAGE Program lines are not allowed in a COMMAND statement.
CAUSE The quoted string literal or the value of the string expression
following COMMAND cannot begin with a numeric value.
ACTION Change the string so that it begins with a character in the set
[a..z] or [A..Z].
---------------------------------------------------------------------------------------
1230 MESSAGE Tried to delete current line while there are still line ranges
left.
CAUSE A program that deletes the current line has been run. For
example:
10 DELETE 10,20
20 PRINT "line to delete"
ACTION Do not include the current line in the range of lines to be
deleted.
---------------------------------------------------------------------------------------
1231 MESSAGE Not enough data space available to start GET SUB.
CAUSE The total amount of space available for the current program has
been exhausted. You may be able to do your own garbage
collection to condense space.
ACTION Since you are trying to do a GET SUB from a BASIC SAVE
formatted file, you should do garbage collection on:
1. The original current program file if it is stored in the
BASIC SAVE file format.
2. All previous files involved in GET SUB commands or
statements from which procedures or functions that are part of
the current program at the time of the error were obtained. In
order to do the actual garbage collection, you will need to do
a GET, SAVE LIST, GET, and RESAVE sequence for each of the
above files:
GET "original_filename"
SAVE LIST "new_filename"
GET "new_filename"
RESAVE "original_filename"
You can then PURGE "new_filename" and repeat the sequence with
the next file.
ACTION If you obtained this message while running a program, then the
run-time data structures used to store the values of variables
might not be allocatable because of space constraints. Try to
reduce the size of large arrays or eliminate unnecessary or
unused variables.
---------------------------------------------------------------------------------------
1232 MESSAGE Could not renumber subunit during GET SUB. Last subunit
removed.
CAUSE Renumbering the procedure or function to be part of the current
program would result in a line number greater than the maximum
line number, 999999.
ACTION Use RENUMBER to increase the number of available line numbers
in the current program before the GET SUB statement or command.
Use a different first line number to begin the numbering of the
new function or procedure in the current program.
Use a smaller line increment in the GET SUB statement or
command so that the entire procedure or function fits in the
current program.
---------------------------------------------------------------------------------------
1233 MESSAGE Could not add subunit name during GET SUB. Last subunit
removed.
CAUSE The interpreter was unable to obtain sufficient space to add
the name of a procedure or function during execution of a GET
SUB command or statement.
ACTION Take action similar to that recommended for error number 1231.
---------------------------------------------------------------------------------------
1234 MESSAGE Renumbering lines invalid for GET SUB statement.
CAUSE A line number in the current program conflicts with one of the
line numbers for the procedure or function to be read into the
interpreter from the BASIC SAVE file specified in the GET SUB
statement. Either the new line number already exists or a line
in the current program would now be included in the new
procedure or function.
ACTION Be certain that the entire range of lines into which the new
procedure is to be read has no program lines prior to execution
of the GET SUB statement or command.
---------------------------------------------------------------------------------------
1235 MESSAGE First subunit specified in GET SUB statement does not exist.
CAUSE Either no subunit number exists or the range of values that
supposedly corresponds to the subunit numbers does not exist in
the BASIC SAVE file for the GET SUB statement or command.
ACTION The numbering of the procedures and functions in the specified
BASIC SAVE file begins with one and each subsequent procedure
or function is one greater. Be certain that the value that you
are using corresponds to this numbering system.
---------------------------------------------------------------------------------------
1236 MESSAGE GET SUB statement requires a BASIC SAVE file.
CAUSE The file code for the file specified in the GET SUB command or
statement does not have a BSVXL file code.
ACTION GET the file with the subunit into the interpreter, PURGE the
file and use the SAVE command to save a new version of the file
with the correct file code.
---------------------------------------------------------------------------------------
1238 MESSAGE GET SUB subunit specifications must be greater than 0.
CAUSE Either no subunit exists in the GETSUB file or the subunit
number specified is less than or equal to zero.
ACTION The numbering of the procedures and functions in the specified
BASIC SAVE file begins with one and each subsequent procedure
or function is one greater. Be certain that the value that you
are using corresponds to this numbering system.
---------------------------------------------------------------------------------------
1240 MESSAGE Line range "line_range" contains a nonexistent line reference.
CAUSE An attempt was made to save or resave a portion of the current
program that contains a main and at least one procedure or
multi-line function when the "line_range" of the line ranges
specified has no program lines and the file to which the
current program is being saved is a BASIC SAVE file.
ACTION SAVE or RESAVE the information to an ASCII file.
ACTION Use only line ranges which contain at lease one line when using
the line range option of the SAVE or RESAVE command when
writing to a BASIC SAVE file.
---------------------------------------------------------------------------------------