Run-Time Error Messages

The Intel Fortran message catalog file was not found on this system. This error has no condition symbol.

The Intel Fortran message catalog file was not found on this system. This error has no condition symbol.

The Intel Fortran message catalog file was not found. This error has no condition symbol.

The Intel Fortran message catalog file could not be opened because of insufficient virtual memory. To overcome this problem, increase the per-process data limit by using the limit (C shell) or ulimit (Bourne* and Korn and bash  shells) commands before running the program again.

For more information, see error 41. This error has no condition symbol.

FOR$IOS_NOTFORSPE. An error in the user program or in the RTL was not a Intel Fortran-specific error and was not reportable through any other Intel Fortran run-time messages. If you call ERRSNS, an error of this kind returns a value of 1 (for more information on the ERRSNS subroutine, see the Intel Fortran Language Reference Manual).

FOR$IOS_BUG_CHECK. Internal error. Please check that the program is correct. Recompile if an error existed in the program. If this error persists, submit a problem report.

FOR$IOS_PERACCFIL. Check the mode (protection) of the specified file. Make sure the correct file was being accessed. Change the protection, specified file, or process used before rerunning program.

FOR$IOS_CAOVEEXI. Specified file xxx already exists when OPEN statement specified STATUS= ' NEW ' (create new file) using I/O unit x. Make sure correct file name, directory path, unit, and so forth were specified in the source program. Decide whether to:

• Rename or remove the existing file before rerunning the program.
• Modify the source file to specify different file specification, I/O unit, or OPEN statement STATUS.

FOR$IOS_UNINOTCON. The specified unit was not open at the time of the attempted I/O operation. Check if correct unit number was specified. If appropriate, use an OPEN statement to explicitly open the file (connect the file to the unit number).

FOR$IOS_SYNERRNAM. The syntax of input to a namelist-directed READ statement was incorrect.

FOR$IOS_TOOMANVAL. An attempt was made to assign too many values to a variable during a namelist READ statement.

FOR$IOS_INVREFVAR. One of the following conditions occurred:

• The variable was not a member of the namelist group.
• An attempt was made to subscript a scalar variable.
• A subscript of the array variable was out-of-bounds.
• An array variable was specified with too many or too few subscripts for the variable.
• An attempt was made to specify a substring of a noncharacter variable or array name.
• A substring specifier of the character variable was out-of-bounds.
• A subscript or substring specifier of the variable was not an integer constant.
• An attempt was made to specify a substring by using an unsubscripted array variable.

FOR$IOS_REWERR. One of the following conditions occurred:

• The file was not a sequential file.
• The file was not opened for sequential or append access.
• The Intel Fortran RTL I/O system detected an error condition during execution of a REWIND statement.

FOR$IOS_DUPFILSPE. Multiple attempts were made to specify file attributes without an intervening close operation. A DEFINE FILE statement was followed by another DEFINE FILE statement or an OPEN statement

FOR$IOS_INPRECTOO. A record was read that exceeded the explicit or default record length specified when the file was opened. To read the file, use an OPEN statement with a RECL= value (record length) of the appropriate size.

FOR$IOS_BACERR. The Intel Fortran RTL I/O system detected an error condition during execution of a BACKSPACE statement.

FOR$IOS_ENDDURREA. One of the following conditions occurred:

• A Intel Fortran RTL I/O system end-of-file condition was encountered during execution of a READ statement that did not contain an END, ERR, or IOSTAT specification.
• 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.
• 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.

This error is returned by END and ERRSNS.

FOR$IOS_RECNUMOUT. A direct access READ, WRITE, or FIND statement specified a record number outside the range specified when the file was opened.

FOR$IOS_OPEDEFREQ. A direct access READ, WRITE, or FIND statement was attempted for a file when no prior DEFINE FILE or OPEN statement with ACCESS= ' DIRECT ' was performed for that file.

FOR$IOS_TOOMANREC. An attempt was made to do one of the following:

• Read or write more than one record with an ENCODE or DECODE statement.
• Write more records than existed.

FOR$IOS_CLOERR. An error condition was detected by the Intel Fortran RTL I/O system during execution of a CLOSE statement.

