HP 3000 Manuals HP 3000 Manuals
Appendix A Error Messages
Numbered Error Messages ( 2 - 216 )
---------------------------------------------------------------------------------------
2 MESSAGE 1. Memory overflow.
2. Not enough data space available for the local variables.
CAUSE The system does not have enough memory to run the program.
Most probable case is that the program is too big or too many
variables are used in the program. Message 1 comes out at run
time and message 2 comes out as a verify error.
ACTION Break the program up into smaller subprograms or use fewer
variables.
---------------------------------------------------------------------------------------
3 MESSAGE 1. Line not found, or not in current program unit.
2. Renumbering label specified is not in the current program
unit.
3. Execution line specified is not in the current program unit.
CAUSE 1. The line referenced is not found within the program unit
being executed.
2. This occurs in the interpreter only. The line label
specified as the first line to be read from an ASCII program
file for a GET, LINK, or MERGE does not exist in the file.
3. Interpreter only: The parameter to the RUN command
specifying the line on which execution is to begin is not
within the current program. For example, if the current
program has no lines then RUN; 10 will generate this error.
ACTION Be certain that the line number specified exists in the current
program.
---------------------------------------------------------------------------------------
4 MESSAGE RETURN without GOSUB.
CAUSE A RETURN statement is encountered without a corresponding GOSUB
statement.
ACTION Delete the statement or check the program for errors.
---------------------------------------------------------------------------------------
5 MESSAGE Encountered end of function before RETURN was executed.
CAUSE A user-defined multi-line function does not end in a RETURN
statement.
ACTION Add a RETURN statement.
---------------------------------------------------------------------------------------
6 MESSAGE 1. FOR without NEXT.
2. No FOR loop active for this NEXT.
3. Illegal imbedded FOR loop variable.
CAUSE 1. Interpreter message only; a FOR loop is not ended by a
corresponding NEXT. This usually happen in an embedded FOR
loop.
2. In the interpreter, error occurs because execution of a
NEXT in a FOR..NEXT construct does not have a corresponding
active FOR. The situation occurs when a branch is made to the
middle of a FOR..NEXT construct without execution of the
corresponding FOR statement. This message also appears in
compiled programs with COPTION RANGE CHECKING selected.
This error occurs because execution of a NEXT in a FOR..NEXT
construct does not have a corresponding active FOR. The
situation occurs when a branch is made to the middle of a
FOR..NEXT construct without execution of the corresponding FOR
statement.
3. The same variable is being used as a FOR loop control
variable for an outer and inner FOR loop in a nested FOR loop
in one of the following statements: READ, READ FORM, WRITE
FORM, PRINT DISPLAY, PRINT USING, INPUT, or READ #"fnum".
For example, 10 READ (FOR I=1 TO 3,(FOR I=4 TO 7,A(I,I)))
ACTION Check program for FOR loop errors, particularly branching into
the middle of FOR loop. Each of the loop control variables in
a nested FOR construct in one of the above statements must have
a distinct name.
---------------------------------------------------------------------------------------
7 MESSAGE 1. Attempt to call an undefined subprogram or function.
2. Subunit "subunit_name" does not exist.
3. Attempt to FNCALL a non-existent function.
CAUSE 1. The function name in a CALL statement is not defined in the
current program or an EXTERNAL statement is missing.
2. The procedure or function in the current program named
"subunit_name" does not exist. "subunit_name" could have been
specified in any statement that requires a line range, for
example, LIST, TRACE statements, CHANGE, and VERIFY.
3. The FNCALL was made to an external function that does not
exist.
ACTION Define the function or subunit.
---------------------------------------------------------------------------------------
8 MESSAGE 1. Improper parameter matching of parameter #N.
2. Improper parameter matching with VAR.
CAUSE The formal parameter defined in the EXTERNAL statement or
retrieved from the intrinsic file does not match the type of
the corresponding actual parameter in the parameter list for
the call. Depending on the cause, one of the two above
messages will appear; N is the parameter number and VAR is the
name of the formal parameter that is mis-matched.
ACTION Replace the actual parameter in the call to the external with a
variable of the correct type. The type of the variable can
also be coerced with one of the built-in functions: REAL,
SREAL, INTEGER, SINTEGER, or DECIMAL. Note that doing so will
result in an expression being passed as the actual parameter.
Expressions are evaluated at the time of the call and the value
is assigned to a temporary cell. The temporary cell becomes
the actual parameter.
---------------------------------------------------------------------------------------
9 MESSAGE Improper number of parameters.
CAUSE The number of parameters passed to a function in a CALL
statement does not match the number of parameters specified in
the function itself.
ACTION Check the function definition and add or delete the appropriate
parameter.
---------------------------------------------------------------------------------------
12 MESSAGE Attempt to redeclare a variable, VAR, in line N.
CAUSE An already declared variable VAR is being redeclared in line N.
ACTION Only declare the variable once.
---------------------------------------------------------------------------------------
15 MESSAGE Invalid bounds on array dimension or string length.
CAUSE Strings or arrays are declared with an invalid bound. E.g.
DIM A$[0]
ACTION Change the declaration to use a valid bound.
---------------------------------------------------------------------------------------
16 MESSAGE Improper array dimensions.
CAUSE 1. An array is defined with an invalid dimension or defined
with more than 6 dimensions. For example, DIM A(-1).
2. A MAT statement detected that one of the operands is not
properly dimensioned for that particular matrix operation.
Example : MAT A = B * C where B is not dimensioned the same as
C.
ACTION Redefine the array with a valid dimension.
---------------------------------------------------------------------------------------
17 MESSAGE Subscript out of range.
CAUSE When an array element is referenced, the subscript is outside
the range of the array. For example, accessing element 3 of a
2-element array.
ACTION Check subscript for correct range.
---------------------------------------------------------------------------------------
18 MESSAGE 1. Substring out of range or substring too long.
2. Input string too long.
CAUSE 1. This error is most often caused by incompatible string or
substring assignment. For example, assigning a string to
another string of shorter length, or referencing a string
beyond its actual length.
2. Trying to input A string that is longer than the max length
of the receiving variable has been input.
ACTION 1. Make sure the string being referenced is within its actual
and maximum length.
2. Input a shorter string, or use substring input.
---------------------------------------------------------------------------------------
19 MESSAGE 1. Improper value in program statement.
2. Computed GOTO/GOSUB expression out of range.
CAUSE Message 1 : An improper value is detected when evaluating
binary built-in functions BITLR and BITRL.
Message 2 : An improper value is detected when executing the
ON X GOTO/GOSUB statement. For example, X contains a value
that is outside of its intended range.
ACTION Check program for correct value.
---------------------------------------------------------------------------------------
20 MESSAGE 1. SHORT INTEGER precision overflow.
2. Numeric expression for CAUSE ERROR must be in SHORT INTEGER
range.
CAUSE 1. Most often caused by assigning to a short integer an
expression whose value is beyond a short integer (16 bit) range
of (-32768, 32767).
2. The value supplied in a CAUSE ERROR statement is beyond the
range of a short integer.
ACTION Check the expression for accuracy or use another data type.
---------------------------------------------------------------------------------------
21 MESSAGE SHORT DECIMAL precision overflow.
CAUSE Most often caused by assigning an expression whose value is
beyond the range of a legal short decimal.
ACTION Check the expression for accuracy or use another data type.
---------------------------------------------------------------------------------------
22 MESSAGE DECIMAL precision overflow.
CAUSE Most often caused by assigning an expression whose value is
beyond the range of a decimal quantity.
ACTION Check the expression for accuracy or use another data type.
---------------------------------------------------------------------------------------
24 MESSAGE TAN(N*PI/2) when N is odd.
CAUSE The argument of a TAN function will produce a result of
infinity.
ACTION Check argument for accuracy.
---------------------------------------------------------------------------------------
25 MESSAGE Argument of ASN or ACS is >1 in absolute value.
CAUSE The call to the mathematical functions ARC SINE and ARC COSINE
contains an invalid argument.
ACTION Check argument for accuracy.
---------------------------------------------------------------------------------------
26 MESSAGE Zero to negative power
CAUSE A zero raised to a negative power results in infinity, an
invalid quantity.
ACTION Check the expression for accuracy.
---------------------------------------------------------------------------------------
27 MESSAGE Negative to nonintegral power
CAUSE A negative number raised to a nonintegral power will result in
a complex number which is not supported by Business BASIC.
ACTION Check the expression for accuracy.
---------------------------------------------------------------------------------------
28 MESSAGE Argument of LOG or LGT is negative.
CAUSE The call to the log functions contains an invalid argument, in
this case a negative number.
ACTION Check the argument for accuracy.
---------------------------------------------------------------------------------------
29 MESSAGE Argument of LOG or LGT is 0.
CAUSE The call to the log functions contains an invalid argument, in
this case a zero quantity.
ACTION Check the argument for accuracy.
---------------------------------------------------------------------------------------
30 MESSAGE Argument of SQR is negative.
CAUSE The square root function SQR is called with a negative
argument.
ACTION Check the argument for accuracy.
---------------------------------------------------------------------------------------
31 MESSAGE Division by zero, or modulo zero.
CAUSE A division by zero is detected during the evaluation of an
expression.
ACTION Check the expression for accuracy.
---------------------------------------------------------------------------------------
32 MESSAGE String not a valid number, or string where numeric data
required.
CAUSE The string parameter to the VAL function does not contain a
number.
ACTION Check parameters for accuracy.
---------------------------------------------------------------------------------------
33 MESSAGE 1. Bad argument to the NUM function.
2. RPT$ number of repetitions must be zero or greater.
3. Repeated string would exceed the maximum string length.
CAUSE Message 1 : The string parameter to the NUM function contains
an invalid character.
Message 2 : The repeat count parameter of the RPT$ function
contains an invalid count; probably negative.
Message 3 : The result length of the repeated string exceeds
the maximum limit for a string variable.
ACTION Check arguments for accuracy.
---------------------------------------------------------------------------------------
34 MESSAGE Line referenced is not an IMAGE statement
CAUSE The line referenced by a PRINT USING statement is not an IMAGE
statement.
ACTION Add the required IMAGE statement.
---------------------------------------------------------------------------------------
35 MESSAGE Improper IMAGE format specification, character N.
CAUSE Character N of the IMAGE statement contains an invalid format
specification.
ACTION Modify the wrong format with a valid specification.
---------------------------------------------------------------------------------------
36 MESSAGE Out of data.
CAUSE The READ statement tries to read more than what is contained in
the DATA statements.
ACTION Use RESTORE statement to reuse data or add more data to the
DATA statements.
---------------------------------------------------------------------------------------
40 MESSAGE 1. Improper REPLACE or DELETE.
2. RENUMBER cannot alter line sequence.
CAUSE 1. Because they affect the structure of the program, some
statements may not be deleted or replaced individually. These
are the SUB statement and the DEF FN statement. An attempt to
replace or delete either of these statements will result in
this error.
2. The sequence of lines in a program was altered by a TO
clause which has a value outside the original range of values
to be renumbered.
ACTION 1. Do not delete or replace the line, or delete the whole
sub-procedure or function.
2. Be certain that the renumbering is done so that the
sequence of statements in the current program is not altered.
---------------------------------------------------------------------------------------
42 MESSAGE Attempt to replace or delete busy line or subprogram.
CAUSE A line or subprogram was deleted or replaced in the middle of
its execution.
ACTION Do not delete this line or subprogram until the end of its
execution.
---------------------------------------------------------------------------------------
43 MESSAGE Matrix not square.
CAUSE The matrix passed to the built-in functions INV (matrix
inversion) and DET (determinant) is not a square matrix.
ACTION Redefine the matrix to make it square.
---------------------------------------------------------------------------------------
44 MESSAGE Illegal operand in matrix transposition or matrix
multiplication.
CAUSE The operands passed to the built-in matrix functions TRN
(transpose) and MUL (multiply) are not declared correctly, so
the operation cannot be performed.
ACTION Redefine the operands.
---------------------------------------------------------------------------------------
47 MESSAGE 1. VAR COMMON area does not exist.
2. Dimension or type of COMMON variable in line N doesn't match
main.
3. Variable list in line N exceeds the COMMON declaration in
main.
4. VAR COMMON area is larger than defined in the original
program.
5. COMMON declaration in line N doesn't match the original
program.
6. VAR COMMON area has more variables than the original
program.
CAUSE All messages in this error number concern with errors with
COMMON declarations; N is a line number where the error occurs
and VAR is the name of the COMMON area.
1. A subprogram contains a named COMMON that does not exist in
the main program.
2. A COMMON in a subprogram contains variables that do not
match that declared in the main program.
3. A COMMON in a sub-program contains more variables than is
declared in the main program.
Messages four through six only occur when executing a GET in
the interpreter.
4. A program that is brought into the interpreter by the GET
command contains a COMMON that is larger than the program that
contains the GET command.
5. A program that is brought into the interpreter by the GET
command contains variables in COMMON that do not match those in
the program that contains the GET command.
6. A program that is brought into the interpreter by the GET
command contains more variables in a COMMON area than is
declared in the program that contains the GET command.
ACTION Check COMMON or its variables for consistency with subprogram
or main.
---------------------------------------------------------------------------------------
48 MESSAGE Recursion not allowed in single line functions.
CAUSE A single line function is calling itself.
ACTION Redefine the function to eliminate recursion.
---------------------------------------------------------------------------------------
49 MESSAGE Subunit specified in ON declaration not found.
CAUSE The subunit in an ON...CALL...statement does not exist.
ACTION Provide the missing subunit or call another subunit.
---------------------------------------------------------------------------------------
50 MESSAGE File number out of range.
CAUSE The file number in an ASSIGN # statement exceeds the range of a
positive, non-zero 16 bit integer; (1, 32767).
ACTION Change the file number.
---------------------------------------------------------------------------------------
51 MESSAGE The file is not currently open.
CAUSE A file was accessed without first being opened.
ACTION Open the file before accessing it.
---------------------------------------------------------------------------------------
52 MESSAGE Improper group.account specifier.
CAUSE The group or account does not exist when a fully qualified file
name is used in a file reference.
ACTION Use a correct group.account specifier for the file.
---------------------------------------------------------------------------------------
53 MESSAGE Improper file name.
CAUSE The file name used either contains characters that are illegal
in file names or the file name is longer than the legal length.
ACTION Change the file name.
---------------------------------------------------------------------------------------
54 MESSAGE 1. Duplicate file name.
2. File already exists; use RESAVE to overwrite.
CAUSE 1. A file that already exists was created.
2. The current program was saved to a file that already
exists.
ACTION 1. Use a different file name or purge the existing file.
2. Use the RESAVE command or SAVE into a new file.
---------------------------------------------------------------------------------------
55 MESSAGE Permanent directory overflow.
CAUSE The file directory is full, no more new files can be created.
ACTION Purge some old and unused files.
---------------------------------------------------------------------------------------
56 MESSAGE File does not exist.
CAUSE A file that does not exist was referenced.
ACTION Use a different file or create the file.
---------------------------------------------------------------------------------------
58 MESSAGE 1. Operation inconsistent with file type or device type.
2. Invalid file type: Must be ASCII, BASIC DATA, or BASIC
SAVE.
3. Invalid file type: Must be ASCII or BASIC DATA file.
CAUSE 1. A file was accessed in a way that is illegal either because
of the file type or because of the device the file is on.
Examples are :
A direct read/write on a tape file.
A direct word read on an ASCII file.
2. The file code on a file for a GET, RUN, or GET SUB command
is not a BASIC data, BASIC SAVE, or ASCII file.
3. A MERGE or LINK command was issued for a file that is
neither a BASIC data file nor an ASCII file.
ACTION 1. Change the access method or move the file to a different
device.
2. Make sure these commands are used with the valid file code.
Only BASIC DATA, BASIC SAVE, or ASCII files are valid file
types.
3. Resave the program for the MERGE or LINK using the SAVE or
SAVE LIST command.
---------------------------------------------------------------------------------------
59 MESSAGE End of file found.
CAUSE A file was accessed beyond its logical end. This is usually
caused by trying to read more data that the file contains or by
writing to a file that is already full.
ACTION Expand the file or don't access records beyond the logical end
of the file.
---------------------------------------------------------------------------------------
60 MESSAGE Physical or logical end of record found in direct access mode.
CAUSE The record size of a file is not big enough to hold the entire
output list during a direct record write.
ACTION Reduce the output list or re-create the file with a larger
record size.
---------------------------------------------------------------------------------------
61 MESSAGE BASIC data file record size too small for data item.
CAUSE The record size of the HP Business BASIC data file is too small
for the numeric data item being output.
ACTION Re-create the file and increase the record size.
---------------------------------------------------------------------------------------
62 MESSAGE File is protected, wrong lockword/password specified.
CAUSE The wrong lockword has been used in trying to open a protected
file.
ACTION Use the correct lockword.
---------------------------------------------------------------------------------------
63 MESSAGE Invalid record size specification.
CAUSE The RECSIZE specification in a CREATE statement is invalid;
most probably too large.
ACTION The maximum record size allowed is installation defined. Check
your installation for RECSIZE limit and modify the CREATE
statement.
---------------------------------------------------------------------------------------
65 MESSAGE Incorrect data type in BASIC data file.
CAUSE A numeric item from a BASIC data file was read into a string
variable or vice versa.
ACTION Use a different variable or redefine the current one.
---------------------------------------------------------------------------------------
68 MESSAGE Syntax error at character N.
CAUSE All syntax errors are error number 68. N points to the
character in the statement that produced the error. This
message is usually followed by another more specific
description. For a list of the syntax error messages, see the
last section of this appendix.
ACTION Re-enter the statement.
---------------------------------------------------------------------------------------
92 MESSAGE Cannot access file because file is being accessed or is
accessed exclusively.
CAUSE This error is most often caused when a file that is opened for
exclusive access in another statement is accessed or a file
that is still open (active) is purged.
ACTION Close the file before accessing it.
---------------------------------------------------------------------------------------
93 MESSAGE Operation inconsistent with file open mode.
CAUSE A file is accessed in a way that is inconsistent with its file
open mode. For example, a file that is open for read only is
written to.
ACTION Close the file and re-open it in a different mode.
---------------------------------------------------------------------------------------
100 MESSAGE IMAGE specification expects a numeric item.
CAUSE A string value has been assigned when the format specification
in the IMAGE statement specifies a numeric format.
ACTION Change the format specification.
---------------------------------------------------------------------------------------
101 MESSAGE IMAGE specification expects a string item.
CAUSE A numeric value has been assigned when the format in the IMAGE
statement specifies a character format.
ACTION Change the format specification.
---------------------------------------------------------------------------------------
102 MESSAGE Format specification too long.
CAUSE The output format of an item in an IMAGE statement is longer
than the internal buffer can handle.
For example, IMAGE DD.DD,510X,K .
The specification 510X overflows the internal buffer used for
formatted input.
ACTION Reduce the size of the format specification, or break it up
into two or more separate formats.
---------------------------------------------------------------------------------------
103 MESSAGE No IMAGE format specifications exist.
CAUSE An item was output using formatted output, but the IMAGE
statement does not contain any format specifier.
ACTION Add the appropriate format specifier to the IMAGE statement.
---------------------------------------------------------------------------------------
104 MESSAGE File open conflict with previous open mode.
CAUSE A file has been opened a second time after it has been opened
already, and the second open mode conflicts with the first one.
For instance, a file that is open for APPEND cannot be opened
in any other mode.
ACTION Re-open the file in a different mode.
---------------------------------------------------------------------------------------
110 MESSAGE Program unit is too large. No space available to process this
line.
CAUSE The program is too big to be processed by the interpreter.
ACTION See Error 2 - memory overflow.
---------------------------------------------------------------------------------------
111 MESSAGE Too many REMARKS or DATA in subunit or too many subunits in
program.
CAUSE The program is too big to be processed by the interpreter.
ACTION See Error 2 - memory overflow.
---------------------------------------------------------------------------------------
112 MESSAGE Cannot add subunits because of size of largest subunit.
CAUSE Program is too big to be processed by the interpreter.
ACTION Reduce the subunit size.
---------------------------------------------------------------------------------------
113 MESSAGE Programs cannot be RUN when the subunit space has been set
above 12400 words.
CAUSE The subunit space is set too large for the program to be run in
the interpreter. This message is mainly for the Program
Analyst.
ACTION Reduce the subunit space size.
---------------------------------------------------------------------------------------
114 MESSAGE Size requested for subunit space is too large. Default size
will be used.
CAUSE The subunit space size requested is too large (larger than
20000), the default size of 10466 words is used.
ACTION None, the default size will be used.
---------------------------------------------------------------------------------------
115 MESSAGE Too much data space used in this subunit.
CAUSE The most probable cause is that the common area in this subunit
contains a variable that is too big. For instance, an array
A(10000) in a COM statement.
ACTION Reduce the size of large arrays.
---------------------------------------------------------------------------------------
117 MESSAGE Not enough memory available for local variables in subunit.
CAUSE The program is too big to be processed by the interpreter.
ACTION Reduce the size of the program.
---------------------------------------------------------------------------------------
119 MESSAGE Unable to allocate data space, request would cause total to
exceed configured limit.
CAUSE The program is too big to be processed by the interpreter.
ACTION Reduce the size of the program.
---------------------------------------------------------------------------------------
131 MESSAGE Device unavailable.
CAUSE The device to which a file is assigned is not available. For
example, a file is assigned to a tape drive that is either
already assigned or is not turned on. This message is usually
returned by the operating system.
ACTION Assign the file to a different device or resolve the problem
with the requested device
---------------------------------------------------------------------------------------
132 MESSAGE Cannot READ a number from a quoted string.
CAUSE This error message only comes from a compiled program. The
READ statement specifies a numeric variable but there is string
data in the DATA statement.
ACTION Correct the DATA statement or read the string data into a
string variable.
---------------------------------------------------------------------------------------
134 MESSAGE Unit not ready or online.
CAUSE The device to which a file is assigned is not ready to be used.
For example, a tape drive may not be online when a tape file is
being read.
ACTION Ready the device and continue.
---------------------------------------------------------------------------------------
150 MESSAGE Type of CASE expression does not match type of SELECT.
CAUSE The SELECT variable and the CASE expression do not match in
data type. For example, the SELECT specifies a numeric
variable but the CASE specifies a string variable.
ACTION Change the SELECT and CASE statements to use data of the same
type.
---------------------------------------------------------------------------------------
151 MESSAGE This statement cannot occur in this report section
CAUSE The interpreter has detected a statement in a report section
that does not belong there. This error is part of error 157,
VERIFY error.
ACTION Delete the statement.
---------------------------------------------------------------------------------------
152 MESSAGE Structured construct mismatch with lines N and M.
CAUSE A multi-line construct is mismatched in its begin and end. For
instance, an multi-line IF is closed with an ENDWHILE statement
or vice versa. This error is part of error 157, VERIFY error.
ACTION Add the necessary statement.
---------------------------------------------------------------------------------------
153 MESSAGE Structured construct error with line N.
CAUSE The interpreter has detected a statement that is not meaningful
in that context. For instance, an ELSE statement found in the
program that is not part of any multi-line IF statement. This
error is part of error 157, VERIFY error.
ACTION Delete line N.
---------------------------------------------------------------------------------------
154 MESSAGE GRAND TOTALS must go in REPORT HEADER, REPORT TRAILER or REPORT
EXIT.
CAUSE The GRAND TOTALS statement is in the wrong part of a report
writer section. This error is part of error 157, VERIFY error.
ACTION Move this line to the appropriate section.
---------------------------------------------------------------------------------------
155 MESSAGE TOTALS must go in HEADER or TRAILER section.
CAUSE The TOTALS line is in the wrong section of the Report Writer
code. This error is part of error 157, VERIFY error.
ACTION Move the TOTALS line to the appropriate section.
---------------------------------------------------------------------------------------
156 MESSAGE This statement must occur within a report definition.
CAUSE The interpreter detected a statement in the report description
section that should be in the report definition section. This
error is part of error 157, VERIFY error.
ACTION Remove the statement.
---------------------------------------------------------------------------------------
157 MESSAGE VERIFY error(s) in program.
CAUSE The interpreter, before executing your program, must first
verify that the program is correctly structured. Any errors
detected during VERIFY are reported separately, followed by
this error message.
ACTION Correct the error indicated and re-run the program.
---------------------------------------------------------------------------------------
158 MESSAGE This statement may not be used in a report definition.
CAUSE A statement that should not appear inside a report definition
has been detected. This error is part of error 157, VERIFY
error.
ACTION Delete the statement.
---------------------------------------------------------------------------------------
171 MESSAGE Statement can only occur in a SUB.
CAUSE A multi-line function is found to contain a statement that has
meaning only in a SUB. For instance, a SUBEXIT statement is in
a multi-line function. This error is part of error 157, VERIFY
error.
ACTION Delete or replace the statement.
---------------------------------------------------------------------------------------
174 MESSAGE Statement on line N can only occur in a numeric function.
CAUSE A string function contains a numeric value in its RETURN
statement. This error is part of error 157, VERIFY error.
ACTION Change the return value to the correct type.
---------------------------------------------------------------------------------------
175 MESSAGE Statement on line N can only occur in a string function.
CAUSE A numeric function contains a string value in its RETURN
statement. This error is part of error 157, VERIFY error.
ACTION Change the return value to the correct type.
---------------------------------------------------------------------------------------
176 MESSAGE Statement on line N can only occur in a multi-line function.
CAUSE The statement on the cited line is allowed only in a multi-line
function.
ACTION Make sure that this statement is in a function or use a
different statement.
---------------------------------------------------------------------------------------
177 MESSAGE Dimensions of VAR use local variables.
CAUSE A variably dimensioned array VAR uses a local variable in its
definition. For instance, DIM A(Loc) where Loc is a local
variable in the SUB where A is defined. This error is part of
error 157, VERIFY error.
ACTION Redefine the array.
---------------------------------------------------------------------------------------
178 MESSAGE Dimensions of VAR use single line functions containing local
variables.
CAUSE A variably dimensioned array uses a single line function to
return its dimension. The single line function uses a local
variable of the SUB in which it is defined. This error is part
of error 157, VERIFY error.
ACTION Redefine the variably dimensioned array.
---------------------------------------------------------------------------------------
179 MESSAGE Structured construct on line N not properly closed.
CAUSE The interpreter has detected a multi-line construct that has no
closing statement. For instance, a SELECT has no corresponding
ENDSELECT statement, or a multi-line IF has no ENDIF. This
error is part of error 157, VERIFY error.
ACTION Add the required closing statement.
---------------------------------------------------------------------------------------
180 MESSAGE Illegal data in input.
CAUSE An illegal data item has been detected during input. If input
data is numeric, this probably means there are non-numeric
characters in the data. For string input, it could mean the
data is longer than the receiving variable.
ACTION Check input data for accuracy.
---------------------------------------------------------------------------------------
182 MESSAGE Current CHARS value of N exceeds valid range of 1 to 500.
CAUSE In the ACCEPT or TINPUT statement, the CHARS option specifies N
characters, more characters than allowed.
ACTION Input fewer characters.
---------------------------------------------------------------------------------------
200 MESSAGE Line referenced is not a PACKFMT statement.
CAUSE In a PACK or UNPACK statement, the referenced PACKFMT line is
not a PACKFMT statement.
ACTION Check the PACK or UNPACK statement to make sure the line
referenced is a PACKFMT line.
---------------------------------------------------------------------------------------
202 MESSAGE String in PACK/UNPACK statement not long enough for PACKFMT
list.
CAUSE The string variable in a PACK or UNPACK statement is not long
enough to accommodate all the variables specified in the
PACKFMT statement.
ACTION Check the PACKFMT list for accuracy or redefine the string
variable in the PACK or UNPACK statement.
---------------------------------------------------------------------------------------
210 MESSAGE Bad data base status array.
CAUSE The status array for the database statements is not a ten word
array of short integers.
ACTION Correct the data type of the status array.
---------------------------------------------------------------------------------------
211 MESSAGE No DBASE IS statement active.
CAUSE A database has been sorted or searched without first defining
it with a DBASE IS statement.
ACTION Add a DBASE IS statement.
---------------------------------------------------------------------------------------
212 MESSAGE Data set N in thread list not in data base.
CAUSE One of the data sets defined in a THREAD IS statement, number
N, does not exist in the database.
ACTION Check the database for valid data sets.
---------------------------------------------------------------------------------------
213 MESSAGE Illegal items in IN DATASET statement.
CAUSE The IN DATASET statement used by SORT to locate the sort key
contains an illegal specification.
ACTION Delete the illegal specification in question.
---------------------------------------------------------------------------------------
214 MESSAGE Substring not allowed in IN DATASET statement with SORT.
CAUSE The IN DATASET statement used by SORT to locate the sort key
contains a substring variable.
ACTION Replace the substring variable with a string.
---------------------------------------------------------------------------------------
215 MESSAGE Variable dimensioned array not allowed in IN DATASET statement
with SORT.
CAUSE The IN DATASET statement used by SORT to locate the sort key
contains a variably dimensioned array variable.
ACTION Replace it with a regularly dimensioned array.
---------------------------------------------------------------------------------------
216 MESSAGE IN DATASET does not allow string parameters to be used.
CAUSE The IN DATASET statement used by SORT to locate the sort key
contains a string variable which is passed into the procedure
as a parameter from another procedure.
ACTION Use a locally defined string variable of the same length as the
parameter.
---------------------------------------------------------------------------------------