MFPLI00040 - MFPLI00059
MFPLI00040S This LEAVE statement is either not contained within a DO group, or it attempts to transfer control out of the current PROCEDURE or BEGIN block.
A LEAVE statement may only transfer control out of a DO group within the current PROCEDURE or BEGIN block.
MFPLI00041S This statement contains an ambiguous reference to "identifier-name".
The compiler cannot determine which instance of "
identifier-name
" is being referenced.
MFPLI00042U Possible compiler error. The compiler is unable to find a value node. Correct all program errors and recompile. If this message persists, contact Micro Focus Support Line.
Internal compiler error.
MFPLI00043S Both the FILE and the STRING options have been used in this statement.
Only one of the options FILE and STRING may be used in a GET or PUT statement.
MFPLI00044S "array-name" has been declared with an INITIAL attribute. An INITIAL attribute cannot be specified for AUTOMATIC arrays with nonconstant extents.
The INITIAL attribute may only be specified for AUTOMATIC arrays that have constant extents.
MFPLI00045S Both the DATA and the LIST options have been used in this statement.
Only one of the options DATA and LIST may be used in a GET or PUT statement.
MFPLI00046S "identifier-name" is declared with conflicting or duplicate attributes.
"
identifier-name
" is either declared with the same attribute twice or with conflicting attributes, for example, FIXED and FLOAT, or BINARY and DECIMAL.
MFPLI00047S Both the KEY and the KEYTO options have been used in this statement.
The KEY and KEYTO options are mutually exclusive and no more than one can be used in a READ statement.
MFPLI00048S Both the SET and the INTO options have been used in this statement.
Only one of the options SET and INTO may be used in a READ statement.
MFPLI00049S An expected type-name value was not found. One of the values in this statement has a data type which is inconsistent with the context in which the value is used.
MFPLI00050E The precision specified for "variable-name" exceeds the implementation's limit of FIXED BINARY variables. The maximum precision has been supplied. Use FIXED DECIMAL for larger values.
The maximum precision that may be specified for a FIXED BINARY variable is 63.
MFPLI00051E The precision specified for "variable-name" exceeds the implementation's limit for FIXED DECIMAL variables. The maximum precision has been supplied.
The maximum precision that may be specified for a FIXED DECIMAL variable is 31.
MFPLI00052E The scale-factor specified for "variable-name" exceeds the implementation's limit. The scale-factor has been set to zero.
MFPLI00053E The precision specified for "variable-name" exceeds the implementation's limit for FLOAT BINARY variables. The maximum precision has been supplied.
The maximum precision that may be specified for a FLOAT BINARY variable is 52.
MFPLI00054E The precision specified for "variable-name" exceeds the implementation's limit for FLOAT DECIMAL variables. The maximum precision has been supplied.
The maximum precision that may be specified for a FLOAT DECIMAL variable is 16.
MFPLI00055E Size or precision must be part of a VALUE clause; ignored.
MFPLI00056S More than 8 dimensions have been specified in a DIMENSION attribute.
MFPLI00057U PASS2 has overflowed its stack. Reduce the complexity of this statement and recompile.
MFPLI00058S A descriptor is an apparent STRUCTURE member, but does not immediately follow a descriptor with a level-number.
MFPLI00059S "array-name" is declared with an * extent but is not a parameter or a descriptor.
Parent topic:
MFPLI - PL/I Compiler Messages