HP Business BASIC/XL Reference Manual - HP 3000 MPE/iX Computer Systems - Edition 1 (32715-90001)

a- 2
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.