FOR$IOS_FILNOTFOU. A file with the specified name could not be found during an open operation.

FOR$IOS_OPEFAI. An error was detected by the Intel Fortran RTL I/O system while attempting to open a file in an OPEN, INQUIRE, or other I/O statement. This message is issued when the error condition is not one of the more common conditions for which specific error messages are provided. It can occur when an OPEN operation was attempted for one of the following:

• Segmented file that was not on a disk or a raw magnetic tape
• Standard I/O file that had been closed

FOR$IOS_MIXFILACC. An attempt was made to use any of the following combinations:

• Formatted and unformatted operations on the same unit
• An invalid combination of access modes on a unit, such as direct and sequential
• A Intel Fortran RTL I/O statement on a logical unit that was opened by a program coded in another language

FOR$IOS_INVLOGUNI. A logical unit number greater than 2,147,483,647 or less than zero was used in an I/O statement.

FOR$IOS_ENDFILERR. One of the following conditions occurred:

• The file was not a sequential organization file with variable-length records.
• The file was not opened for sequential or append access.
• An unformatted file did not contain segmented records.
• The Intel Fortran RTL I/O system detected an error during execution of an ENDFILE statement.

FOR$IOS_UNIALROPE. A DEFINE FILE statement specified a logical unit that was already opened.

FOR$IOS_SEGRECFOR. An invalid segmented record control data word was detected in an unformatted sequential file. The file was probably either created with RECORDTYPE= ' FIXED ' or ' VARIABLE ' in effect, or was created by a program written in a language other than Fortran.

FOR$IOS_ATTACCNON. A direct-access READ or FIND statement attempted to access beyond the end of a relative file (or a sequential file on disk with fixed-length records) or access a record that was previously deleted in a relative file.

FOR$IOS_INCRECLEN. An attempt was made to open a direct access file without specifying a record length.

FOR$IOS_ERRDURWRI. The Intel Fortran RTL I/O system detected an error condition during execution of a WRITE statement.

FOR$IOS_ERRDURREA. The Intel Fortran RTL I/O system detected an error condition during execution of a READ statement.

FOR$IOS_RECIO_OPE. While processing an I/O statement for a logical unit, another I/O operation on the same logical unit was attempted, such as a function subprogram that performs I/O to the same logical unit that was referenced in an expression in an I/O list or variable format expression.

FOR$IOS_INSVIRMEM. The Intel Fortran RTL attempted to exceed its available virtual memory while dynamically allocating space. To overcome this problem, increase the per-process data limit by using the limit (C shell) or ulimit (Bourne* and Korn and bash shell) commands before you run this program again.

To determine whether the maximum per-process data size is already allocated, check the value of the maxdsiz parameter in the sysconfigtab or system configuration file. If necessary, increase its value. Changes to do not take effect until the system has been rebooted (you do not need to rebuild the kernel if you modify sysconfigtab).

Before you try to run this program again, wait until the new system resources take effect.

FOR$IOS_NO_SUCDEV. A pathname included an invalid or unknown device name when an OPEN operation was attempted.

FOR$IOS_FILNAMSPE. A pathname or file name given to an OPEN or INQUIRE statement was not acceptable to the Intel Fortran RTL I/O system.

FOR$IOS_INCRECTYP. The RECORDTYPE value in an OPEN statement did not match the record type attribute of the existing file that was opened.

FOR$IOS_KEYVALERR. An improper value was specified for an OPEN or CLOSE statement specifier requiring a value.

FOR$IOS_INCOPECLO. Specifications in an OPEN or CLOSE statement were inconsistent. Some invalid combinations follow:

• READONLY or ACTION= ' READ ' with STATUS= ' NEW ' or STATUS= ' SCRATCH '
• READONLY with STATUS= ' REPLACE ' , ACTION= ' WRITE ' ,
  or ACTION= ' READWRITE '
