FORTRAN, Error Messages
*Conan The Librarian (sorry for the slow response - running on an old VAX)
|
VMS Help FORTRAN, Error Messages *Conan The Librarian (sorry for the slow response - running on an old VAX) |
|
| 1 - Compilation Errors |
A diagnostic message issued by the compiler describes the detected
error and, in some cases, contains an indication of the action
taken by the compiler in response to the error.
Besides reporting errors detected in source program syntax, the
compiler issues messages indicating errors that involve the
compiler itself, such as I/O errors.
The severity-level classes of compilation error messages, in order
of greatest to least severity, are as follows:
Code Description
---- -----------
F Fatal; must be corrected before the program can
be compiled. No object file is produced.
E Error; should be corrected. An object file is
produced, but the output or program result may
be incorrect.
W Warning; should be investigated by checking the
statements to which warning diagnostic messages
refer. Warnings are issued for statements that
use acceptable, but nonstandard, syntax and for
statements corrected by the compiler. An object
file is produced, but the program results may be
incorrect. (If you specify /NOWARNINGS on the
FORTRAN command line, you will not receive these
messages.)
I Information; not an error message and does not call
for corrective action. However, the informational
message informs you that either a correct Compaq Fortran
statement may have unexpected results or you have
used a Compaq Fortran extension to FORTRAN-77.
The following examples show how compilation messages are displayed:
%FORT-W-FMTEXTCOM, Extra comma in format list
[FORMAT (I3,)] in module MORTGAGE at line 13
%FORT-F-UNDSTALAB, Undefined statement label
[66] in module MORTGAGE at line 19
1.1 - ADJARRBOU
SEVERITY: F MESSAGE TEXT: Adjustable array bound contains invalid data item EXPLANATION: An adjustable array dimension declarator expression contained an operand that was not one of the following: o A constant o A variable in a common block o A variable associated with a subprogram dummy argument
1.2 - ADJARRUSE
SEVERITY: F MESSAGE TEXT: Adjustable array used in invalid context EXPLANATION: A reference to an adjustable array was made in a context where such a reference is not allowed.
1.3 - ADJLENUSE
SEVERITY: F MESSAGE TEXT: Passed-length character name used in invalid context EXPLANATION: A reference to a passed-length character array or variable was made in a context where such a reference is not allowed.
1.4 - AGGREFSIZ
SEVERITY: F MESSAGE TEXT: Aggregate reference exceeds 65535 bytes per element EXPLANATION: Any aggregate reference larger than 65535 bytes cannot be used in an I/O list or as an actual or dummy argument.
1.5 - ALNNOMAT
SEVERITY: W
MESSAGE TEXT: A lignment settings of common block are inconsistent with
previous declaration
EXPLANATION: Occurs when using CDEC$ OPTIONS/ALIGN (or /WARN=ALIGN)
if the same COMMON is declared in multiple places within a single
compilation unit and /ALIGN or /WARN=ALIGN has changed between
places. For example:
CDEC$ OPTIONS /ALIGN=COMMON=NATURAL
COMMON /COM1/ A,B ! common elements are naturally aligned
CDEC$ END OPTIONS
CDEC$ OPTIONS /ALIGN=COMMON=PACKED
COMMON /COM1/ C,D ! common elements are packed
CDEC$ END OPTIONS
Note that COMMON declarations can also take place in SAVE and
VOLATILE statements and in CDEC$ PSECT, CPAR$ PRIVATE and CPAR$
SHARED directives. All declarations must be in the scope of a
consistent setting for alignment and alignment warnings.
USER ACTION: Modify the program to remove inconsistent alignment directives.
1.6 - ALTRETLAB
SEVERITY: F MESSAGE TEXT: Alternate return label used in invalid context EXPLANATION: An alternate return argument cannot be used in a function reference.
1.7 - ALTRETOMI
SEVERITY: E
MESSAGE TEXT: Alternate return omitted in SUBROUTINE or ENTRY
statement
EXPLANATION: An asterisk is missing in the argument list of a
subroutine for which an alternate return is specified. Examples:
1. SUBROUTINE XYZ(A,B)
. . .
RETURN 1
2. ENTRY ABC(Q,R)
. . .
RETURN I+4
1.8 - ALTRETSPE
SEVERITY: F
MESSAGE TEXT: Alternate return specifier invalid in FUNCTION
subprogram
EXPLANATION: The argument list of a FUNCTION declaration contains
an asterisk or a RETURN statement in a function subprogram
specifies an alternate return. Examples:
1. INTEGER FUNCTION TCB(ARG,*,X)
2. FUNCTION IMAX
. . .
RETURN I+J
END
1.9 - ARGLISEXE
SEVERITY: F MESSAGE TEXT: IARGCOUNT/IARGPTR used in non-executable statement EXPLANATION: One of the argument list inquiry functions, IARGCOUNT or IARGPTR, was used in a non-executable statement such as a statement function declaration.
1.10 - ARIVALREQ
SEVERITY: F MESSAGE TEXT: Character expression where arithmetic value required EXPLANATION: An expression that must be arithmetic (INTEGER, REAL, LOGICAL, or COMPLEX) was of type CHARACTER.
1.11 - ASFUNUSED
SEVERITY: I MESSAGE TEXT: Statement function was defined but not used EXPLANATION: The specified statement function was defined but never used. This message can be suppressed with /WARNINGS=NOUNCALLED.
1.12 - ASSARRUSE
SEVERITY: F MESSAGE TEXT: Assumed size array name used in invalid context EXPLANATION: An assumed size array name was used where the size of the array was also required, for example, in an I/O list.
1.13 - ASSDOVAR
SEVERITY: W MESSAGE TEXT: Assignment to DO variable within loop EXPLANATION: The control variable of a DO loop has been altered within the range of the DO statement.
1.14 - ATTRIERR
SEVERITY: I
MESSAGE TEXT: COMMON attributes conflict, using the default
attribute
EXPLANATION: This error only occurs with the CDEC$ PSECT compiler
directive statement and under any of the following circumstances:
o A common block is declared as both GBL (global) and LCL
(local), both WRT (write) and NOWRT (nowrite), or both SHR
(shared) and NOSHR (noshared).
o More than one alignment (ALIGN=) to the COMMON block is
specified.
o The following combination of compiler directive statements
occurs:
CPAR$ SHARED com_blk
and
CDEC$ PSECT /com_blk/ ATTRI=something-not-page-alignment
o An alignment value exceeding the legal range is specified. The
alignment attribute can only take the value of 0 through 9.
1.15 - AUTDATINI
SEVERITY: W MESSAGE TEXT: Variable is data-initialized; AUTOMATIC ignored EXPLANATION: A variable was declared as AUTOMATIC but was also data-initialized in a DATA or type-specification statement. AUTOMATIC variables cannot be data-initialized. The AUTOMATIC attribute was ignored.
1.16 - AUTSAVALL
SEVERITY: W MESSAGE TEXT: SAVE of all variables specified; AUTOMATIC ignored EXPLANATION: A variable was declared as AUTOMATIC in a program unit which contained a SAVE statement that, by omitting a list of names of variables to be SAVEd, specified that all variables should be SAVEd. The AUTOMATIC attribute was ignored.
1.17 - BADALIGN
SEVERITY: W MESSAGE TEXT: Variable not naturally aligned EXPLANATION: A variable or array was declared in such a way that it crossed a natural boundary for its data size.
1.18 - BADEND
SEVERITY: F MESSAGE TEXT: END [STRUCTURE|UNION|MAP] must match top EXPLANATION: A STRUCTURE, UNION, or MAP statement did not have a corresponding END STRUCTURE, END UNION, or END MAP statement, respectively.
1.19 - BADFIELD
SEVERITY: F MESSAGE TEXT: Field name not defined for this structure EXPLANATION: A field name not defined in a record structure was used in a record reference.
1.20 - BADRECREF
SEVERITY: F MESSAGE TEXT: Aggregate reference where scalar reference required EXPLANATION: An aggregate record reference was used where a scalar record reference was required.
1.21 - BADVALUE
SEVERITY: F MESSAGE TEXT: "keyword-value" is an invalid keyword value EXPLANATION: The specified FORTRAN command line contained a keyword "keyword-value" that is not recognized as a valid keyword value.
1.22 - BRNCHINTOBLK
SEVERITY: I MESSAGE TEXT: Questionable branch into loop or block EXPLANATION: A branch into a DO loop or IF block was detected. Although this might be valid if the FORTRAN 66 "extended range of a DO loop" feature was being used, it generally indicates a programming error. A common case involves two or more DO loops which share a common termination. In such cases, the shared termination statement is considered to belong to the innermost DO loop. This message can be suppressed with /WARNINGS=NOUSAGE.
1.23 - BUGCHECK
SEVERITY: F MESSAGE TEXT: Internal consistency failure EXPLANATION: The compiler detected an internal error and the compilation was terminated. Please report the problem to Compaq (by means of a Software Performance Report (SPR)) and include all information necessary to reproduce the error.
1.24 - CDDALNARY
SEVERITY: I MESSAGE TEXT: CDD description specifies an aligned array (unsupported) EXPLANATION: The CDD description contained an array field whose elements have an alignment that Compaq Fortran cannot accommodate. When this error is encountered, the array is replaced by a structure of the appropriate size.
1.25 - CDDBITSIZ
SEVERITY: F MESSAGE TEXT: CDD field specifies a bit size or alignment. EXPLANATION: The CDD's bit datatype and bit alignment are not supported by Compaq Fortran.
1.26 - CDDERROR
SEVERITY: I MESSAGE TEXT: CDD description extraction condition EXPLANATION: The Compaq Fortran compiler encountered an error while extracting a structure definition from the Common Data Dictionary (CDD). See the accompanying messages for more information.
1.27 - CDDINIVAL
SEVERITY: I MESSAGE TEXT: CDD description contains Initial Value attribute (ignored) EXPLANATION: A field that specified an initial value was present in the CDD description being expanded. When this error is encountered, the initial value is ignored.
1.28 - CDDNOTSTR
SEVERITY: F MESSAGE TEXT: CDD record is not a structure EXPLANATION: Compaq Fortran requires structure definitions (elementary field descriptions in CDDL). The data described by the CDD is not a structure.
1.29 - CDDRECDIM
SEVERITY: F MESSAGE TEXT: CDD record is dimensioned EXPLANATION: Compaq Fortran does not support dimensioned structures, for example, arrays of structures.
1.30 - CDDSCALED
SEVERITY: W MESSAGE TEXT: CDD description specifies a scaled data type EXPLANATION: Compaq Fortran does not support scaled data types. The data described by the CDD specifies a scaled component.
1.31 - CDDTOOBIG
SEVERITY: F MESSAGE TEXT: Attributes for some member of CDD record description exceed implementation's limit for member complexity EXPLANATION: Some member of the Common Data Dictionary record description had too many attributes and created a program that was too large. Change the CDD description to make the field description smaller.
1.32 - CDDTOODEEP
SEVERITY: F MESSAGE TEXT: Attributes for CDD record description exceed implementation's limit for record complexity EXPLANATION: The CDD record description contained structures that were nested too deeply. Modify the CDD description to reduce the level of nesting in the record description.
1.33 - CHACONCONTD
SEVERITY: I
MESSAGE TEXT: Character, Hollerith or RAD50 constant continued
across lines; may be non-portable
EXPLANATION: A character, Hollerith or RAD50 constant was continued
across two or more source lines. This is potentially non-portable
as some implementations pad source lines with blanks and others,
including Compaq Fortran, do not, which can result in different constant
values. This diagnostic is issued only if one or more of the source
lines which made up the statement was shorter than the statement field
width (72 or 132 columns, depending on /EXTEND_SOURCE), and can be
suppressed with /WARNINGS=NOUSAGE.
USER ACTION: For character constants, use the concatenation
operator to build up long values. Replace Hollerith or
RAD50 constants with character constants if feasible or
ensure that they are complete on one line. For character
constants used for data initialization, PARAMETER constants
must be used to maintain FORTRAN-77 standard conformance.
For example:
CHARACTER*(*) CHRCON
PARAMETER (CHRCON = 'This is a continued '//
1 'character value')
CHARACTER*80 CHRVAL
DATA CHRVAL /CHRCON/
1.34 - CHANAMINC
SEVERITY: E
MESSAGE TEXT: Character name incorrectly initialized with numeric
value
EXPLANATION: Character data with a length greater than one was
initialized with a numeric value in a DATA statement. Example:
CHARACTER*4 A
DATA A/14/
1.35 - CHASBSLIM
SEVERITY: F
MESSAGE TEXT: Character substring limits out of order
EXPLANATION: The first character position of a substring
expression was greater than the last character position. Example:
C(5:3)
1.36 - CHAVALREQ
SEVERITY: F MESSAGE TEXT: Arithmetic expression where character value required EXPLANATION: An expression that must be of type CHARACTER was of another data type.
1.37 - CLOSEIN
SEVERITY: F MESSAGE TEXT: Error closing "file-spec" as input EXPLANATION: Unable to close the file "file-spec".
1.38 - CLOSEOUT
SEVERITY: F MESSAGE TEXT: Error closing "file-spec" as output EXPLANATION: Unable to close the file "file-spec".
1.39 - COMALNERR
SEVERITY: F MESSAGE TEXT: COMMON alignment error, too small for variable EXPLANATION: A field in the COMMON block is larger than the size of alignment requested by the CDEC$ PSECT directive. USER ACTION: Specify a larger alignment value in the CDEC$ PSECT directive for the COMMON block.
1.40 - COMVARDECL
SEVERITY: F MESSAGE TEXT: Common variable cannot be declared SHARED or PRIVATE EXPLANATION: A variable within a common block cannot be specified in a CONTEXT_SHARED or PRIVATE compiler directive statement. Entire common blocks can be declared shared or private, but individual elements within them cannot be declared context-shared or private.
1.41 - CONMEMEQV
SEVERITY: E MESSAGE TEXT: Conflicting memory attributes in an equivalenced group EXPLANATION: By means of an EQUIVALENCE statement, certain memory locations were given conflicting memory attributes (shared or context-shared and private).
1.42 - COMNAMCONF
SEVERITY: I MESSAGE TEXT: COMMON block name conflicts with other global entity - usage is non-standard and non-portable EXPLANATION: The name of a COMMON block is not allowed to be the same as the name of any other global entity (program unit, external procedure) (F77 standard 18.1.1). Such a conflict may cause incorrect execution on other platforms. USER ACTION: Change the name of either the COMMON block or the other global entity to remove the conflict. This message can be suppressed by /WARNINGS=NOUSAGE.
1.43 - CONSIZEXC
SEVERITY: E MESSAGE TEXT: Constant size exceeds variable size in data initialization EXPLANATION: A constant used for data initialization is larger than its corresponding variable.
1.44 - DBGOPT
SEVERITY: I MESSAGE TEXT: The NOOPTIMIZE qualifier is recommended with the DEBUG qualifier EXPLANATION: Optimizations performed by the compiler can cause several different kinds of unexpected behavior when using OpenVMS DEBUG. For more information about compiler optimizations, see the Compaq Fortran Performance Guide for OpenVMS VAX Systems.
1.45 - DEFSTAUNK
SEVERITY: I MESSAGE TEXT: Default STATUS='UNKNOWN' used in OPEN statement EXPLANATION: The OPEN statement default STATUS='UNKNOWN' can cause an old file to be inadvertently modified.
1.46 - DEPENDITEM
SEVERITY: I MESSAGE TEXT: CDD description contains Depends Item attribute (ignored) EXPLANATION: Fortran does not support the Common Data Dictionary Depend Item attribute.
1.47 - DESCOMABORT
SEVERITY: F MESSAGE TEXT: /DESIGN=COMMENTS processing has been aborted due to an internal error EXPLANATION: The design processing routines have detected an internal error; subsequent messages provide more detail. Please report the problem to Compaq.
1.48 - DESCOMERR
SEVERITY: W MESSAGE TEXT: Error in processing design information EXPLANATION: The comment analysis routines have detected an error in the text of a comment, such as an undefined keyword in a structured tag. Additional messages relating to the error are also displayed.
1.49 - DESCOMNOLSE
SEVERITY: F MESSAGE TEXT: /DESIGN=COMMENTS requires installation of DEC Language Sensitive Editor EXPLANATION: To use /DESIGN=COMMENTS, the Language Sensitive Editor (part of DECset) needs to be installed on this system. Omit /DESIGN=COMMENTS, attempt the compilation on another system where the Language Sensitive Editor is installed, or install the Language Sensitive Editor and retry.
1.50 - DESCOMSEVERR
SEVERITY: F MESSAGE TEXT: A serious error has occurred processing /DESIGN=COMMENTS EXPLANATION: The comment analysis routines have detected a severe error that prevents further comment analysis in the current compilation. Additional messages relating to the error are also displayed. The compilation is aborted.
1.51 - DESIGNTOOOLD
SEVERITY: F MESSAGE TEXT: /DESIGN=COMMENTS processing routines are too old for the compiler EXPLANATION: The version of the comment analysis routines present on the system is not supported by this version of Compaq Fortran. Install a newer version of the Language Sensitive Editor to obtain the newer comment analysis routines.
1.52 - DICTABORT
SEVERITY: F MESSAGE TEXT: DICTIONARY processing of CDD record description aborted EXPLANATION: The Compaq Fortran compiler is unable to process the Common Data Dictionary record description. See the accompanying messages for further information.
1.53 - DIRSTRREQ
SEVERITY: I MESSAGE TEXT: Directive requires string constant, directive ignored EXPLANATION: This error only occurs with the use of the CDEC$ compiler directive statements: TITLE, SUBTITLE, and IDENT. String values for the TITLE, SUBTITLE, and IDENT directives cannot be more than 31 characters. Any other values, including PARAMETER statement constants that are defined to be strings, are invalid on these directives.
1.54 - ENDOPTMIS
SEVERITY: W MESSAGE TEXT: No matching CDEC$ END OPTIONS for CDEC$ OPTIONS EXPLANATION: A CDEC$ OPTIONS directive must be terminated by CDEC$ END OPTIONS. USER ACTION: Make sure that each CDEC$ OPTIONS directive is properly terminated by a CDEC$ END OPTIONS directive.
1.55 - ENTDUMVAR
SEVERITY: F MESSAGE TEXT: ENTRY dummy variable previously used in executable statement EXPLANATION: The dummy arguments of an ENTRY statement must not have been used previously in an executable statement in the same program unit.
1.56 - EQVEXPCOM
SEVERITY: F MESSAGE TEXT: EQUIVALENCE statement incorrectly expands a common block EXPLANATION: A common block cannot be extended beyond its beginning by an EQUIVALENCE statement.
1.57 - EQVSAVCOM
SEVERITY: E MESSAGE TEXT: EQUIVALENCE may not be used to put a SAVE variable into COMMON EXPLANATION: An EQUIVALENCE group was found which included a COMMON variable and a variable named in a SAVE statement. SAVE variables can not be placed in COMMON, although an entire COMMON block can be named in a SAVE statement.
1.58 - ERRLIMEXC
SEVERITY: F MESSAGE TEXT: Error limit exceeded; compilation terminated EXPLANATION: The limit on the number of E or F level errors specified by the /ERROR_LIMIT qualifer was exceeded for this compilation unit. Compilation of this unit was terminated, but compilation continued for other units, if any.
1.59 - EXCCHATRU
SEVERITY: E MESSAGE TEXT: Non-blank characters truncated in string constant EXPLANATION: A character constant or Hollerith constant was converted to a data type that was not large enough to contain all the significant characters.
1.60 - EXCDIGTRU
SEVERITY: E MESSAGE TEXT: Non-zero digits truncated in constant EXPLANATION: A Hollerith, character literal or typeless constant was converted to a data type that was not large enough to contain all the significant digits.
1.61 - EXCNAMDAT
SEVERITY: E MESSAGE TEXT: Number of names exceeds number of values in data initialization EXPLANATION: The number of constants specified in a DATA statement must match the number of variables or array elements to be initialized. When a mismatch occurs, any extra variables or array elements are not initialized.
1.62 - EXCVALDAT
SEVERITY: E MESSAGE TEXT: Number of values exceeds number of names in data initialization EXPLANATION: The number of variables or array elements to be initialized must match the number of constants specified in data initialization. When a mismatch occurs, any extra constant values are ignored.
1.63 - EXPSTAOVE
SEVERITY: F MESSAGE TEXT: Compiler expression stack overflow EXPLANATION: An expression was too complex or there were too many actual arguments in a subprogram reference. A maximum of 255 actual arguments can be compiled. You can subdivide a complex expression or reduce the number of arguments.
1.64 - EXTARYUSE
SEVERITY: I
MESSAGE TEXT: Extension to FORTRAN-77: Nonstandard use of array
EXPLANATION: One of the following extensions was detected:
o An array was used as a FILE specification in an OPEN statement.
o The file name of an INQUIRE statement was a numeric scalar
reference or a numeric array name reference
1.65 - EXTBADCONT
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: nonstandard continuation character EXPLANATION: A nonstandard character was used as a continuation indicator.
1.66 - EXTCATDARG
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Concatenation of dummy argument EXPLANATION: A character dummy argument appeared as an operand in a concatenation operation.
1.67 - EXTCHAFOL
SEVERITY: E MESSAGE TEXT: Extra characters following a valid statement EXPLANATION: Superfluous text was found at the end of a syntactically correct statement. Check for typing or syntax errors.
1.68 - EXTCHARREQ
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Character required EXPLANATION: A character variable was initialized with a noncharacter value by means of a DATA statement.
1.69 - EXTCHASOU
SEVERITY: W MESSAGE TEXT: Extra characters in source line were truncated EXPLANATION: A source line was read that was longer than the statement field width and /WARNINGS=TRUNCATED_SOURCE was specified. The source line was truncated to the statement field width; 72 or 132 characters, depending on the value of the /EXTEND_SOURCE command or OPTIONS statement qualifier in effect.
1.70 - EXTCHRARG
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: CHARACTER*(*) argument used as function EXPLANATION: A formal argument used as a function was declared CHARACTER*(*). The FORTRAN-77 standard requires the length to be an integer constant.
1.71 - EXTCOMPARNAM
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: COMMON block has same name as PARAMETER constant EXPLANATION: A COMMON blocks was declared to have the same name as a PARAMETER constant, a PARAMETER constant was declared to have the same name as a previously declared COMMON block.
1.72 - EXTCONT19
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: more than 19 continuation lines EXPLANATION: More than 19 continuation lines were defined for the statement.
1.73 - EXTDATACOM
SEVERITY: I
MESSAGE TEXT: Extension to FORTRAN-77: Nonstandard DATA
initialization
EXPLANATION: One of the following extensions occurred:
o An element in a blank common block was data initialized.
o An element of a named common block was data initialized outside
of the BLOCK DATA program unit.
1.74 - EXTDATORD
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: DATA statement out of order EXPLANATION: A DATA statement occurred before a declaration statement. All DATA statements must occur after the declaration section of a program.
1.75 - EXTILDOCNT
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Negative implied-Do iteration count EXPLANATION: The iteration count of an implied DO was negative.
1.76 - EXTINTRIN
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: nonstandard intrinsic function EXPLANATION: A nonstandard intrinsic function was used.
1.77 - EXTLSTINF
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: nonstandard list directed internal EXPLANATION: A nonstandard list directed internal read or write statement was used.
1.78 - EXTMISSUB
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Missing array subscripts EXPLANATION: Only one subscript was used to reference a multi-dimensional array in an EQUIVALENCE statement.
1.79 - EXTMIXCOM
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Mixed numeric and character elements in COMMON EXPLANATION: A common block must not contain both numeric and character data.
1.80 - EXTMIXEQV
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Mixed numeric and character elements in EQUIVALENCE EXPLANATION: A numeric variable or numeric array element cannot be equivalenced to a character variable or character array element.
1.81 - EXTOPERAT
SEVERITY: I
MESSAGE TEXT: Extension to FORTRAN-77: Nonstandard operation
EXPLANATION: One of the following operations was detected:
o A logical operand and a nonlogical operand were used in the
same operation.
o A real type expression and a complex type expression were used
in the same statement.
o A character operand and a noncharacter operand were used in the
same operation.
o A nonlogical expression was assigned to a logical variable.
o A noncharacter expression was assigned to a character variable.
o A character dummy argument appeared in a concatenation
operation and the result of the expression was not assigned to
a character variable.
o Logical operators were used with nonlogical operands.
o Arithmetic operators were used with nonnumeric operands.
1.82 - EXTRECUSE
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Nonstandard use of field reference EXPLANATION: A record reference (for example, record-name.field-name) was used in a program compiled with the /STANDARD=[SYNTAX|ALL] qualifier in the FORTRAN command.
1.83 - EXTUSECCON
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Nonstandard use of character constant EXPLANATION: A character constant was used in an assignment statement where a numeric value is required.
1.84 - EXT_ARIREQ
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Arithmetic expression required EXPLANATION: A logical expression was used in an arithmetic IF statement.
1.85 - EXT_ASFARGNAM
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Statement function argument name same as non-variable EXPLANATION: A statement function dummy argument had the same name as an entity other than a variable or a common block (for example, a PARAMETER constant).
1.86 - EXT_COM
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: nonstandard comment EXPLANATION: FORTRAN-77 allows only the characters "C" and "*" to begin a comment line; "c", "D", "d", and "!" are extensions to FORTRAN-77.
1.87 - EXT_CONST
SEVERITY: I
MESSAGE TEXT: Extension to FORTRAN-77: nonstandard constant
EXPLANATION: The following constant forms are extensions to
FORTRAN-77:
Form Example
--------- ------------------
Hollerith nH.....
Typeless 'nnnn'B, B'nnnn',
'nnnn'X, X'nnnn',
'nnnn'O, O'nnnn',
'nnnn'Z, Z'nnnn'
Binary B'nn'
Octal "oooo or Ooooo
Hexadecimal Znnnn
Radix-50 nR.....
Complex with
PARAMETER components
COMPLEX*16 (www.xxxDn, yyy.zzzDn)
REAL*16 yyy.zzzQn
1.88 - EXT_DOEXPR
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Nonstandard loop expression EXPLANATION: The upper bound expression, lower bound expression, or increment expression of a DO loop was not of type integer, real, or double precision.
1.89 - EXT_FMT
SEVERITY: I
MESSAGE TEXT: Extension to FORTRAN-77: nonstandard FORMAT
statement item
EXPLANATION: The following format field descriptors are extensions
to FORTRAN-77:
$,O,Z All forms
A,L,I,F,E,G,D Default field width forms
P Without scale factor
1.90 - EXT_INTREQ
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Integer expression required EXPLANATION: One of the following items was not of type integer: o A logical unit number o The record specifier, REC=recspec o The arithmetic expression of a computed GOTO statement o The RETURN [I] o A subscript expression o Array dimension bounds o Character substring bounds expressions
1.91 - EXT_INVINTARG
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Nonstandard use of intrinsic function as actual argument EXPLANATION: The FORTRAN-77 standard does not permit the use of type conversion (INT, DBLE, etc.), lexical relationship (LGE, LGT, etc.), or minimum or maximum functions (MIN, MAX, etc.) as actual arguments.
1.92 - EXT_KEY
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: nonstandard keyword EXPLANATION: A nonstandard keyword was used.
1.93 - EXT_KEYCONF
SEVERITY: I
MESSAGE TEXT: Extension to FORTRAN-77: nonstandard combination of
keywords/values
EXPLANATION: A statement included a nonstandard combination of
keywords or keyword values, for example:
o In an OPEN statement, FILE= specified when STATUS='SCRATCH'
1.94 - EXT_LEX
SEVERITY: I
MESSAGE TEXT: Extension to FORTRAN-77: nonstandard lexical item
EXPLANATION: One of the following nonstandard lexical items was
used:
o An alternate return specifier with an ampersand (&) in a CALL
statement
o The apostrophe (') form of record specifier in a direct access
I/O statement
o A variable format expression
1.95 - EXT_LOGREQ
SEVERITY: I
MESSAGE TEXT: Extension to FORTRAN-77: Logical expression
required
EXPLANATION: One of the following syntax extensions was detected:
o A numeric expression was used in a logical IF statement.
o A numeric expression was used in a block IF statement.
o A value other than .TRUE. or .FALSE. was assigned to a
logical variable.
o A logical variable was initialized with a nonlogical value by
means of a DATA statement.
1.96 - EXT_NAME
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: nonstandard name EXPLANATION: A name longer than six characters or containing a dollar sign ($) or an underscore (_) was used.
1.97 - EXT_OPER
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: nonstandard operator EXPLANATION: The operators .XOR., %VAL, %REF, %DESCR, and %LOC are extensions to FORTRAN-77. The standard form of .XOR. is .NEQV. The % operators are extensions provided to allow access to non-Fortran parts of the VMS environment.
1.98 - EXT_RETTYP
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: Nonstandard function return type EXPLANATION: One of the following conditions was detected: o The function was not declared with a standard data type. o The entry point was not declared with a standard data type.
1.99 - EXT_SOURC
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: tab indentation or lowercase source EXPLANATION: The use of tab indention or lowercase letters in source code is an extension to FORTRAN-77.
1.100 - EXT_STMT
SEVERITY: I MESSAGE TEXT: Extension to FORTRAN-77: nonstandard statement type EXPLANATION: A nonstandard statement type was used.
1.101 - EXT_SYN
SEVERITY: I
MESSAGE TEXT: Extension to FORTRAN-77: nonstandard syntax
EXPLANATION: One of the following syntax extensions was specified:
o PARAMETER name = value
Error: Typeless syntax without parentheses
o type name/value/
Error: Data initialization in type declaration
o DATA (ch(exp:exp),v=e2)/values/
Error: Substring initialization with implied-DO in
DATA statement
o CHARACTER FUNCTION NAME*n
Error: Character function length after name
o INCLUDE '(module)'
Error: Library-based INCLUDE (only if /STANDARD=MIA)
o CALL name(arg2,,arg3)
Error: Null actual argument
o READ (...),iolist
Error: Comma between I/O control and element lists
o PARAMETER (name2=ABS(name1))
Error: Function use in PARAMETER
o e1 ** -e2
Error: Two consecutive operators
1.102 - EXT_TYPE
SEVERITY: I
MESSAGE TEXT: Extension to FORTRAN-77; nonstandard data type
specification
EXPLANATION: The following DATA type specifications are extensions
to FORTRAN-77. The FORTRAN-77 equivalent is given where available.
This message is issued when these types are used in the IMPLICIT
statement or in a numeric type statement.
Extension Standard
--------- --------
BYTE -
LOGICAL*1 -
LOGICAL*2 LOGICAL (with /NOI4 specified only)
LOGICAL*4 LOGICAL
INTEGER*1 -
INTEGER*2 INTEGER (with /NOI4 specified only)
INTEGER*4 INTEGER
REAL*4 REAL
REAL*8 DOUBLE PRECISION
REAL*16 -
COMPLEX*8 COMPLEX
COMPLEX*16 -
DOUBLE COMPLEX -
1.103 - FEANOTSUP
SEVERITY: E MESSAGE TEXT: Feature not supported on this platform EXPLANATION: Detected a language feature supported on other Compaq Fortran platforms that is not suported on this platform.
1.104 - FEAUNSAXP
SEVERITY: W MESSAGE TEXT: Feature not supported on Alpha systems EXPLANATION: Detected a language feature supported on this platform that is not supported on Alpha systems.
1.105 - FLDMISALN
SEVERITY: W MESSAGE TEXT: Record contains one or more misaligned fields EXPLANATION: One or more fields are not naturally aligned in a RECORD structure. If the record is or contains a record array, one or more of the array elements may not be naturally aligned. Specifying /NOALIGN or /ALIGN=RECORDS=PACKED, the default, causes Compaq Fortran to pack the fields within records instead of naturally aligning them. USER ACTION: Consider specifying the /ALIGN qualifier or rearrange fields so that they fall on natural boundaries.
1.106 - FLDNAME
SEVERITY: F MESSAGE TEXT: Structure field is missing a field name EXPLANATION: Unnamed fields are not allowed. The effect of an unnamed field can be achieved by using %FILL in place of a field name in a typed data declaration.
1.107 - FMTEXTCOM
SEVERITY: W MESSAGE TEXT: Extra comma in format list EXPLANATION: A format list contained an extra comma. Example: FORMAT(I4,)
1.108 - FMTEXTNUM
SEVERITY: E MESSAGE TEXT: Extra number in format list EXPLANATION: A format list contained an extraneous number. Example: FORMAT (I4,3)
1.109 - FMTINVCHA
SEVERITY: E MESSAGE TEXT: Format item contains meaningless character EXPLANATION: An invalid character or a syntax error was detected in a FORMAT statement.
1.110 - FMTINVCON
SEVERITY: E MESSAGE TEXT: Constant in format item out of range EXPLANATION: A numeric value in a FORMAT statement exceeds the allowable range. For information about range limits, see the DEC Fortran Language Reference Manual.
1.111 - FMTMISNUM
SEVERITY: E MESSAGE TEXT: Missing number in format list EXPLANATION: An expected number was missing from a format list. Example: FORMAT (F6.)
1.112 - FMTMISSEP
SEVERITY: E MESSAGE TEXT: Missing separator between format items EXPLANATION: A required separator character was omitted between fields in a FORMAT statement.
1.113 - FMTNEST
SEVERITY: E MESSAGE TEXT: Format groups nested too deeply EXPLANATION: Format groups cannot be nested beyond eight levels.
1.114 - FMTPAREN
SEVERITY: E MESSAGE TEXT: Unbalanced parentheses in format list EXPLANATION: The number of right parentheses does not match the number of left parentheses.
1.115 - FMTSIGN
SEVERITY: E MESSAGE TEXT: Format item cannot be signed EXPLANATION: A signed constant is valid only with the P format code.
1.116 - FUNVALUND
SEVERITY: W MESSAGE TEXT: Function value undefined at end of routine EXPLANATION: A function did not have its return value defined at the end of the routine.
1.117 - HOLCOURED
SEVERITY: E MESSAGE TEXT: Count of Hollerith or Radix-50 constant too large, reduced EXPLANATION: The value specified by the integer preceding the H or R was greater than the number of characters remaining in the source statement.
1.118 - IDOINVOP
SEVERITY: F
MESSAGE TEXT: Invalid operation in implied-DO list
EXPLANATION: An invalid operation was attempted in an implied-DO
list in a DATA statement; for example, a function reference in the
subscript or substring expression of an array or character
substring reference.
Example:
DATA (A(SIN(REAL(I))), I=1,10) /101./
1.119 - IDOINVPAR
SEVERITY: F MESSAGE TEXT: Invalid DO parameters in implied-DO list EXPLANATION: An invalid control parameter was detected in an implied-DO list in a DATA statement; for example, an increment of zero.
1.120 - IDOINVREF
SEVERITY: F
MESSAGE TEXT: Invalid reference to name in implied-DO list
EXPLANATION: A control parameter expression in an implied-DO list
in a DATA statement contained a name that was not the name of a
control variable within the scope of any implied-DO list. Example:
DATA (A(J), J=1,10),(B(I), I=J,K) /1001./
Both J and K in the second implied-DO list are invalid names.
1.121 - IDOSYNERR
SEVERITY: F MESSAGE TEXT: Syntax error in implied-DO list in data initialization EXPLANATION: Improper syntax was detected in an implied-DO list in data initialization; for example, improperly nested parentheses.
1.122 - ILDIRSPEC
SEVERITY: I MESSAGE TEXT: Unrecognized directive ignored EXPLANATION: A directive with a valid Compaq Fortran prefix was encountered in the first 5 columns of a source code statement (such as a Compaq Fortran vector directive), but its presence in the context of the specified command qualifiers is inconsistent or the keyword following the prefix (such as CDEC$ or CPAR$) was not recognized.
1.123 - ILDOPARCTL
SEVERITY: F MESSAGE TEXT: Illegal parallel DO-loop, control variable must be declared INTEGER EXPLANATION: Only integer control variables can be used with parallel DO loops.
1.124 - ILDOPARDIR
SEVERITY: E MESSAGE TEXT: DO_PARALLEL directive must be followed by DO statement, directive ignored EXPLANATION: The first executable statement after a DO_PARALLEL compiler directive statement (CPAR$ DO_PARALLEL) must be a DO statement.
1.125 - ILIDFDIR
SEVERITY: W MESSAGE TEXT: Loop directive must be followed by DO statement EXPLANATION: A CDEC$ directive that applies to DO loops was found but no DO loop was found within its range.
1.126 - ILLBRANCH
SEVERITY: E MESSAGE TEXT: Illegal branch into or out of parallel DO-loop EXPLANATION: A branch into or out of a parallel DO loop is not allowed.
1.127 - ILPARSTMT
SEVERITY: E MESSAGE TEXT: Statement not permitted inside parallel DO-loop EXPLANATION: I/O statements and RETURN, STOP, and PAUSE statements are not permitted inside a parallel DO-loop.
1.128 - IMPDECLAR
SEVERITY: W MESSAGE TEXT: Use of implicit with declaration warnings EXPLANATION: An IMPLICIT statement was used in a program compiled with the /WARNINGS=DECLARATIONS qualifier on the FORTRAN command line.
1.129 - IMPMULTYP
SEVERITY: E MESSAGE TEXT: Letter mentioned twice in IMPLICIT statement, last type used EXPLANATION: A letter was given an implicit data type more than once. The last data type given is used.
1.130 - IMPNONE
SEVERITY: E
MESSAGE TEXT: Untyped name, must be explicitly typed
EXPLANATION: The displayed name was not defined in any data type
declaration statement, and an IMPLICIT NONE statement was
specified. Check that the name was not accidentally created by an
undetected syntax error. Example:
DO 10 I = 1.10
The apparent DO statement is really an assignment to the
accidentally created variable DO10I.
1.131 - IMPSYNERR
SEVERITY: E MESSAGE TEXT: Syntax error in IMPLICIT statement EXPLANATION: Improper syntax was used in an IMPLICIT statement.
1.132 - INCDONEST
SEVERITY: F
MESSAGE TEXT: DO or IF statement incorrectly nested
EXPLANATION: One of the following conditions occurred:
o A statement label specified in a DO statement was used
previously. Example:
10 I = I + 1
J = J + 1
DO 10 K=1,10
o A DO loop contains an incomplete DO loop or IF block.
Examples:
1. DO 10 I=1,10
J = J + 1
DO 20 K=1,10
J = J + K
10 CONTINUE
The start of the incomplete IF block can be a block IF, ELSE
IF, or ELSE statement.
2. DO 10 I=1,10
J = J + I
IF (J .GT. 20) THEN
J = J - 1
ELSE
J = J + 1
10 CONTINUE
END IF
1.133 - INCFILNES
SEVERITY: F MESSAGE TEXT: INCLUDE files and/or DICTIONARY statements nested too deeply EXPLANATION: Up to 10 levels of nested INCLUDE files and DICTIONARY statements are permitted.
1.134 - INCFUNTYP
SEVERITY: F
MESSAGE TEXT: Inconsistent function data types
EXPLANATION: The function name and entry points in a function
subprogram must be consistent within one of three groups of data
types:
Group 1: All numeric types except REAL*16 and COMPLEX*16
Group 2: REAL*16 and COMPLEX*16
Group 3: Character
Example:
CHARACTER*15 FUNCTION I
REAL*4 G
ENTRY G
1.135 - INCLABUSE
SEVERITY: F
MESSAGE TEXT: Inconsistent usage of statement label
EXPLANATION: Labels of executable statements were confused with
labels of FORMAT statements or with labels of nonexecutable
statements. Example:
GO TO 10
10 FORMAT (I5)
1.136 - INCLENMOD
SEVERITY: F
MESSAGE TEXT: Incorrect length modifier in declaration
EXPLANATION: An unacceptable length was specified in a data type
declaration. For example:
INTEGER PIPES*8
1.137 - INCMODNAM
SEVERITY: F
MESSAGE TEXT: Module name not found in library
EXPLANATION: When an INCLUDE statement of the form INCLUDE
'(module)' is used, several text libraries are searched for the
specified module name. These are, in order:
1. Libraries specified on the FORTRAN command line
with the /LIBRARY qualifier
2. The library specified using the logical name
FORT$LIBRARY
3. The Compaq Fortran system text library,
SYS$LIBRARY:FORSYSDEF.
The INCMODNAM message is issued when the specified module name
cannot be found in any of the libraries. Note that one of the
causes of this search failure may be an open failure on one of the
libraries. If a "$LIBRARY/LIST" command shows the module to be
present in the library, check to ensure that the library itself can
be read by the compiler.
1.138 - INCNOTSUP
SEVERITY: F MESSAGE TEXT: INCLUDE not supported for current source file device EXPLANATION: An INCLUDE statement was found while the current source device was not random-access, for example a tape drive or a terminal. The compiler requires that it be able to close and later reopen and reposition the source file before processing an INCLUDE statement.
1.139 - INCOPEFAI
SEVERITY: F MESSAGE TEXT: Open failure on INCLUDE file EXPLANATION: The specified file could not be opened, possibly because of an incorrect file specification, nonexistent file, unmounted volume, or protection violation.
1.140 - INCOPNFORT
SEVERITY: W MESSAGE TEXT: Unable to open text library defined by FORT$LIBRARY EXPLANATION: In an attempt to include a text library, the compiler was unable to open the text library defined by the logical name FORT$LIBRARY.
1.141 - INCOPNSYSL
SEVERITY: W MESSAGE TEXT: Open error opening include file SYS$LIBRARY:FORSYSDEF.TLB EXPLANATION: In an attempt to include a module from Compaq Fortran's symbolic definition library (FORSYSDEF), the compiler was unable to locate the library. (FORSYSDEF contains Compaq Fortran source definitions for related groups of system symbols.)
1.142 - INCSTAFUN
SEVERITY: W MESSAGE TEXT: Inconsistent statement function reference EXPLANATION: The actual arguments in a statement function reference did not agree in either order, number, or data type with the formal arguments declared.
1.143 - INCSYNERR
SEVERITY: F MESSAGE TEXT: Syntax error in INCLUDE file specification EXPLANATION: The file-name string was not acceptable (invalid syntax, invalid qualifier, undefined device, and so on).
1.144 - INQUNIT
SEVERITY: F MESSAGE TEXT: Missing or invalid use of UNIT or FILE specifier in INQUIRE statement EXPLANATION: An INQUIRE statement must have a UNIT specifier or a FILE specifier, but not both.
1.145 - INSVIRMEM
SEVERITY: F MESSAGE TEXT: Insufficient virtual memory to complete compilation EXPLANATION: The compiler was not able to acquire sufficient virtual memory to complete the compilation. USER ACTION: Increase your process page file quota (AUTHORIZE quota PGFLQUO) and/or the system virtual page count limit (SYSGEN parameter VIRTUALPAGECNT), specify the /NOOPTIMIZE compiler command qualifier, or reduce the size or complexity of the compilation unit.
1.146 - INTACTARG
SEVERITY: W MESSAGE TEXT: Intrinsic routine used as actual argument should be named in INTRINSIC statement EXPLANATION: An identifier which had been previously used as an intrinsic routine was used as an actual argument, but was not named in an INTRINSIC statement. The compiler assumed that the intrinsic routine of that name was intended. USER ACTION: If the identifier is intended to be a routine name, declare it in an EXTERNAL or INTRINSIC statement, as appropriate. This message can be suppressed with /WARNINGS=NOUSAGE.
1.147 - INTFUNARG
SEVERITY: E MESSAGE TEXT: Arguments incompatible with intrinsic function, assumed EXTERNAL EXPLANATION: A function reference was made using an intrinsic function name, but the argument list does not agree in order, number, or type with the intrinsic function requirements. When this error occurs, the function is assumed to be supplied by you as an EXTERNAL function.
1.148 - INTVALREQ
SEVERITY: F MESSAGE TEXT: Non-integer expression where integer value required EXPLANATION: An expression that must be of type integer was another data type.
1.149 - INVACTARG
SEVERITY: E MESSAGE TEXT: Invalid use of intrinsic function name as actual argument EXPLANATION: A generic name of an intrinsic function was used as an actual argument.
1.150 - INVASSVAR
SEVERITY: E MESSAGE TEXT: Invalid ASSOCIATEVARIABLE specification EXPLANATION: An ASSOCIATEVARIABLE specification in an OPEN or DEFINE FILE statement was a dummy argument or an array element.
1.151 - INVCHASOU
SEVERITY: W MESSAGE TEXT: Invalid character treated as blank EXPLANATION: A nonprinting character was found in a source line and was replaced by a space (blank) character. The value of the last nonprinting character found in a source line appears within the message in the form [CHAR(nnn)], where nnn is the decimal value of the nonprinting character. For more information on valid nonprinting characters in source files, see your user manual.
1.152 - INVCHAUSE
SEVERITY: E
MESSAGE TEXT: Invalid character used in constant
EXPLANATION: An invalid character was used in a constant. Valid
characters are:
Hexadecimal: 0 - 9, A - F, a - f
Octal: 0 - 7
Binary: 0 - 1
Radix-50: A - Z, 0 - 9, $, period, or space
For Radix-50, a space is substituted for the invalid character.
For hexadecimal and octal, the entire constant is set to zero.
1.153 - INVCONST
SEVERITY: E MESSAGE TEXT: Arithmetic error while evaluating constant or constant expression EXPLANATION: The specified value of a constant was too large or too small to be represented.
1.154 - INVCONSTR
SEVERITY: F
MESSAGE TEXT: Invalid control structure using ELSE IF, ELSE, or
END IF
EXPLANATION: The order of ELSE IF, ELSE, or END IF statements is
incorrect.
ELSE IF, ELSE, and END IF statements cannot stand alone. ELSE IF
and ELSE must be preceded by either a block IF statement or an ELSE
IF statement. END IF must be preceded by either a block IF, ELSE
IF, or ELSE statement. Examples:
1. DO 10 I=1,10
J = J + I
ELSE IF (J .LE. K) THEN
Error: ELSE IF preceded by a DO statement.
2. IF (J .LT. K) THEN
J = I + J
ELSE
J = I - J
ELSE IF (J .EQ. K) THEN
END IF
Error: ELSE IF preceded by an ELSE statement.
1.155 - INVDEVSPE
SEVERITY: E MESSAGE TEXT: Invalid device specified, analysis data file not produced EXPLANATION: The file specified by the /ANALYSIS_DATA qualifier could not be written because it was not a random access file.
1.156 - INVDOTERM
SEVERITY: W MESSAGE TEXT: Statement cannot terminate a DO loop EXPLANATION: The terminal statement of a DO loop cannot be a GO TO, arithmetic IF, block IF, RETURN, ELSE, ELSE IF, END IF, DO, or END statement.
1.157 - INVDUMARG
SEVERITY: E MESSAGE TEXT: Dummy argument invalid in parallel memory directive EXPLANATION: Dummy arguments cannot be specified on a parallel memory directive.
1.158 - INVENDKEY
SEVERITY: W MESSAGE TEXT: Invalid END= keyword, ignored EXPLANATION: The END keyword was used illegally in a WRITE, REWRITE, direct access READ, or keyed access READ statement.
1.159 - INVENTRY
SEVERITY: E MESSAGE TEXT: ENTRY within DO loop or IF block, statement ignored EXPLANATION: An ENTRY statement is not allowed within the range of a DO loop or IF block.
1.160 - INVEQVCOM
SEVERITY: F MESSAGE TEXT: Invalid equivalence of two variables in common EXPLANATION: Variables in common blocks cannot be equivalenced to each other.
1.161 - INVFUNUSE
SEVERITY: F
MESSAGE TEXT: Invalid use of function name in CALL statement
EXPLANATION: A CALL statement referred to a subprogram name that
was used as a CHARACTER, REAL*16, or COMPLEX*16 function. Example:
IMPLICIT CHARACTER*10(C)
CSCAL = CFUNC(X)
CALL CFUNC(X)
1.162 - INVINIVAR
SEVERITY: E MESSAGE TEXT: Invalid initialization of variable not in common EXPLANATION: An attempt was made in a BLOCK DATA subprogram to initialize a variable that was not in a common block.
1.163 - INVINTFUN
SEVERITY: E MESSAGE TEXT: Name used in INTRINSIC statement is not an intrinsic function EXPLANATION: A function name which appeared in the INTRINSIC statement was not an intrinsic function.
1.164 - INVIOSPEC
SEVERITY: F MESSAGE TEXT: Invalid I/O specification for this type of I/O statement EXPLANATION: A syntax error occurred in the portion of an I/O statement that precedes the I/O list. Examples: 1. TYPE (6), J 2. WRITE 100, J
1.165 - INVKEYOPE
SEVERITY: F MESSAGE TEXT: Incorrect keyword in OPEN, CLOSE, or INQUIRE statement EXPLANATION: An OPEN, CLOSE, or INQUIRE statement contained an invalid keyword.
1.166 - INVLEFSID
SEVERITY: F MESSAGE TEXT: Left side of assignment must be variable or array element EXPLANATION: The symbolic name to which the value of an expression is assigned must be a variable, array element, or character substring reference.
1.167 - INVLEXEME
SEVERITY: F MESSAGE TEXT: Variable name, constant, or expression invalid in this context EXPLANATION: An entity was used incorrectly; for example, the name of a subprogram was used where an arithmetic expression was required.
1.168 - INVLOGIF
SEVERITY: F MESSAGE TEXT: Statement cannot appear in logical IF statement EXPLANATION: A logical IF statement must not contain a DO statement or another logical IF, IF THEN, ELSE IF, ELSE, END IF, or END statement.
1.169 - INVNMLELE
SEVERITY: F MESSAGE TEXT: Invalid namelist element EXPLANATION: An element other than a variable or array name appeared in a namelist declaration.
1.170 - INVNUMSUB
SEVERITY: F MESSAGE TEXT: Number of subscripts does not match array declaration EXPLANATION: More or fewer dimensions than were declared for the array were referenced.
1.171 - INVPERARG
SEVERITY: F
MESSAGE TEXT: Invalid argument to %VAL, %REF, %DESCR, or %LOC
EXPLANATION: The argument specified for one of the built-in
functions was not valid. Examples:
%VAL (3.5D0) Error: Argument cannot be REAL*8,
REAL*16, character, or complex.
%LOC (X+Y) Error: Argument must not be an expression.
1.172 - INVPERUSE
SEVERITY: E
MESSAGE TEXT: %VAL, %REF, or %DESCR used in invalid context
EXPLANATION: The argument list built-in functions (%VAL, %REF, and
%DESCR) cannot be used outside an actual argument list. Example:
X = %REF(Y)
1.173 - INVQUAL
SEVERITY: I MESSAGE TEXT: Invalid qualifier or qualifier value in OPTIONS statement EXPLANATION: An invalid qualifier or qualifier value was specified in the OPTIONS statement. When this error occurs, the qualifier is ignored.
1.174 - INVRECUSE
SEVERITY: F
MESSAGE TEXT: Invalid use of record or array name
EXPLANATION: A statement in the program violated one of the
following rules:
o An aggregate cannot be assigned to a nonaggregate or to an
aggregate with a structure that is not the same.
o An array name reference cannot be qualified.
o Aggregate references cannot be used in I/O lists of formatted
I/O statements.
o An aggregate or array cannot be passed as an expression in an
actual argument list.
1.175 - INVREPCOU
SEVERITY: E MESSAGE TEXT: Invalid repeat count in data initialization, count ignored EXPLANATION: The repeat count in a data initialization was not an unsigned, nonzero integer constant. When this error occurs, the count is ignored.
1.176 - INVSBSREF
SEVERITY: E
MESSAGE TEXT: Substring reference used in invalid context
EXPLANATION: A substring reference was made to a variable or array
that is not of type CHARACTER. Example:
REAL X(10)
Y = X(J:K)
1.177 - INVSTALAB
SEVERITY: W MESSAGE TEXT: Invalid statement label ignored EXPLANATION: An improperly formed statement label (namely, a label containing letters) appeared in columns 1 to 5 of an initial line. When this error occurs, the statement label is ignored.
1.178 - INVSUBREF
SEVERITY: F MESSAGE TEXT: Subscripted reference to non-array variable EXPLANATION: A variable that is not defined as an array cannot appear with subscripts.
1.179 - INVTYPUSE
SEVERITY: F MESSAGE TEXT: Name previously used with conflicting data type EXPLANATION: A data type was assigned to a name that had already been used in a context that required a different data type.
1.180 - IODUPKEY
SEVERITY: F MESSAGE TEXT: Duplicated keyword in I/O statement EXPLANATION: Each keyword subparameter in an I/O statement or auxiliary I/O statement can be specified only once.
1.181 - IOINVFMT
SEVERITY: F
MESSAGE TEXT: Format specifier in error
EXPLANATION: The format specifier in an I/O statement is invalid.
It must be one of the following:
o The label of a FORMAT statement.
o An asterisk (*) in a list-directed I/O statement.
o A run-time format specifier: a variable, array element, or
character substring reference.
o An integer variable that was assigned a FORMAT label by an
ASSIGN statement.
1.182 - IOINVKEY
SEVERITY: F MESSAGE TEXT: Invalid keyword for this type of I/O statement EXPLANATION: An I/O statement contained a keyword that cannot be used with that type of I/O statement.
1.183 - IOINVLIST
SEVERITY: F MESSAGE TEXT: Invalid I/O list element for input statement EXPLANATION: An input statement I/O list contained an invalid element, such as an expression or a constant.
1.184 - IOSYNERR
SEVERITY: F MESSAGE TEXT: Syntax error in I/O list EXPLANATION: Improper syntax was detected in an I/O list.
1.185 - LABASSIGN
SEVERITY: F MESSAGE TEXT: Label in ASSIGN statement exceeds INTEGER*2 range EXPLANATION: A label whose value is assigned to an INTEGER*2 variable by an ASSIGN statement must not be separated by more than 32K bytes from the beginning of the code for the program unit.
1.186 - LENCHAFUN
SEVERITY: E
MESSAGE TEXT: Length specified must match CHARACTER FUNCTION
declaration
EXPLANATION: The length specifications for all ENTRY names in a
character function subprogram must be the same. Example:
CHARACTER*15 FUNCTION F
CHARACTER*20 G
ENTRY G
1.187 - LOGVALREQ
SEVERITY: F MESSAGE TEXT: Non-logical expression where logical value required EXPLANATION: An expression that must be of type LOGICAL was of another data type.
1.188 - LOG4LCKREQ
SEVERITY: E MESSAGE TEXT: Lock variable must be declared LOGICAL*4 EXPLANATION: The lock entity used in a LOCKON or LOCKOFF directive must be declared to be LOGICAL*4.
1.189 - LOWBOUGRE
SEVERITY: E MESSAGE TEXT: Lower bound greater than upper bound in array declaration EXPLANATION: The upper bound of a dimension declarator must be equal to or greater than the lower bound.
1.190 - LSEDIAGS
SEVERITY: I MESSAGE TEXT: Additional diagnostics written to LSE diagnostics file EXPLANATION: Additional data dependence diagnostics were written to the DEC Language-Sensitive Editor diagnostics file and can be reviewed in the editor.
1.191 - MINDIGITS
SEVERITY: I MESSAGE TEXT: CDD description specifies precision less than allowed for data type. Minimum precision is supplied. EXPLANATION: Some Common Data Dictionary data types specified a number of digits that is incompatible with Compaq Fortran data types. When this error occurs, the Compaq Fortran compiler expands the data type to conform to a Compaq Fortran data type.
1.192 - MINOCCURS
SEVERITY: I MESSAGE TEXT: CDD description contains Minimum Occurs attribute (ignored) EXPLANATION: Compaq Fortran does not support the Common Data Dictionary Minimum Occurs attribute.
1.193 - MISSAPOS
SEVERITY: E MESSAGE TEXT: Missing apostrophe in character constant EXPLANATION: A character constant must be enclosed by apostrophes.
1.194 - MISSCOM
SEVERITY: F MESSAGE TEXT: Missing common block name EXPLANATION: A common block name was omitted or specified improperly on a SHARED directive.
1.195 - MISSCONST
SEVERITY: F MESSAGE TEXT: Missing constant EXPLANATION: A required constant was not found.
1.196 - MISSDEL
SEVERITY: F
MESSAGE TEXT: Missing operator or delimiter symbol
EXPLANATION: Two terms of an expression were not separated by an
operator, or a punctuation mark (such as a comma) was omitted.
Examples:
CIRCUM = 3.14 DIAM
IF (I 10,20,30
1.197 - MISSEND
SEVERITY: E MESSAGE TEXT: Missing END statement, END is assumed EXPLANATION: An END statement was missing at the end of the last input file. When this error occurs, an END statement is inserted.
1.198 - MISSEXPO
SEVERITY: E MESSAGE TEXT: Missing exponent after E, D, or Q EXPLANATION: A floating-point constant was specified in E, D, or Q notation, but the exponent was omitted.
1.199 - MISSKEY
SEVERITY: F MESSAGE TEXT: Missing keyword EXPLANATION: A required keyword, such as TO, was omitted from a statement such as ASSIGN 10 TO I.
1.200 - MISSLABEL
SEVERITY: F MESSAGE TEXT: Missing statement label EXPLANATION: A required statement label reference was omitted.
1.201 - MISSNAME
SEVERITY: F MESSAGE TEXT: Missing variable or subprogram name EXPLANATION: A required variable name or subprogram name was not found.
1.202 - MISSUNIT
SEVERITY: F MESSAGE TEXT: Unit specifier keyword missing in I/O statement EXPLANATION: An I/O statement must include a unit specifier subparameter.
1.203 - MISSVAR
SEVERITY: F
MESSAGE TEXT: Missing variable or constant
EXPLANATION: An expression, or a term of an expression, was
omitted. Examples:
WRITE ( )
DIST = *TIME
1.204 - MISSVARCOM
SEVERITY: E MESSAGE TEXT: Missing variable or common name EXPLANATION: A name of a variable or a common block that is required by a compiler directive statement or a VOLATILE statement was omitted.
1.205 - MULDECNAM
SEVERITY: F MESSAGE TEXT: Multiple declaration of name EXPLANATION: A name appeared in two or more inconsistent declaration statements or a dummy argument was specified in an EQUIVALENCE statement.
1.206 - MULDECTYP
SEVERITY: E MESSAGE TEXT: Multiple declaration of data type for variable, first type used EXPLANATION: A variable appeared in more than one data type declaration statement. When this error occurs, the first type declaration is used.
1.207 - MULDEFLAB
SEVERITY: E MESSAGE TEXT: Multiple definition of statement label, second ignored EXPLANATION: The same label appeared on more than one statement. When this error occurs, the first occurrence of the label is used.
1.208 - MULFLDNAM
SEVERITY: F MESSAGE TEXT: Multiply defined field name EXPLANATION: Each field name within the same level of a given structure declaration must be unique.
1.209 - MULSPEPAR
SEVERITY: E MESSAGE TEXT: Multiple specification of parallel memory attributes, first specification used EXPLANATION: A variable, array, record, or COMMON block was a given memory attributes (shared and private or context-shared and private) in a parallel directive. When this error occurs, the first attribute specified is the one that is used.
1.210 - MULSTRNAM
SEVERITY: F MESSAGE TEXT: Multiply defined STRUCTURE name EXPLANATION: A STRUCTURE name must be unique among STRUCTURE names.
1.211 - NAMTOOLON
SEVERITY: W MESSAGE TEXT: Name longer than 31 characters EXPLANATION: A symbolic name cannot exceed 31 characters. When this error occurs, the symbolic name is truncated to 31 characters.
1.212 - NESTPARDO
SEVERITY: E MESSAGE TEXT: Nested parallel DO-loops not permitted, directive ignored EXPLANATION: A parallel DO-loop directive (CPAR$ DO_PARALLEL) was detected within a DO-loop that was already marked as parallel. Nested parallel DO-loop directives are not supported.
1.213 - NMLIOLIST
SEVERITY: E MESSAGE TEXT: I/O list not permitted with namelist I/O EXPLANATION: An I/O statement with a namelist specifier incorrectly contained an I/O list.
1.214 - NODEPCOMMN
SEVERITY: I MESSAGE TEXT: Dependence analysis inhibited due to call in DO-loop and COMMON loop control variable EXPLANATION: Dependence analysis is not performed on DO-loops that have a control variable specified within a COMMON block and a reference to an external routine. The analysis is not done because of the potential for changing the control variable in the external routine.
1.215 - NODEPDEEP
SEVERITY: I MESSAGE TEXT: Dependence analysis inhibited due to more than 7 loops nested inside DO-loop EXPLANATION: Dependence analysis is not performed on DO-loops that have more than seven levels of nesting.
1.216 - NODEPEQUIV
SEVERITY: I MESSAGE TEXT: Dependence analysis inhibited due to EQUIVALENCEd loop control variable EXPLANATION: Dependence analysis is not performed on DO-loops that have a control variable that is also specified in an EQUIVALENCE statement.
1.217 - NODEPFLOW
SEVERITY: I MESSAGE TEXT: Dependence analysis inhibited due to transfer into or out of DO-loop EXPLANATION: Dependence analysis is not performed on DO-loops that contain transfers into or out of the loop. A STOP or RETURN is considered as a transfer out of a DO-loop.
1.218 - NODEPINT4
SEVERITY: I MESSAGE TEXT: Dependence analysis inhibited due to non-integer control variable EXPLANATION: Dependence analysis is not performed on DO-loops that have a non-integer control variable. (Note - INTEGER*2 is now allowed.)
1.219 - NODEPNEST
SEVERITY: I MESSAGE TEXT: Dependence analysis inhibited due to inhibitor in loop nested inside DO-loop EXPLANATION: Dependence analysis is not performed on DO-loops that contain a nested DO-loop with inhibitors.
1.220 - NODEPOVLP
SEVERITY: I MESSAGE TEXT: Dependence analysis inhibited due to potential overlap dummy arguments and common variables in DO-loop EXPLANATION: Dependence analysis is not performed on DO-loops that contain references and stores into dummy arguments and variables in a common block. The potential for dummy arguments and variables in common blocks being aliased is the reason for this inhibitor. This error is partially controlled by the setting of the /ASSUME=[NO]DUMMY_ALIASES qualifier.
1.221 - NODEPPAR
SEVERITY: I MESSAGE TEXT: Dependence analysis inhibited due to parallel loop nested inside DO-loop EXPLANATION: Dependence analysis is not performed on DO-loops that contain a nested parallel DO-loop that was established by a compiler directive statement (directed decomposition).
1.222 - NODEPSTMT
SEVERITY: I
MESSAGE TEXT: Dependence analysis inhibited due to use of
inhibitor statement inside DO-loop
EXPLANATION: Dependence analysis is not performed on DO-loops that
contain any of the following statements:
o An assigned GOTO
o A computed GOTO
o A character function invocation
o A LOCKON or LOCKOFF directive
o A format containing a variable format expression was referenced
in an I/O statement within the DO-loop
1.223 - NODEPVOLAT
SEVERITY: I MESSAGE TEXT: Dependence analysis inhibited due to volatile control variable EXPLANATION: Dependence analysis is not performed on DO-loops that have a control variable that is declared volatile.
1.224 - NODFLOAT
SEVERITY: W MESSAGE TEXT: CDD description specifies the D_floating data type. The data cannot be represented when compiling /G_FLOAT. EXPLANATION: A D_floating data type was specified when compiling with the /G_FLOATING qualifier. Ignore the warning message or recompile the program using the /NOG_FLOATING qualifier.
1.225 - NOGFLOAT
SEVERITY: W MESSAGE TEXT: CDD description specifies G_floating data type. The data cannot be represented when compiling /NOG_FLOAT. EXPLANATION: A G_floating data type was specified when compiling with the /NOG_FLOATING qualifier. Ignore the warning message or recompile the program using the /G_FLOAT qualifier.
1.226 - NONCONSUB
SEVERITY: F MESSAGE TEXT: Nonconstant subscript where constant required EXPLANATION: Subscript and substring expressions used in DATA and EQUIVALENCE statements must be constants.
1.227 - NOPATH
SEVERITY: W
MESSAGE TEXT: No path to this statement
EXPLANATION: Program control cannot reach this statement. When
this error occurs, the statement is deleted. Example:
10 I = I + 1
GO TO 10
STOP
1.228 - NOPPARVEC
SEVERITY: W MESSAGE TEXT: /NOOPTIMIZE conflicts /PARALLEL=AUTOMATIC or /VECTOR EXPLANATION: When you specify /PARALLEL=AUTOMATIC or /VECTOR, you must omit /NOOPTIMIZE.
1.229 - NOSOUFILE
SEVERITY: F MESSAGE TEXT: No source file specified EXPLANATION: A command line was entered that specified only library file names and no source files to compile.
1.230 - NOTINLINED
SEVERITY: I MESSAGE TEXT: Intrinsic reference was not expanded inline EXPLANATION: The reference to a BLAS intrinsic routine could not be expanded into inline code.
1.231 - NOVECACCU
SEVERITY: I MESSAGE TEXT: Vectorization inhibition: Qualifier /ASSUME=ACCURACY prevents recurrence vectorization EXPLANATION: Vectorization is not performed. The /ASSUME=ACCURACY_SENSITIVE option prevents recurrence vectorization.
1.232 - NOVECALIGN
SEVERITY: I MESSAGE TEXT: Vectorization inhibition: Misaligned array EXPLANATION: Vectorization is not performed. Data for vector instructions must be aligned on natural boundaries, based on the data type. An array is aligned on natural boundaries if all its elements are so aligned.
1.233 - NOVECDTARR
SEVERITY: I MESSAGE TEXT: Vectorization inhibition: Data type not supported for array EXPLANATION: Vectorization is not performed because the data type is not supported for the array.
1.234 - NOVECDTIND
SEVERITY: I MESSAGE TEXT: Vectorization inhibition: Use of unsupported data type in array index EXPLANATION: Vectorization is not performed because an unsupported data type is used in the array index.
1.235 - NOVECSUBP
SEVERITY: I MESSAGE TEXT: Vectorization inhibition: Reference to subprogram EXPLANATION: Vectorization is not performed for data that can be modified in the subprogram.
1.236 - NOVECVOLARR
SEVERITY: I MESSAGE TEXT: Vectorization inhibition: Use of volatile array EXPLANATION: Vectorization is not performed. Volatile arrays have dependences the compiler is unaware of; thus, they cannot be vectorized.
1.237 - NOVECVOLIND
SEVERITY: I MESSAGE TEXT: Vectorization inhibition: Use of volatile array index EXPLANATION: Vectorization is not performed. The compiler cannot identify all dependences for volatile array indexes; thus, they cannot be vectorized.
1.238 - OPEDOLOOP
SEVERITY: F
MESSAGE TEXT: Unclosed DO loop or IF block
EXPLANATION: The terminal statement of a DO loop or the END IF
statement of an IF block was not found. Example:
DO 20 I=1,10
X = Y
END
1.239 - OPENIN
SEVERITY: F MESSAGE TEXT: Error opening "file-spec" as input EXPLANATION: Unable to open the file "file-spec".
1.240 - OPENOTPER
SEVERITY: F MESSAGE TEXT: Operation not permissible on these data types EXPLANATION: An invalid operation was specified, such as an .AND. of two real variables.
1.241 - OPENOUT
SEVERITY: F MESSAGE TEXT: Error opening "file-spec" as output EXPLANATION: Unable to open the file "file-spec".
1.242 - OPTLV4CHK
SEVERITY: W MESSAGE TEXT: /OPTIMIZE=LEVEL=4 conflicts with /CHECK=BOUNDS; /OPTIMIZE=LEVEL=4 ignored EXPLANATION: When you specify /CHECK=BOUNDS, you cannot use /OPTIMIZE=LEVEL=4. A lower level of optimization has been used.
1.243 - OPTMISSING
SEVERITY: W MESSAGE TEXT: No matching CDEC$ OPTIONS for CDEC$ END OPTIONS EXPLANATION: A CDEC$ END OPTIONS directive terminates a CDEC$ OPTIONS section. USER ACTION: Remove extraneous CDEC$ END OPTIONS directives or add CDEC$ OPTIONS directives as appropriate.
1.244 - PARCHKCON
SEVERITY: W MESSAGE TEXT: /PARALLEL=AUTOMATIC conflicts with /CHECK=BOUNDS EXPLANATION: When you specify /CHECK=BOUNDS, you cannot use /PARALLEL=AUTOMATIC. /PARALLEL=NOAUTOMATIC was used.
1.245 - PLACEEOL
SEVERITY: F MESSAGE TEXT: Placeholder not terminated before end of line EXPLANATION: The closing delimiter of a placeholder was not found before the end of the line.
1.246 - PLACENODESIGN
SEVERITY: E MESSAGE TEXT: Placeholder not valid without /DESIGN=PLACEHOLDERS EXPLANATION: A placeholder was found but /DESIGN=PLACEHOLDERS was not specified on the compile command line.
1.247 - PLACENODOT
SEVERITY: E MESSAGE TEXT: Repetition of pseudocode placeholder not allowed EXPLANATION: A pseudocode placeholder was found with three dots after it, indicating a list placeholder, which is not supported.
1.248 - PLACENOOBJ
SEVERITY: I MESSAGE TEXT: Placeholders detected - no object code generated EXPLANATION: One or more placeholders were found in the current compilation unit and so no object code was generated for that unit.
1.249 - PLACENOTVAL
SEVERITY: E MESSAGE TEXT: Placeholder not valid in this context EXPLANATION: A placeholder was found in a context that is not supported.
1.250 - PROSTOREQ
SEVERITY: F MESSAGE TEXT: Program storage requirements exceed addressable memory EXPLANATION: The storage space allocated to the variables and arrays of the program unit exceeded the addressing range of the machine.
1.251 - PRVCTLVAR
SEVERITY: I MESSAGE TEXT: Control variable for parallel loop defaulting to PRIVATE EXPLANATION: The control variable for a parallel DO loop was not explicitly declared private.
1.252 - PRVSYMIL
SEVERITY: E MESSAGE TEXT: PRIVATE symbol invalid in routine without parallel DO-loop EXPLANATION: Symbols declared within a routine that does not contain a parallel DO loop cannot be listed in a PRIVATE directive.
1.253 - READERR
SEVERITY: F MESSAGE TEXT: Error reading "file-spec" EXPLANATION: Unable to read from file "file-spec".
1.254 - RECPARCON
SEVERITY: W MESSAGE TEXT: /RECURSIVE conflicts with /PARALLEL; /RECURSIVE ignored EXPLANATION: If you specify /PARALLEL, you must omit /RECURSIVE. Compilation uses /PARALLEL but ignores /RECURSIVE.
1.255 - REDCONMAR
SEVERITY: W MESSAGE TEXT: Redundant continuation mark ignored EXPLANATION: A continuation mark was used where an initial line is required. When this error occurs, the continuation mark is ignored.
1.256 - REFERENCE
SEVERITY: I MESSAGE TEXT: CDD description contains Reference attribute (ignored) EXPLANATION: Fortran does not support the CDD Reference attribute.
1.257 - ROUREFREC
SEVERITY: F MESSAGE TEXT: Routine referenced recursively; /RECURSIVE required EXPLANATION: A subroutine, function or entry name was referenced recursively in the same program unit, but the /RECURSIVE command or OPTIONS statement qualifier was not specified.
1.258 - ROWMAJOR
SEVERITY: I MESSAGE TEXT: Bounds reversed for CDD member row-major array EXPLANATION: A row-major multi-dimensioned array was found in a CDD record. The bounds were reversed to allow for Fortran column-major array addressing.
1.259 - SAVPRICONF
SEVERITY: E MESSAGE TEXT: PRIVATE variable or common block must not be declared SAVE EXPLANATION: Symbols cannot be declared in both a SAVE statement and a PRIVATE directive or common block.
1.260 - SHRCTLVAR
SEVERITY: E MESSAGE TEXT: Control variable for parallel DO-loops must be declared PRIVATE EXPLANATION: The control variable for a parallel DO-loop was explicitly declared SHARED. Control variables for parallel DO-loops must be explicitly declared PRIVATE.
1.261 - SHRNAMLON
SEVERITY: E MESSAGE TEXT: Shared COMMON name too long, limited to 26 characters EXPLANATION: The maximum length of a COMMON block name specified in a SHARED compiler directive statement is 26 characters.
1.262 - SOURCETYPE
SEVERITY: I MESSAGE TEXT: CDD description contains Source Type attribute (ignored) EXPLANATION: Compaq Fortran does not support the CDD Source Type attribute.
1.263 - STAENDSTR
SEVERITY: F MESSAGE TEXT: Statement not allowed within structure; structure definition closed EXPLANATION: A statement not allowed in a structure declaration block was encountered. When this error occurs, the compiler assumes that you omitted one or more END STRUCTURE statements.
1.264 - STAINVSTR
SEVERITY: E MESSAGE TEXT: Statement not allowed within structure definition; statement ignored EXPLANATION: A statement not allowed in a structure declaration block was encountered. Structure declaration blocks can only include the following statements: typed data declaration statements, RECORD statements, UNION/END UNION statements, MAP/END MAP statements, and STRUCTURE/END STRUCTURE statements.
1.265 - STANOTVAL
SEVERITY: E MESSAGE TEXT: Statement not valid in this program unit, statement ignored EXPLANATION: A program unit contained a statement that is not allowed; for example, a BLOCK DATA subprogram containing an executable statement.
1.266 - STAOUTORD
SEVERITY: E MESSAGE TEXT: Statement out of order, statement ignored EXPLANATION: A statement was used in a place where it does not belong. When this error occurs, the statement is ignored.
1.267 - STATOOCOM
SEVERITY: F MESSAGE TEXT: Statement too complex EXPLANATION: A statement was too complex to be compiled. It must be subdivided into two or more statements.
1.268 - STRCONTRU
SEVERITY: E MESSAGE TEXT: String constant truncated to maximum length EXPLANATION: A character constant or Hollerith constant can contain up to 2000 characters. A Radix-50 constant can contain up to 12 characters.
1.269 - STRDEPTH
SEVERITY: F MESSAGE TEXT: STRUCTUREs/UNIONs/MAPs nested too deeply EXPLANATION: The combined nesting level limit for structures, unions, and maps is 20 levels.
1.270 - STREMPTY
SEVERITY: I MESSAGE TEXT: Structure is empty EXPLANATION: A STRUCTURE declaration contains no fields. USER ACTION: This informational message may indicate an unintended coding error. If so, correct the problem.
1.271 - STRNAME
SEVERITY: E MESSAGE TEXT: Outer level structure is missing a structure name EXPLANATION: An outer level STRUCTURE statement must have a structure name in order for a RECORD statement to be able to reference the structure declaration.
1.272 - STRNOTDEF
SEVERITY: F MESSAGE TEXT: Structure name in RECORD statement not defined EXPLANATION: Either a RECORD statement did not contain a structure name enclosed within slashes or the structure name contained in a RECORD statement was not defined in a structure declaration.
1.273 - SUBEXPVAL
SEVERITY: E MESSAGE TEXT: Subscript or substring expression value out of bounds EXPLANATION: A reference was made to either an array element beyond the specified dimensions or a character substring outside the specified bounds.
1.274 - SUBNOTALL
SEVERITY: F MESSAGE TEXT: Subqualifier not allowed with negated qualifier EXPLANATION: A negated qualifier specified on the command line also specified subqualifier values. For example: /NOCHECK=UNDERFLOW
1.275 - TAGVARIAB
SEVERITY: I MESSAGE TEXT: CDD description contains Tag Variable attribute (ignored) EXPLANATION: Compaq Fortran does not support the Common Data Dictionary Tag Variable attribute.
1.276 - TOOMANCOM
SEVERITY: F MESSAGE TEXT: Too many named common blocks EXPLANATION: Compaq Fortran allows a maximun of 508 named common blocks. You must reduce the number of named common blocks.
1.277 - TOOMANCON
SEVERITY: E MESSAGE TEXT: Too many continuation lines, remainder ignored EXPLANATION: Up to 99 continuation lines are permitted.
1.278 - TOOMANDIM
SEVERITY: E MESSAGE TEXT: More than 7 dimensions specified, remainder ignored EXPLANATION: An array cannot have more than seven dimensions.
1.279 - TOOMNYOPT
SEVERITY: W
MESSAGE TEXT: CDEC$ OPTIONS directives nested too deeply -
this one ignored
EXPLANATION: CDEC$ OPTIONS directives cannot be nested beyond 100
levels.
USER ACTION: Modify source so that CDEC$ OPTIONS nesting depth
does not exceed 100.
1.280 - TOOMANYDO
SEVERITY: F MESSAGE TEXT: DO and IF statements nested too deeply EXPLANATION: DO loops and block IF statements cannot be nested beyond 128 levels.
1.281 - UNDARR
SEVERITY: F MESSAGE TEXT: Undimensioned array or statement function definition out of order EXPLANATION: Either a statement function definition was found among executable statements or an assignment statement involving an undimensioned array was found.
1.282 - UNDSTALAB
SEVERITY: F MESSAGE TEXT: Undefined statement label EXPLANATION: A reference was made to a statement label that is not defined in the program unit.
1.283 - UNRECSTMT
SEVERITY: F MESSAGE TEXT: Unrecognized statement EXPLANATION: The statement encountered was not recognized as valid.
1.284 - UNSUPPTYPE
SEVERITY: I MESSAGE TEXT: CDD description specifies an unsupported data type EXPLANATION: The Common Data Dictionary description for a structure item attempted to use a data type that is not supported by Compaq Fortran. The Compaq Fortran compiler makes the data type accessible by declaring it as an inner structure containing a single unnamed field (%FILL field) that is a LOGICAL*1 array with an appropriate dimension. Change the data type to one that is supported by Compaq Fortran or use the Compaq Fortran built-in functions to manipulate the contents of the field.
1.285 - USEBEFDEF
SEVERITY: I
MESSAGE TEXT: Use of variable before definition; name in SAVE
statement if appropriate
EXPLANATION: A variable in a subprogram was used before its
value was defined. This may have been intentional, with an
assumption of implicit SAVE semantics, but may also have been
a programming error. This message can be suppressed with
/WARNINGS=NOUNINITIALIZED.
USER ACTION: If intentional, name the variable in a SAVE
statement and make sure that it is properly initialized.
Initialization to zero is not guaranteed on all implementations.
1.286 - USEUNIVAR
SEVERITY: W MESSAGE TEXT: Use of initialized variable EXPLANATION: A variable was used before it was initialized. Initialize the variable before using it. This message can be suppressed with /WARNINGS=NOUNINITIALIZED.
1.287 - VARINCEQV
SEVERITY: F
MESSAGE TEXT: Variable inconsistently equivalenced to itself
EXPLANATION: EQUIVALENCE statements specified inconsistent
relationships between variables or array elements. Example:
EQUIVALENCE (A(1), A(2))
1.288 - VARNOTASS
SEVERITY: E MESSAGE TEXT: Variable not assigned label by ASSIGN statement EXPLANATION: A variable was found in a context that required an assigned label (such as in an assigned GOTO statement or as the format specifier of an I/O statement), but no ASSIGN statement was found that assigned a label to that variable. This error commonly occurs if you use an arithmetic assignment statement instead of the ASSIGN statement. If the program executes, the result is unpredictable.
1.289 - VARUNUSED
SEVERITY: I MESSAGE TEXT: Variable was declared but not used EXPLANATION: The specified variable was declared but never used.
1.290 - VAXELNUNS
SEVERITY: W MESSAGE TEXT: This feature is unsupported on VAXELN EXPLANATION: The specified Compaq Fortran feature is not supported on a VAXELN system.
1.291 - VECCHKCON
SEVERITY: W MESSAGE TEXT: /VECTOR conflicts with /CHECK=BOUNDS; /VECTOR ignored EXPLANATION: When you specify /CHECK=BOUNDS, you cannot use /VECTOR. The /VECTOR qualifier is ignored.
1.292 - VFUFEANEX
SEVERITY: W
MESSAGE TEXT: This feature is unsupported and non-executable on
ULTRIX
EXPLANATION: The program attempted to use a Compaq Fortran I/O
feature that is not available on ULTRIX systems. If the resulting
program is run on an ULTRIX system, a run-time error will be issued
if this statement is executed. Major Compaq Fortran features not
available on ULTRIX include the following:
o OPEN and INQUIRE options:
- ORGANIZATION= 'RELATIVE' or 'INDEXED'
- ACCESS='KEYED'
- RECORDTYPE= 'STREAM' or 'STREAM_CR'
- KEY
- DEFAULTFILE
- USEROPEN
o I/O statements DELETE, REWRITE, and UNLOCK
o Read statement keyword attributes: KEY, KEYEQ, KEYGE, KEYGT,
and KEYID
1.293 - VFUFEAUNS
SEVERITY: W
MESSAGE TEXT: This feature is unsupported on ULTRIX-32
EXPLANATION: The program attempted to use a Compaq Fortran I/O
feature that is not available on ULTRIX systems. If the resulting
program is run on an ULTRIX system, this construct will be ignored.
Major Compaq Fortran features not available on ULTRIX include the
following:
o OPEN statement keywords (and attributes):
- DISPOSE= 'PRINT', 'PRINT/DELETE', 'SUBMIT', 'SUBMIT/DELETE'
- BUFFERCOUNT
- EXTENDSIZE
- INITIALSIZE
- NOSPANBLOCKS
- SHARED
o CLOSE statement keywords (and attributes):
- DISPOSE= 'PRINT', 'PRINT/DELETE', 'SUBMIT', 'SUBMIT/DELETE'
- STATUS
1.294 - VFUSRCUNA
SEVERITY: W MESSAGE TEXT: Requested source is not available on ULTRIX EXPLANATION: The program attempted to use one of the following Compaq Fortran I/O features that are not available on ULTRIX systems: o The DICTIONARY statement o The INCLUDE statement for a text module from a library file
1.295 - WRITEERR
SEVERITY: F MESSAGE TEXT: Error writing "file-spec" EXPLANATION: Unable to write to file "file-spec".
1.296 - WRONGCLD
SEVERITY: F MESSAGE TEXT: Wrong command definition installed - please see your system manager EXPLANATION: The current command tables do not include the proper definition of the FORTRAN command. This may be due to having installed an older version of the command definition, or the system command tables were updated but a user process is still using an older version.
1.297 - ZERLENSTR
SEVERITY: E MESSAGE TEXT: Zero-length string EXPLANATION: The length specified for a character, Hollerith, hexadecimal, octal, or Radix-50 constant must not be zero.
| 2 - Run Time Errors |
Errors that occur during execution of your program are reported by
diagnostic messages from the Run-Time Library. These messages can
result from hardware conditions, file system errors, errors
detected by RMS, errors that occur during transfer of data between
the program and an internal record, computations that cause
overflow or underflow, incorrect calls to the Run-Time Library,
problems in array descriptions, and conditions detected by the
operating system. Refer to the OpenVMS Run-Time Library Reference
Manuals for more information.
In order of greatest to least severity, the three classes of
run-time diagnostic messages are as follows:
Code Description
---- -----------
F Severe error; must be corrected. The program
cannot complete execution and is terminated when
the error is encountered.
E Error; should be corrected. The program may
continue execution, but the output from this
execution may be incorrect.
W Warning; should be investigated. The program
continues executing, but output from this execution
may be incorrect.
The following example shows how run-time messages are displayed:
%FOR-F-ADJARRDIM, adjustable array dimension error
In this Help file, the letter "C" after an error code indicates
that program execution can continue immediately after the error if
a user-written condition handler specifies that execution continue.
2.1 - General
2. 1.1 - ADJARRDIM
NUMBER: 93
ERROR CODE: F, C
MESSAGE TEXT: adjustable array dimension error
EXPLANATION: Upon entry to a subprogram, one of the following
errors was detected during the evaluation of dimensioning
information:
o An upper-dimension bound was less than a lower-dimension bound.
o The dimensions implied an array that was larger than the
addressable memory.
2. 1.2 - ATTACCNON
NUMBER: 36
ERROR CODE: F
MESSAGE TEXT: attempt to access non-existent record
EXPLANATION: One of the following conditions occurred:
o A direct access READ, FIND, or DELETE statement attempted to
access a nonexistent record from a relative organization file.
o A direct access READ or FIND statement attempted to access
beyond the end of a sequential organization file.
o A keyed access READ statement attempted to access a nonexistent
record from an indexed organization file.
2. 1.3 - BACERR
NUMBER: 23
ERROR CODE: F
MESSAGE TEXT: BACKSPACE error
EXPLANATION: One of the following conditions occurred:
o The file was not a sequential organization file.
o The file was not opened for sequential access. (A unit opened
for append access can not be backspaced until a REWIND
statement is executed for that unit.)
o RMS detected an error condition during execution of a BACKSPACE
statement.
2. 1.4 - CLOERR
NUMBER: 28 ERROR CODE: F MESSAGE TEXT: CLOSE error EXPLANATION: An error condition was detected by RMS during execution of a CLOSE statement.
2. 1.5 - DELERR
NUMBER: 55
ERROR CODE: F
MESSAGE TEXT: DELETE error
EXPLANATION: One of the following conditions occurred:
o On a direct access DELETE, the file did not have relative
organization.
o On a current record DELETE, the file did not have relative or
indexed organization, or the file was opened for direct access.
o RMS detected an error condition during execution of a DELETE
statement.
2. 1.6 - DUPFILSPE
NUMBER: 21 ERROR CODE: F MESSAGE TEXT: duplicate file specifications EXPLANATION: Multiple attempts were made to specify file attributes without an intervening close operation. One of the following conditions occurred: o A DEFINE FILE was followed by another DEFINE FILE statement. o A DEFINE FILE was followed by an OPEN statement. o A CALL ASSIGN or CALL FDBSET was followed by an OPEN statement.
2. 1.7 - ENDDURREA
NUMBER: 24
ERROR CODE: F
MESSAGE TEXT: end-of-file during read
EXPLANATION: One of the following conditions occurred:
o An RMS end-of-file condition was encountered during execution
of a READ statement that did not contain an END, ERR, or IOSTAT
specification.
o An end-of-file record written by the ENDFILE statement was
encountered during execution of a READ statement that did not
contain an END, ERR, or IOSTAT specification.
o An attempt was made to read past the end of an internal file,
character string, or array during execution of a READ statement
that did not contain an END, ERR, or IOSTAT specification.
2. 1.8 - ENDFILERR
NUMBER: 33
ERROR CODE: F
MESSAGE TEXT: ENDFILE error
EXPLANATION: One of the following conditions occurred:
o The file was not a sequential organization file with
variable-length records.
o The file was not opened for sequential or append access.
o An unformatted file did not contain segmented records.
o RMS detected an error during execution of an ENDFILE statement.
2. 1.9 - ERRDURREA
NUMBER: 39 ERROR CODE: F MESSAGE TEXT: error during read EXPLANATION: RMS detected an error condition during execution of a READ statement.
2. 1.10 - ERRDURWRI
NUMBER: 38 ERROR CODE: F MESSAGE TEXT: error during write EXPLANATION: RMS detected an error condition during execution of a WRITE statement.
2. 1.11 - FILNAMSPE
NUMBER: 43 ERROR CODE: F MESSAGE TEXT: file name specification error EXPLANATION: A file-name specification given to OPEN, INQUIRE, or CALL ASSIGN statement was not acceptable to RMS.
2. 1.12 - FILNOTFOU
NUMBER: 29 ERROR CODE: F MESSAGE TEXT: file not found EXPLANATION: A file with the specified name could not be found during an open operation.
2. 1.13 - FINERR
NUMBER: 57 ERROR CODE: F MESSAGE TEXT: FIND error EXPLANATION: RMS detected an error condition during execution of a FIND statement.
2. 1.14 - FLOCONFAI
NUMBER: 95 ERROR CODE: E MESSAGE TEXT: floating point conversion failed EXPLANATION: The attempted unformatted read or write of nonnative floating-point data failed. A nonnative floating-point value either exceeded the allowable maximum value for the equivalent native format and was set equal to invalid, or the value was infinity (plus or minus), not a number (NaN), or otherwise invalid and was set to invalid. Very small numbers are set to zero (0). This could be caused by the specified nonnative floating-point format not matching the floating-point format found in the specified file. Make sure the correct file was specified. Make sure the record layout matches the format Compaq Fortran is expecting. Check that the correct nonnative floating-point data format was specified, as described in your user manual.
2. 1.15 - FLOOVEMAT
NUMBER: 88 ERROR CODE: F, C MESSAGE TEXT: floating overflow in math library EXPLANATION: A floating overflow condition was detected during execution of a math library procedure. The result returned was the reserved operand, -0.
2. 1.16 - FLOUNDMAT
NUMBER: 89 ERROR CODE: F, C MESSAGE TEXT: floating underflow in math library EXPLANATION: A floating underflow condition was detected during execution of a math library procedure. The result returned was zero.
2. 1.17 - FLTDIV
NUMBER: 73 ERROR CODE: F, C MESSAGE TEXT: arithmetic trap, zero divide EXPLANATION: During a floating-point or decimal arithmetic operation, an attempt was made to divide by 0.0. If floating-point, the result returned is the the reserved operand, -0. If decimal, the result of the operation is unpredictable.
2. 1.18 - FLTDIV_F
NUMBER: 73 ERROR CODE: F, C MESSAGE TEXT: arithmetic fault, zero divide EXPLANATION: During a floating-point arithmetic operation, an attempt was made to divide by zero.
2. 1.19 - FLTOVF
NUMBER: 72 ERROR CODE: F, C MESSAGE TEXT: arithmetic trap, floating overflow EXPLANATION: During an arithmetic operation a floating-point value exceeded the largest representable value for that data type. The result of the operation was set to the reserved operand, -0.
2. 1.20 - FLTOVF_F
NUMBER: 72 ERROR CODE: F, C MESSAGE TEXT: arithmetic fault, floating overflow EXPLANATION: During an arithmetic operation, a floating-point value exceeded the largest representable value for that data type.
2. 1.21 - FLTUND
NUMBER: 74 ERROR CODE: F, C MESSAGE TEXT: arithmetic trap, floating underflow EXPLANATION: During an arithmetic operation a floating-point value became less than the smallest representable value for that data type and was replaced with a value of zero.
2. 1.22 - FLTUND_F
NUMBER: 74 ERROR CODE: F, C MESSAGE TEXT: arithmetic fault, floating underflow EXPLANATION: During an arithmetic operation a floating-point value became less than the smallest representable value for that data type.
2. 1.23 - FORVARMIS
NUMBER: 61 ERROR CODE: F, C MESSAGE TEXT: format/variable-type mismatch EXPLANATION: An attempt was made either to read or write a real variable with an integer field descriptor (I or L), or to read or write an integer or logical variable with a real field descriptor (D, E, F, or G). If execution continued, one of the following actions occurred: o If I or L, conversion as if INTEGER*4. o If D, E, F, or G, conversion as if REAL*4.
2. 1.24 - INCFILORG
NUMBER: 51
ERROR CODE: F
MESSAGE TEXT: inconsistent file organization
EXPLANATION: One of the following conditions occurred:
o The file organization specified in an OPEN statement did not
match the organization of the existing file.
o The file organization of the existing file was inconsistent
with the specified access mode; that is, either direct access
was specified with an indexed organization file or keyed access
was specified with a sequential or relative organization file.
2. 1.25 - INCKEYCHG
NUMBER: 50 ERROR CODE: F MESSAGE TEXT: inconsistent key change or duplicate key EXPLANATION: A WRITE or REWRITE to an indexed organization file caused a key field to change or be duplicated. This condition was not allowed by the attributes of the file, as established when the file was created.
2. 1.26 - INCOPECLO
NUMBER: 46
ERROR CODE: F
MESSAGE TEXT: inconsistent OPEN/CLOSE parameters
EXPLANATION: Specifications in an OPEN or CLOSE statement were
inconsistent. Some invalid combinations are:
o READONLY with STATUS='NEW' or STATUS='SCRATCH'
o ACCESS='APPEND' with READONLY, STATUS='NEW', or
STATUS='SCRATCH'
o DISPOSE='SAVE', 'PRINT', or 'SUBMIT' with STATUS='SCRATCH'
o DISPOSE='DELETE' with READONLY
2. 1.27 - INCRECLEN
NUMBER: 37
ERROR CODE: F
MESSAGE TEXT: inconsistent record length
EXPLANATION: One of the following conditions occurred:
o An attempt was made to create a new relative, indexed, or
direct access file without specifying a record length.
o An existing file was opened in which the record length did not
match the record size given in an OPEN or DEFINE FILE
statement.
2. 1.28 - INCRECTYP
NUMBER: 44 ERROR CODE: F MESSAGE TEXT: inconsistent record type EXPLANATION: The RECORDTYPE value in an OPEN statement did not match the record type attribute of the existing file that was opened.
2. 1.29 - INFFORLOO
NUMBER: 60 ERROR CODE: F MESSAGE TEXT: infinite format loop EXPLANATION: The format associated with an I/O statement that included an I/O list had no field descriptors to use in transferring those values.
2. 1.30 - INPCONERR
NUMBER: 64 ERROR CODE: F, C MESSAGE TEXT: input conversion error EXPLANATION: During a formatted input operation, either an invalid character was detected in an input field, or the input value overflowed the range representable in the input variable. The value of the variable was set to zero.
2. 1.31 - INPRECTOO
NUMBER: 22 ERROR CODE: F MESSAGE TEXT: input record too long EXPLANATION: A record was read that exceeded the explicit or the default record length specified in OPEN (or by the default OPEN). To read the file, use an OPEN statement with a RECL value of the appropriate size.
2. 1.32 - INPSTAREQ
NUMBER: 67 ERROR CODE: F MESSAGE TEXT: input statement requires too much data EXPLANATION: An unformatted READ statement attempted to read more data than existed in the record being read.
2. 1.33 - INSVIRMEM
NUMBER: 41 ERROR CODE: F MESSAGE TEXT: insufficient virtual memory EXPLANATION: The Compaq Fortran Run-Time Library attempted to exceed its virtual page limit while dynamically allocating space.
2. 1.34 - INTDIV
NUMBER: 71 ERROR CODE: F, C MESSAGE TEXT: arithmetic trap, integer zero divide EXPLANATION: During an integer arithmetic operation, an attempt was made to divide by zero. The result of the operation was set to the dividend, which is equivalent to division by one.
2. 1.35 - INTOVF
NUMBER: 70 ERROR CODE: F, C MESSAGE TEXT: arithmetic trap, integer overflow EXPLANATION: During an arithmetic operation, an integer value exceeded byte, word, or longword range. The result of the operation was the correct low-order part.
2. 1.36 - INVARGFOR
NUMBER: 48
ERROR CODE: F
MESSAGE TEXT: invalid argument to Fortran Run-Time Library
EXPLANATION: One of the following conditions occurred:
o An invalid argument was given to a PDP-11 FORTRAN compatibility
subroutine, such as ERRSET.
o The Compaq Fortran compiler passed an invalid coded argument to
the Run-Time Library. This can occur if the compiler is newer
than the Run-Time Library in use.
2. 1.37 - INVARGMAT
NUMBER: 81 ERROR CODE: F MESSAGE TEXT: invalid argument to math library EXPLANATION: One of the mathematical procedures detected an invalid argument value.
2. 1.38 - INVKEYSPE
NUMBER: 49 ERROR CODE: F MESSAGE TEXT: invalid key specification EXPLANATION: A key specification in an OPEN statement or in a keyed access READ statement was invalid. For example, the key length may have been zero or greater than 255 bytes, or the key length may not conform to the key specification of the existing file.
2. 1.39 - INVLOGUNI
NUMBER: 32 ERROR CODE: F MESSAGE TEXT: invalid logical unit number EXPLANATION: A logical unit number greater than 119 or less than zero was used in an I/O statement.
2. 1.40 - INVMATKEY
NUMBER: 94 ERROR CODE: F MESSAGE TEXT: invalid key match specifier for key direction EXPLANATION: A keyed READ used an invalid key match specifier for the direction of that key. Use KEYGE and KEYGT only on ascending keys. Use KEYLE and KEYLT only on descending keys. Use KEYNXT and KEYNXTNE to avoid enforcement of key direction and match specifier.
2. 1.41 - INVREFVAR
NUMBER: 19
ERROR CODE: F
MESSAGE TEXT: invalid reference to variable "varname" in namelist
input
EXPLANATION: The name of the variable in error is substituted for
"varname" in the message text. One of the following conditions
occurred:
o The variable was not a member of the namelist group.
o An attempt was made to subscript the scalar variable.
o A subscript of the array variable was out-of-bounds.
o There were too many or too few subscripts for the variable.
o An attempt was made to specify a substring of a noncharacter
variable or array name.
o A substring specifier of the character variable is
out-of-bounds.
o A subscript or substring specifier of the variable was not an
integer constant.
o An attempt was made to specify a substring using an
unsubscripted array variable.
2. 1.42 - KEYVALERR
NUMBER: 45 ERROR CODE: F MESSAGE TEXT: keyword value error in OPEN statement EXPLANATION: An OPEN or CLOSE statement keyword requiring a value had an improper value. Refer to the DEC Fortran Language Reference Manual for the allowed keyword values.
2. 1.43 - LISIO_SYN
NUMBER: 59 ERROR CODE: F, C MESSAGE TEXT: list-directed I/O syntax error EXPLANATION: The data in a list-directed input record had an invalid format, or the type of the constant was incompatible with the corresponding variable. The value of the variable was unchanged.
2. 1.44 - LOGZERNEG
NUMBER: 83 ERROR CODE: F, C MESSAGE TEXT: logarithm of zero or negative value EXPLANATION: An attempt was made to take the logarithm of zero or a negative number. The result returned was the reserved operand, -0.
2. 1.45 - MIXFILACC
NUMBER: 31
ERROR CODE: F
MESSAGE TEXT: mixed file access modes
EXPLANATION: One of the following conditions occurred:
o An attempt was made to use both formatted and unformatted
operations on the same unit.
o An attempt was made to use an invalid combination of access
modes on a unit, such as direct and sequential. The only valid
combination is sequential and keyed access on a unit opened
with ACCESS='KEYED'.
o An attempt was made to execute a Fortran I/O statement on a
logical unit that was opened by a language other than Fortran.
2. 1.46 - NO_CURREC
NUMBER: 53 ERROR CODE: F MESSAGE TEXT: no current record EXPLANATION: A REWRITE or current record DELETE was attempted when no current record was defined.
2. 1.47 - NO_SUCDEV
NUMBER: 42 ERROR CODE: F MESSAGE TEXT: no such device EXPLANATION: A file-name specification included an invalid or unknown device name when an open operation was attempted.
2. 1.48 - NOTFORSPE
NUMBER: 1 ERROR CODE: F MESSAGE TEXT: not a Fortran-specific error EXPLANATION: An error occurred in the user program or in the Run-Time Library that was not a Fortran-specific error. Therefore it was not reportable through any other message in the table. If you call ERRSNS, an error of this kind returns a value of 1. Use the fifth argument of the call to ERRSNS (condval) to obtain the unique system condition value that identifies the error.
2. 1.49 - OPEDEFREQ
NUMBER: 26
ERROR CODE: F
MESSAGE TEXT: OPEN or DEFINE FILE required for keyed or direct
access
EXPLANATION: One of the following conditions occurred:
o A direct access READ, WRITE, FIND, or DELETE statement
specified a file that was not opened with a DEFINE FILE
statement or with an OPEN statement specifying ACCESS='DIRECT'.
o A keyed access READ statement specified a file that was not
opened with an OPEN statement specifying ACCESS='KEYED'.
2. 1.50 - OPEFAI
NUMBER: 30 ERROR CODE: F MESSAGE TEXT: open failure EXPLANATION: An error was detected by RMS while attempting to open a file in an OPEN, INQUIRE, or other I/O statement. This message is used when the error condition is not one of the more common conditions for which specific error messages are provided.
2. 1.51 - OUTCONERR
NUMBER: 63 ERROR CODE: E, C MESSAGE TEXT: output conversion error EXPLANATION: During a formatted output operation, the value of a particular number could not be output in the specified field length without loss of significant digits. When this error occurs, the field is filled with asterisks.
2. 1.52 - OUTSTAOVE
NUMBER: 66 ERROR CODE: F MESSAGE TEXT: output statement overflows record EXPLANATION: An output statement attempted to transfer more data than would fit in the maximum record size.
2. 1.53 - RECIO_OPE
NUMBER: 40
ERROR CODE: F
MESSAGE TEXT: recursive I/O operation
EXPLANATION: While processing an I/O statement for a logical unit,
another I/O operation on the same logical unit was attempted. One
of the following conditions may have occurred:
o A function subprogram that performs I/O to the same logical
unit was referenced in an expression in an I/O list or variable
format expression.
o An I/O statement was executed at AST level for the same logical
unit.
o An exception handler (or a procedure it called) executed an I/O
statement in response to a signal from an I/O statement for the
same logical unit.
2. 1.54 - RECNUMOUT
NUMBER: 25 ERROR CODE: F MESSAGE TEXT: record number outside range EXPLANATION: A direct access READ, WRITE, or FIND statement specified a record number outside the range specified when the file was created.
2. 1.55 - REWERR
NUMBER: 20
ERROR CODE: F
MESSAGE TEXT: REWIND error
EXPLANATION: One of the following conditions occurred:
o The file was not a sequential organization file.
o The file was not opened for sequential or append access.
o RMS detected an error condition during execution of a REWIND
statement.
2. 1.56 - REWRITERR
NUMBER: 54 ERROR CODE: F MESSAGE TEXT: REWRITE error EXPLANATION: RMS detected an error condition during execution of a REWRITE statement.
2. 1.57 - SEGRECFOR
NUMBER: 35 ERROR CODE: F MESSAGE TEXT: segmented record format error EXPLANATION: An invalid segmented record control data word was detected in an unformatted sequential file. The file was probably either written in a language other that Fortran, or created with RECORDTYPE='FIXED' or 'VARIABLE' in effect.
2. 1.58 - SIGLOSMAT
NUMBER: 87 ERROR CODE: F, C MESSAGE TEXT: significance lost in math library EXPLANATION: The magnitude of an argument or the magnitude of the ratio of the arguments to a math library function was so large that all significance in the result was lost. The result returned was the reserved operand -0.
2. 1.59 - SPERECLOC
NUMBER: 52 ERROR CODE: F MESSAGE TEXT: specified record locked EXPLANATION: A READ or direct access WRITE, FIND, or DELETE was attempted on a record that was locked by another user.
2. 1.60 - SQUROONEG
NUMBER: 84 ERROR CODE: F, C MESSAGE TEXT: square root of negative value EXPLANATION: An argument required the evaluation of the square root of a negative value. The result returned was the reserved operand, -0.
2. 1.61 - SUBRNG
NUMBER: 77 ERROR CODE: F, C MESSAGE TEXT: trap, subscript out of range EXPLANATION: An array reference was detected outside the declared array bounds.
2. 1.62 - SYNERRFOR
NUMBER: 62 ERROR CODE: F MESSAGE TEXT: syntax error in format EXPLANATION: A syntax error was encountered while the Run-Time Library was processing a format stored in an array or character variable.
2. 1.63 - SYNERRNAM
NUMBER: 17 ERROR CODE: F MESSAGE TEXT: syntax error in namelist input "text" EXPLANATION: The syntax of input to a namelist READ statement was incorrect. The part of the record in which the error was detected is substituted for "text" in the message text.
2. 1.64 - TOOMANREC
NUMBER: 27
ERROR CODE: F
MESSAGE TEXT: too many records in I/O statement
EXPLANATION: One of the following conditions occurred:
o An attempt was made to read or write more than one record with
an ENCODE or DECODE statement.
o An attempt was made to write more records than existed.
2. 1.65 - TOOMANVAL
NUMBER: 18 ERROR CODE: F MESSAGE TEXT: too many values for namelist variable "varname" EXPLANATION: An attempt was made to assign too many values to a variable during a namelist READ statement. The name of the variable is substituted for "varname" in the message text.
2. 1.66 - UNDEXP
NUMBER: 82 ERROR CODE: F, C MESSAGE TEXT: undefined exponentiation EXPLANATION: An exponentiation that is mathematically undefined was attempted, for example, 0.**0. The result returned was the reserved operand -0 (for floating-point operations) or zero (for integer operations).
2. 1.67 - UNIALROPE
NUMBER: 34 ERROR CODE: F MESSAGE TEXT: unit already open EXPLANATION: A DEFINE FILE statement specified a logical unit that was already opened.
2. 1.68 - UNLERR
NUMBER: 56 ERROR CODE: F MESSAGE TEXT: UNLOCK error EXPLANATION: RMS detected an error condition during execution of an UNLOCK statement.
2. 1.69 - VFEVALERR
NUMBER: 68 ERROR CODE: F, C MESSAGE TEXT: variable format expression value error EXPLANATION: The value of a variable format expression was not within the range acceptable for its intended use; for example, a field width was less than or equal to zero. A value of one was assumed, except for a P edit descriptor, for which a value of zero was assumed.
2. 1.70 - WRIREAFIL
NUMBER: 47 ERROR CODE: F MESSAGE TEXT: write to READONLY file EXPLANATION: A write operation was attempted to a file that was declared READONLY in the OPEN statement that is currently in effect.
2. 1.71 - WRONUMARG
NUMBER: 80 ERROR CODE: F MESSAGE TEXT: wrong number of arguments EXPLANATION: An improper number of arguments was used to call a math library procedure.
2.2 - Parallel Processing Specific
2. 2.1 - COMSHRERR
SEVERITY: F MESSAGE TEXT: Unable to share memory region from x to y EXPLANATION: The Fortran Run-Time Library could not make the specified memory region shared among the processes participating in the parallel processing environment.
2. 2.2 - DEFVALUSED
SEVERITY: I MESSAGE TEXT: Default value of xx used for logical name EXPLANATION: A default value was used for the specified logical name.
2. 2.3 - FAIACTCPU
SEVERITY: F MESSAGE TEXT: Failed to obtain active CPU count EXPLANATION: The Fortran Run-Time Library could not obtain the active CPU count. Thus, it was unable to set up the parallel processing environment.
2. 2.4 - FAIDCLEXIT
SEVERITY: F MESSAGE TEXT: Failed to declare an exit handler EXPLANATION: The Fortran Run-Time Library could not declare an exit handler. Thus, it was unable to set up the parallel processing environment.
2. 2.5 - FAIIDPRC
SEVERITY: F MESSAGE TEXT: Failed to identify the process EXPLANATION: The Fortran Run-Time Library could not identify the process. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2. 2.6 - FAIIMAGNAME
SEVERITY: F MESSAGE TEXT: Failed to obtain image name EXPLANATION: The Fortran Run-Time Library could not obtain the image name. Thus, it was unable to set up the parallel processing environment.
2. 2.7 - FAIOWNERID
SEVERITY: F MESSAGE TEXT: Failed to obtain owner process ID EXPLANATION: The Fortran Run-Time Library could not obtain the owner process identification. Thus, it was unable to set up the parallel processing environment.
2. 2.8 - FAIPRCID
SEVERITY: F MESSAGE TEXT: Failed to obtain process ID EXPLANATION: The Fortran Run-Time Library could not obtain the process identification. Thus, it was unable to set up the parallel processing environment.
2. 2.9 - FAIPRCNAME
SEVERITY: F MESSAGE TEXT: Failed to obtain process name EXPLANATION: The Fortran Run-Time Library could not obtain the process name. Thus, it was unable to set up the parallel processing environment.
2. 2.10 - FAISHRSTACK
SEVERITY: F MESSAGE TEXT: Unable to share the stack region from x to y EXPLANATION: The Fortran Run-Time Library could not make the specified stack region shared among processes participating in the parallel processing environment.
2. 2.11 - FAISUBPRC
SEVERITY: F MESSAGE TEXT: Failed to create subprocess EXPLANATION: The Fortran Run-Time Library could not get the process identification. Thus, it was unable to set up the parallel processing environment.
2. 2.12 - FATINTERR
SEVERITY: F MESSAGE TEXT: Fatal internal error in the Fortran Parallel Processing Run-Time Library EXPLANATION: The Fortran Run-Time Library detected an unrecoverable, inconsistent condition. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2. 2.13 - INVCOMADR
SEVERITY: F MESSAGE TEXT: Invalid memory region addresses EXPLANATION: The Fortran Run-Time Library detected invalid starting and ending addresses for a shared memory region. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2. 2.14 - INVLCLADR
SEVERITY: F MESSAGE TEXT: Invalid $LOCAL PSECT addresses EXPLANATION: The Fortran Run-Time Library detected invalid starting and ending addresses for a $LOCAL PSECT. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2. 2.15 - INVLOGNAM
SEVERITY: E MESSAGE TEXT: Invalid logical name definition EXPLANATION: A logical name was defined incorrectly.
2. 2.16 - INVNUMPRC
SEVERITY: F MESSAGE TEXT: Invalid number of processes EXPLANATION: The Fortran Run-Time Library detected an invalid number of processes. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2. 2.17 - INVUNWIND
SEVERITY: F MESSAGE TEXT: Invalid stack unwinding encountered EXPLANATION: The Fortran Run-Time Library detected an invalid attempt to unwind the stack.
2. 2.18 - LOCALACCESS
SEVERITY: F MESSAGE TEXT: Subprocess unable to access the shared $LOCAL PSECT EXPLANATION: A subprocess could not access the shared $LOCAL PSECT.
2. 2.19 - LOCALSHRERR
SEVERITY: F MESSAGE TEXT: Unable to share the $LOCAL PSECT EXPLANATION: The Fortran Run-Time Library could not make the $LOCAL PSECT shared among the processes participating in the parallel processing environment.
2. 2.20 - MEMSHRERR
SEVERITY: F MESSAGE TEXT: Memory sharing error EXPLANATION: The Fortran Run-Time Library failed to share data among the processes participating in the parallel processing environment.
2. 2.21 - NOPARINIT
SEVERITY: I MESSAGE TEXT: Parallel processing environment was not available EXPLANATION: The Compaq Fortran main program was not compiled with /PARALLEL. As a result, the parallel processing environment was not available.
2. 2.22 - NOTIMPRET
SEVERITY: F MESSAGE TEXT: Routine not implemented in this version of FORRTL2 EXPLANATION: An attempt was made to use a routine that is not implemented in this version of the Fortran Run-Time Library.
2. 2.23 - NOTRUNINPP
SEVERITY: I MESSAGE TEXT: Unable to run the DO-Loop PC: xx in parallel EXPLANATION: A parallel DO loop with the specified PC address cannot run in parallel.
2. 2.24 - STACKSHRERR
SEVERITY: F MESSAGE TEXT: Stack sharing error EXPLANATION: The Fortran Run-Time Library could not make the stack shared among the processes participating in the parallel processing environment.
2. 2.25 - STKBUFOVR
SEVERITY: F MESSAGE TEXT: Stack buffer overflow was detected EXPLANATION: An internal limit on the number of shared stack regions that your program can have was exceeded. Submit a Software Performance Report (SPR) that describes the conditions leading to the error.
2. 2.26 - SUBPRCDIED
SEVERITY: F MESSAGE TEXT: Subprocess PID: xx terminated EXPLANATION: A subprocess with the specified process ID was terminated.
2. 2.27 - TOOMANPRC
SEVERITY: E MESSAGE TEXT: Too many processes, allowed a maximum of 32 processes EXPLANATION: A limit on the number of processes participating in the Fortran parallel processing environment was exceeded. The limit is currently 32.
| 3 - Vectorization Errors |
The following errors identify when vectorization was inhibited and
attempt to identify why it was inhibited. These messages are
generated if the /VECTOR/SHOW=DATA_DEPENDENCES/DIAGNOSTICS
qualifiers are specified. These errors are only generated to the
diagnostic file, not to the listing file or terminal.
Unknown dependence using xxxx
The compiler has analyzed the dependences between array
references and is unable to determine the order in which the
references must occur. Many times this is caused by not knowing
the range of values possible for an expression used as part of
the array index.
Nonuniform dependence
The compiler has detected that the relative order of references
to common memory locations, for two array references in the loop,
are not uniform for all such locations. For example:
A(I) = B(I) * A(N-I)
Some locations are accessed first by A(I) and others by A(N-I).
Outer level vectorization inhibited
The compiler has analyzed the dependences between array
references at different DO-loop levels and is unable to determine
the order in which the references must occur.
These errors relate to assertion declarations. See Section 6.2.1
in your performance guide for information on how to handle these
errors.
Within LSE, you can use Review Mode to apply suggested assertions
to handle these errors. To do so, move the cursor to the
suggestion that you wish to use and press Ctrl/G. This instructs
LSE to apply the suggestion to the source file. LSE then prompts
for a confirmation that this change is desirable. If it is, answer
YES and the suggestion will be inserted.
|
|
