MFPLI00100 - MFPLI00119
MFPLI00100S "entry-name" has been referenced with too few arguments.
The entry "
entry-name
" has been referenced with fewer arguments than the number of parameter descriptors in the declaration.
MFPLI00101S "entry-name" has been referenced with too many empty argument lists.
MFPLI00102S This statement contains duplicate options.
The statement contains the same option more than once, for example a DO statement with two TO options.
MFPLI00103S Invalid option for this statement or invalid syntax in an option.
Either an option on this statement or its syntax is invalid.
MFPLI00104S One of the iSUBs used in the base-reference of "variable-name" cannot be replaced by a subscript from this reference. This reference cannot be mapped into a valid reference to the base-variable.
MFPLI00105S The precision specified for the result of this built-in function exceeds the implementation's maximum allowed for the resulting data type.
The precision specified for the result of this conversion built-in function is too big.
MFPLI00106S A reference to "array-name" contains a subscript that has not been used as a replacement for an iSUB or an asterisk in the base-reference. This reference cannot be mapped into a valid reference to the base variable.
MFPLI00107S "array-name" has been referenced with too few subscripts. Asterisk subscripts must be used to reference a cross-section. All subscripted references must have as many subscripts as the array has dimensions - including any inherited dimensions.
An array reference must either have no subscript list or a list with the same number of subscripts as the number of dimensions in the declaration of the array.
MFPLI00108S An array or STRUCTURE value has been used in a context that requires a scalar value.
A scalar value is required by the context, for example the control variable of a DO statement, but an aggregate value has been supplied.
MFPLI00109W BIT operators should only be applied to BIT operands.
MFPLI00110E A string constant exceeds the implementation's maximum length of length-limit. Truncation will occur.
This implementation's maximum length for a string constant is
length-limit
.
MFPLI00111S An operation on two STRUCTUREs is possible only when both STRUCTUREs have the same number of immediate members.
MFPLI00112S An operation on two arrays is possible only when both arrays have the same number of dimensions and the exact same lower and upper bounds.
MFPLI00113S A bit-string constant contains an invalid digit following the B. Only 1, 2, 3, or 4 are permitted.
Bit-string constants can be expressed in binary, quaternary, octal or hexadecimal.
MFPLI00114W %%preprocessor-statement is an unrecognizable %% statement; ignored.
%%
preprocessor-statement
is not recognized as a pre-processor statement.
MFPLI00115S Invalid syntax in %%REPLACE statement. The correct syntax is %%REPLACE id BY c; where id is an identifier and c is: a character-string constant, a bit-string constant, or an arithmetic constant preceded by an optional minus sign.
The syntax of the %%REPLACE statement is invalid;.
MFPLI00116S "constant" could not be converted to its internal representation. Check for too many digits, an exponent that is too large or too small, or an invalid character in a string constant.
MFPLI00117U The number of nested %%INCLUDE statements has exceeded the implementation's limit.
MFPLI00118S Invalid syntax in %%INCLUDE statement. The correct syntax is one of the following forms: %%INCLUDE 'string-constant'; %%INCLUDE identifier; or %%INCLUDE (identifier); or %%INCLUDE identifier(identifier);
The syntax of the %%INCLUDE statement is invalid;.
MFPLI00119S The first argument to a LBOUND, HBOUND, or DIM built-in function must be an array reference.
The LBOUND, HBOUND and DIMENSION built-in functions require an array reference as the first argument.
Parent topic:
MFPLI - PL/I Compiler Messages