• ACCESS= ' APPEND ' with READONLY, ACTION= ' READ ' , STATUS= ' NEW ' , or STATUS= ' SCRATCH '
• DISPOSE= ' SAVE ' , ' PRINT ' , or ' SUBMIT ' with STATUS= ' SCRATCH '
• DISPOSE= ' DELETE ' with READONLY
• CLOSE statement STATUS= ' DELETE ' with OPEN statement READONLY
• ACCESS= ' APPEND ' with STATUS= ' REPLACE '
• ACCESS= ' DIRECT ' or ' KEYED ' with POSITION= ' APPEND ' , ' ASIS ' , or ' REWIND '

FOR$IOS_WRIREAFIL. A write operation was attempted to a file that was declared ACTION= ' READ ' or READONLY in the OPEN statement that is currently in effect.

FOR$IOS_INVARGFOR. The compiler passed an invalid or improperly coded argument to the Intel Fortran RTL. This can occur if the compiler is newer than the RTL in use.

FOR$IOS_INCFILORG. The file organization specified in an OPEN statement did not match the organization of the existing file.

FOR$IOS_NO_CURREC. Attempted to execute a REWRITE statement to rewrite a record when the current record was undefined. To define the current record, execute a successful READ statement. You can optionally perform an INQUIRE statement on the logical unit after the READ statement and before the REWRITE statement. No other operations on the logical unit may be performed between the READ and REWRITE statements.

FOR$IOS_DELERR. An error condition was detected by the Intel Fortran RTL I/O system during execution of a DELETE statement.

FOR$IOS_FINERR. The Intel Fortran RTL I/O system detected an error condition during execution of a FIND statement.

FOR$IOS_FMTSYN. Check the statement containing xx, a character substring from the format string, for a format syntax error. For information about FORMAT statements, see the Intel Fortran Language Reference Manual.

FOR$IOS_LISIO_SYN ². 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.

FOR$IOS_INFFORLOO. The format associated with an I/O statement that included an I/O list had no field descriptors to use in transferring those values.

FOR$IOS_FORVARMIS ². An attempt was made either to read or write a real variable with an integer field descriptor (I, L, O, Z, B), or to read or write an integer or logical variable with a real field descriptor (D, E, or F).

FOR$IOS_SYNERRFOR. A syntax error was encountered while the RTL was processing a format stored in an array or character variable.

FOR$IOS_OUTCONERR ². 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 situation is encountered, the overflowed field is filled with asterisks to indicate the error in the output record. If no ERR address has been defined for this error, the program continues after the error message is displayed.

FOR$IOS_INPCONERR ². During a formatted input operation, 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.

FOR$IOS_FLTINV. During an arithmetic operation, the floating-point values used in a calculation were invalid for the type of operation requested or invalid exceptional values. For example, when requesting a log of the floating-point values 0.0 or a negative number. For certain arithmetic expressions, specifying the -check nopower option can suppress this message.

FOR$IOS_OUTSTAOVE. An output statement attempted to transfer more data than would fit in the maximum record size.

FOR$IOS_INPSTAREQ. Attempted to read more data than exists in a record with an unformatted READ statement or with a formatted sequential READ statement from a file opened with a PAD specifier value of ' NO ' .

FOR$IOS_VFEVALERR ². 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 1 was assumed, except for a P edit descriptor, for which a value of zero was assumed.

FOR$IOS_SIGINT. The process received the signal SIGINT. Determine source of this interrupt signal (described in signal(3)).

FOR$IOS_INTOVF. During an arithmetic operation, an integer value exceeded byte, word, or longword range. The result of the operation was the correct low-order part. Consider specifying a larger integer data size (modify source program or, for an INTEGER declaration, possibly use the f90 option -integer_size nn ).

FOR$IOS_INTDIV. 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 1.

FOR$IOS_FLTOVF. During an arithmetic operation, a floating-point value exceeded the largest representable value for that data type.

FOR$IOS_FLTDIV. During a floating-point arithmetic operation, an attempt was made to divide by zero.

FOR$IOS_FLTUND. During an arithmetic operation, a floating-point value became less than the smallest finite value for that data type. Depending on the values of the -fpe n option, the underflowed result was either set to zero or allowed to gradually underflow.

FOR$IOS_SIGFPE. A floating-point exception occurred. Core dump file created. Possible causes include:

• Division by zero
• Overflow
• Invalid operation, such as subtraction of infinite values, multiplication of zero by infinity (without signs), division of zero by zero or infinity by infinity
• Conversion of floating-point to fixed-point format when an overflow prevents conversion

FOR$IOS_SIGIOT. Core dump file created. Examine core dump for possible cause of this IOT signal.

FOR$IOS_SUBRNG. An array reference was detected outside the declared array bounds.

FOR$IOS_SIGTERM. The process received the signal SIGTERM. Determine source of this software termination signal (described in signal(3) ).

FOR$IOS_SIGQUIT. The process received the signal SIGQUIT. Core dump file created. Determine source of this quit signal (described in signal(3) ).

FOR$IOS_FLOCONFAI. The attempted unformatted read or write of nonnative floating-point data failed because the floating-point value:

• Exceeded the allowable maximum value for the equivalent native format and was set equal to infinity (plus or minus)
• Was infinity (plus or minus) and was set to infinity (plus or minus)
• Was invalid and was set to not a number (NaN)

Very small numbers are set to zero (0). This error could be caused by the specified nonnative floating-point format not matching the floating-point format found in the specified file.

Check the following:

• Whether the correct file was specified.
• Whether the record layout matches the format Intel Fortran is expecting.
• The ranges for the data being used.
• Whether the correct nonnative floating-point data format was specified.

96

info (96): F_UFMTENDIAN environment variable was ignored:erroneous syntax

FOR$IOS_UFMTENDIAN. Syntax for specifying whether little endian or big endian conversion is performed for a given Fortran unit was incorrect. Even though the program will run, the results might not be correct if you do not change the value of F_UFMTENDIAN. For correct syntax, see Environment Variable F_UFMTENDIAN Method.

108

severe (108): Cannot stat file

FOR$IOS_CANSTAFIL. Attempted stat operation on the indicated file failed. Make sure correct file and unit were specified.

FOR$IOS_OPEREQSEE. Attempted an operation on a file that requires the ability to perform seek operations on that file. Make sure the correct unit, directory path, and file were specified.

FOR$IOS_BRK_RANGE. Break exception generated a SIGTRAP signal (described in signal(3)). Core dump file created.

The cause is an array subscript that is outside the dimensioned boundaries of that array.

Either recompile with the -check bounds option (perhaps with the decfort_dump_flag environment variable set) or examine the core dump file to determine the source code in error.

FOR$IOS_BRK_RANGE2. Break exception generated a SIGTRAP signal (described in signal(3) ). Core dump file created.

The cause is an array subscript that is outside the dimensioned boundaries of the array index n.

Either recompile with the -check bounds option (perhaps with the decfort_dump_flag environment variable set) or examine the core dump file to determine the source code in error.

FOR$IOS_FLTINE. A floating-point arithmetic or conversion operation gave a result that differs from the mathematically exact result. This trap is reported if the rounded result of an IEEE operation is not exact.

FOR$IOS_ROPRAND. The Intel Fortran RTL encountered a reserved operand. Please report the problem to Intel..

FOR$IOS_ASSERTERR. The Intel Fortran RTL encountered an assertion error. Please report the problem to Intel..

FOR$IOS_NULPTRERR. Attempted to use a pointer that does not contain an address. Modify the source program, recompile, and relink.

FOR$IOS_STKOVF. The Intel Fortran RTL encountered a stack overflow while executing your program.

FOR$IOS_STRLENERR. During a string operation, an integer value appears in a context where the value of the integer is outside the permissible string length range.

Either recompile with the -check bounds option (perhaps with the decfort_dump_flag environment variable set) or examine the core file to determine the source code causing the error.

FOR$IOS_SUBSTRERR. An array subscript is outside the dimensioned boundaries of an array.

Either recompile with the -check bounds option (perhaps with the decfort_dump_flag environment variable set) or examine the core file to determine the source code causing the error.

FOR$IOS_RANGEERR. An integer value appears in a context where the value of the integer is outside the permissible range.

FOR$IOS_INVREALLOC. An allocatable array must not already be allocated when you attempt to allocate it. You must deallocate the array before it can again be allocated.

FOR$IOS_RESACQFAI. Failed to acquire a Intel Fortran RTL global resource for a reentrant routine.

For a multithreaded program, the requested global resource is held by a different thread in your program.

For a program using asynchronous handlers, the requested global resource is held by the calling part of the program (such as main program) and your asynchronous handler attempted to acquire the same global resource.

FOR$IOS_INVDEALLOC. A Fortran-90 allocatable array or pointer must already be allocated when you attempt to deallocate it. You must allocate the array or pointer before it can again be deallocated.

FOR$IOS_INVDEALLOC2. A pointer that was passed to DEALLOCATE pointed to an explicit array, an array slice, or some other type of memory that could not be deallocated in a DEALLOCATE statement. Only whole arrays previous allocated with an ALLOCATE statement can be validly passed to DEALLOCATE.

FOR$IOS_SIGSEGV. One of two possible messages occurs for this error number:

• severe (174): SIGSEGV, segmentation fault occurred

  This message indicates that the program attempted an invalid memory reference. Check the program for possible errors.

• severe (174): SIGSEGV, possible program stack overflow occurred

  The following explanatory text also appears:
  Program requirements exceed current stacksize resource limit.

FOR$IOS_SHORTDATEARG. The number of characters associated with the DATE argument to the DATE_AND_TIME intrinsic was shorter than the required length. You must increase the number of characters passed in for this argument to be at least 8 characters in length. Verify that the TIME and ZONE arguments also meet their minimum lengths.

FOR$IOS_SHORTTIMEARG. The number of characters associated with the TIME argument to the DATE_AND_TIME intrinsic was shorter than the required length. You must increase the number of characters passed in for this argument to be at least 10 characters in length. Verify that the DATE and ZONE arguments also meet their minimum lengths.

FOR$IOS_SHORTZONEARG. The number of characters associated with the ZONE argument to the DATE_AND_TIME intrinsic was shorter than the required length. You must increase the number of characters passed in for this argument to be at least 5 characters in length. Verify that the DATE and TIME arguments also meet their minimum lengths.

FOR$IOS_DIV. A floating-point or integer divide-by-zero exception occurred.

FOR$IOS_ARRSIZEOVF. An attempt to dynamically allocate storage for an array failed because the required storage size exceeds addressable memory.

FOR$IOS_UNFIO_FMT. Attempted unformatted I/O to a unit where the OPEN statement (FORM specifier) indicated the file was formatted. Check that the correct unit (file) was specified.

If the FORM specifier was not present in the OPEN statement and the file contains unformatted data, specify FORM= ' UNFORMATTED ' in the OPEN statement. Otherwise, if appropriate, use formatted I/O (such as list-directed or namelist I/O).

FOR$IOS_FMTIO_UNF. Attempted formatted I/O (such as list-directed or namelist I/O) to a unit where the OPEN statement indicated the file was unformatted (FORM specifier). Check that the correct unit (file) was specified.

If the FORM specifier was not present in the OPEN statement and the file contains formatted data, specify FORM= ' FORMATTED ' in the OPEN statement. Otherwise, if appropriate, use unformatted I/O.

FOR$IOS_OPERREQDIS. Attempted to use a BACKSPACE statement on such devices as a terminal or pipe.

FOR$IOS_OPEREQSEQ. Attempted to use a BACKSPACE statement on a file whose organization was not sequential or whose access was not sequential. A BACKSPACE statement can only be used for sequential files opened for sequential access.

FOR$IOS_PROABOUSE. The program called abort to terminate the program.

FOR$IOS_ENDRECDUR. An end-of-record condition was encountered during execution of a nonadvancing I/O READ statement that did not specify the EOR branch specifier.

FOR$IOS_FLOINVEXC. The total number of floating-point invalid data traps encountered during program execution was nn. This message appears at program completion.

FOR$IOS_FLOOVFEXC. The total number of floating-point overflow traps encountered during program execution was nn. This message appears at program completion.

FOR$IOS_FLODIV0EXC. The total number of floating-point divide-by-zero traps encountered during program execution was nn. This message appears at program completion.

FOR$IOS_FLOUNDEXC. The total number of floating-point underflow traps encountered during program execution was nn. This message appears at program completion.