Fortran 77 Runtime Error Messages

December 1, 1998

If an error occurs when a FORTRAN program is running, the program displays an error message to standard error. These run-time error messages begin with:

*** message category nnn: message

message category can be any of the following:

FORTRAN I/O ERROR
FORTRAN RANGE ERROR
FORTRAN SHARED COMMON ERROR
FORTRAN MEMORY ALLOCATION ERROR
FORTRAN ISAM ERROR

nnn is the error number.

message is the error message.

     FILE: file, UNIT: unit
     LAST FORMAT: xxx

file is the name of the file upon which I/O failed.
unit is the unit number associated with the file.
fmt is the most recent format attempted or completed.

__________________________________________________________________________________

NOTE  The run-time diagnostics are distinct from the compilation diagnostics.

      Several meanings are given for many error messages.  Usually, only one
      is applicable.  Where more than one programmer action is given, try only
      one at a time, and recompile and run the program each time.

__________________________________________________________________________________

The IOSTAT error number.
The error message.
A more thorough explanation of message.
Appropriate programmer actions to take.

Format specification contains unrecognizable code or string, contains an impossible format (for example, F0.s or G2.9), or a format descriptor describes a field too wide for internal buffers, or the value of a variable-format expression is out of range.

Change the format specification to the proper syntax or value.

Unit number was not greater than or equal to zero.

Use a nonnegative unit number.

Formatted I/O was attempted on a file opened for unformatted I/O. Open the file for formatted I/O; do unformatted I/O on this file.

Unformatted I/O was attempted on a file opened for formatted I/O.

Open the file for unformatted I/O; do formatted I/O on this file.

Direct operation attempted on sequential file; direct operation attempted on opened file connected to a terminal.

Use sequential operations on this file; open file for direct access; do not do direct I/O on a file connected to a terminal.

Found repeat value, but no asterisk; first character after optional decimal point was not "T" or "F".

Change input data to correspond to syntax expected by list-directed input of logicals; use input statement that corresponds to syntax of input data.

Found repeat value, but no asterisk; characters not delimited by quotation marks.

Change input data to correspond to syntax expected by list-directed input of characters; use input statement that corresponds to syntax of input data.

Tried to open a file that the system would not allow for one of the following reasons:

• Access to the file was denied by the file system due to access restriction.


• The named file does not exist.


• Type of access request is impossible.

Correct the path-name to invoke the file intended.

Attempted a BACKSPACE, REWIND, or ENDFILE on a terminal or other device for which these operations are not defined.

Do not use BACKSPACE, REWIND, or ENDFILE.

Tried to do I/O on record of a file past beginning or end of record.

Perform I/O operation within bounds of the record; increase record length.

While reading complex data, one of the following problems has occurred:

• No left parenthesis and no repeat value.


• Found repeat value, but no asterisk.


• No comma after real part.


• No closing right parenthesis.

Change input data to correspond to syntax expected by list-directed input of complex numbers; use input statement corresponding to syntax of input data.

Library cannot allocate an I/O block (from an OPEN statement), parse array (for formats assembled at run-time), file name string (from OPEN), characters from list-directed read, ISAM key descriptor, shared COMMON descriptor, variable-format descriptor, or file buffer. The program may be trying to overwrite a shared memory segment defined by another process.

Allocate more free space in the heap area (see the beginning of this chapter); open fewer files; use FORMAT statements in place of assembling formats at run time in character arrays; read fewer characters; user fewer ISAM keys; use fewer shared COMMON areas; use fewer variable-format expressions; or reduce the maximum size of file records.

Unit specified in I/O statement has not previously been connected to anything.

Connect unit (that is, OPEN it) before attempting I/O on it; perform I/O on another, already connected, unit.

Read a character that is not admissible for the type of conversion being performed; input a value into a variable that was too large for the type of the variable.

Remove from input data any characters that are illegal in integers or real numbers.

An illegal character was read when logical data was expected.

Change input data to correspond to syntax expected when reading logical data; use input statement corresponding to syntax of input data.

Executed OPEN statement with STATUS='SCRATCH', but also named the file.

Either open file with STATUS='SCRATCH', or name the file in an OPEN statement.

Executed OPEN statement with STATUS='NEW', but file already exists.

Use OPEN without STATUS specifier, or with STATUS='OLD', or STATUS='UNKNOWN'.

Executed an OPEN statement with ACCESS='KEYED' on a new file but the KEY= specifier is missing.

Executed OPEN statement with a UNIT specifier that is already associated with a different file name.

Use an OPEN statement with a UNIT specifier that is not connected to a file name; open the connected file to the same unit name.

OPEN statement specified FORM='UNFORMATTED' and BLANK=xx.

Use either FORM='FORMATTED' or BLANK=xx when opening files.

Attempted to read a record of a formatted or unformatted direct file that is beyond the current end-of-file.

Read records that are within the bounds of the file.

FORM specifier did not begin with "F", "f", "U", or "u".

Use either 'FORMATTED' or 'UNFORMATTED' for the FORM specifier in an OPEN statement.

The file specified in the CLOSE statement was previously opened with 'SCRATCH' specified in the STATUS specifier.

Open the file with a STATUS other than 'SCRATCH'; do not specify STATUS='KEEP' in the CLOSE statement for this scratch file.

STATUS specifier did not begin with "O", "o", "N", "n", "S", "s", "U", or "u".

Use 'OLD', 'NEW', 'SCRATCH', or 'UNKNOWN' for the STATUS specifier in OPEN statement.

STATUS specifier did not begin with "K", "k", "D", or "d".

Use 'KEEP' or 'DELETE' for the STATUS specifier in a CLOSE statement.

ACCESS specifier did not begin with "K", "k", "S", "s", "D", or "d".

Use 'SEQUENTIAL' or 'DIRECT' for the ACCESS specifier in an OPEN statement.

OPEN statement has ACCESS='DIRECT', but no RECL specifier.

Add RECL specifier; specify ACCESS='SEQUENTIAL'.

RECL specifier in OPEN statement was less than or equal to zero.

Use a positive number for RECL specifier in OPEN statement.

BLANK specifier did not begin with "N", "n", "Z", or "z".

Use 'NULL' or 'ZERO' for BLANK specifier in OPEN statement.

End-of-file mark read by a READ with no END= specifier indicating a label to which to jump.

Use the END= specifier to handle the EOF; check logic.

Record number less than one was specified for direct I/O.

Use record numbers greater than zero.

A character string was read for a numerical or logical variable.

Check input data and input variable type.

Output requested is too long for specified (or preexisting) record length.

Make the number of bytes output by WRITE less than or equal to the file record size.

More bytes of I/O were requested than exist in the current record.

Match the format to the data record.

An index to an array or substring reference was outside of the declared limits at the specified statement number.

Check all indexes to arrays and substrings in and around the given statement number.

The value of the variable did not correspond to any of the labels in the list in an assigned GOTO statement.

Check for a possible logic error in the program or an incorrect list in the assigned GOTO statement at or near the given statement number.

A DO loop with a zero increment has produced an infinite loop.

Check for a logic error in or near the given statement number.

No format descriptor was found to match I/O list items.

Add at least one repeatable edit descriptor to the format statement.

An empty format, (), was used with the list items specified.

Remove the items from I/O list; fill in the format specifications with the appropriate format descriptors.

OPEN statement is incomplete.

Change the STATUS specifier to 'SCRATCH' or 'UNKNOWN'; or add the file specifier.

The file system returned an error status during an I/O operation.

See the associated file system error message.

A numeric item in the I/O list was matched with a nonnumeric format descriptor.

Match format descriptors to I/O list.

A character item in the I/O list was matched with a format descriptor other than "A" or "R".

Match format descriptors to I/O list.

A logical item in the I/O list was matched with a format descriptor other than "L".

Match format descriptors to I/O list.

Format did not begin with a left parenthesis.

Begin format with a left parenthesis.

Format descriptor did not begin with a character that can start a legal format descriptor.

Specify correct format descriptor.

Format error: Character in the set IFEDGMNK@OLAR(PHX expected and not found.

Specify correct format descriptor to follow number.

The specifier being scaled is not "F", "E", "D", "M", "N", or "G".

Scale only specifiers for floating-point I/O.

Too many left parentheses for the format processor to stack.

Nest parentheses less deeply.

A specifier beginning with "T" is not a correct tab specifier.

Correct the specifier beginning with "T".

A specifier beginning with "B" did not have "N" or "Z" as the next character.

Correct the specifier beginning with "B".

The end of the format was reached when another specifier was expected.

Check the end of the format for a condition that would lead the processor to look for another specifier (possibly a missing right parenthesis).

Other specifier found when /, :, or ) expected.

Insert separator where needed.

Number not found following format descriptor requiring a field width.

Specify field width where required.

No period was found to specify the number of decimal places in an "F", "G", "E", or "D" format descriptor.

Specify the number of decimal places for the field.

More right parentheses than left parentheses were found.

Correct format so parentheses balance.

String extends past the end of the format or is too long for buffer.

Check for unbalanced quotation mark or for "H" format count too large; or break up long string.

Record length specified in redundant OPEN conflicted with the value as opened.

Only BLANK= specifier may be changed by a redundant OPEN.

An attempt was made to transfer more characters than internal file length.

Match READ or WRITE with internal file size.

The file number requested to be set was not a legal file system file number.

Check that the OPEN succeeded and the file number is correct.

An illegal character was found in NAMELIST-directed input.

Be sure input data conforms to the syntax rules for "NAMELIST"-directed input; remove illegal character from data.

An invalid subscript or substring specifier was found in NAMELIST-directed input. Possible causes: bad syntax, subscript/substring component out-of-bounds, wrong number of subscripts, substring on non-CHARACTER variable.

Check input data for syntax errors. Be sure subscript/substring specifiers are correct for data type; specify only array elements within the bounds of the array being read.

Too many input values were found during a NAMELIST-directed READ. This message will be generated by attempts to fill variables beyond their memory limits.

Supply only as many values as the length of the array.

A variable name was encountered in the input stream which was not declared as part of the current NAMELIST group.

Read only the variables in this NAMELIST.

An illegal NAMELIST I/O operation was attempted on an unformatted (binary) file.

OPEN file with FORM='FORMATTED'; use NAMELIST I/O only on

The size of the shared memory segment is less than the system-imposed minimum or greater than the system-imposed maximum.

Change the size of the shared memory segment or shared common to be within the valid size.

Permission has been denied in either creating or attaching to the existing shared memory segment.

Check the user id and consult with your system manager.

The name/ID of the shared memory segment is too large.

Decrease the size of the name/ID.

There is not enough available memory to allocate the segment.

Decrease the size requested; inspect the current allocations with ipcs -m and free unreleased or unused segments; consult with your system manager to increase

There is insufficient permission to LOCK the shared memory segment.

Check the user ID and permissions and change as appropriate.

You have exceeded the system imposed limit of the maximum shared memory segments attached to a process.

Remove any unreleased or unused segments; consult your system manager to increase the limit.

Automatic arrays will implicitly cause a request for memory to be made at the start of the subprogram containing the automatic array. For allocatable arrays, the user explicitly requests space using the ALLOCATE statement. In either case, the underlying dynamic memory allocation system reports that there is insufficient space to honor the request.

Free other allocatable arrays before allocating this one. Also, be sure that all allocatable arrays are deallocated in each procedure prior to return, to insure that memory is not being "lost."

Also, check that the correct amount of space is being requested. For example, the bounds expression defining the size of an automatic array may have a value much larger than expected.

An allocatable array listed in the ALLOCATE statement had an allocation status of currently allocated.

Check to insure that every array listed in the ALLOCATE statement has either never been allocated or has been subsequently deallocated (with the DEALLOCATE statement). Using the ALLOCATED intrinsic before this statement may be helpful in finding the allocatable array which is causing the problem.

An allocatable array listed in the DEALLOCATE statement had an allocation status of not currently allocated.

Check to ensure that every array listed in the DEALLOCATE statement has been allocated with an ALLOCATE statement. Use of the ALLOCATED intrinsic before this statement may be helpful in finding the allocatable array which is causing the problem.

The stride value given in a section triplet reference has a value of zero.

Check the strides of the array sections given in the line indicated in the message.

Arrays used together in expressions must be conformable (of the same shape). In some cases, when the bounds of the arrays are constant, this violation can be detected at compile-time. When the bounds are non-constant, and a conformance violation is detected, this message is issued.

This error is only be generated if the $RANGE compiler directive or the -C compile-line option is enabled.

Check the shapes of the arrays involved. The use of non-conformant arrays is not a valid operation, and generally indicates a problem in the program.

You attempted to add a duplicate value to an index with WRITE or REWRITE. Duplicate values are not allowed for the primary key. Duplicate values are allowed for alternate keys.

Check for duplicate key values and change them to be unique.

A value on an ISAM statement is not within the range of acceptable values.

One or more of the key elements that make up the key description is outside the range of acceptable values for that element on an ISAM OPEN statement.

The maximum number of ISAM files that can be open at one time would be exceeded if this request were processed.

Close a file before opening another one.

The format of the C-ISAM file has been corrupted.

Informix's bcheck program may be able to repair the problem.

The record requested by this call cannot be accessed because it has been locked by another user. A record is automatically locked when it is read.

If a record will not be updated, it should be unlocked with UNLOCK so that other users can read it.

You defined the same key two or more times in an OPEN statement.

A record could not be found that contained the requested value in the specified position with a READ statement.

Check the value given. Modify your program to handle this situation.

This call must operate on the current record. The current record is not defined.

READ the appropriate record before performing this operation.

The lock file cannot be created.

Check the directory permissions.

Adequate memory cannot be allocated.

Increase the swap space.

The log file record cannot be read.

You cannot use the Network File Server with ISAM. ISAM files must be local rather than accessed over a network.

Make sure that the directory where you want to open your ISAM file is not NFS-mounted.

ISAM has encountered a bad record number. Probably, an ISAM index file has been corrupted.

Informix's bcheck may be able to repair the problem.

The ISAM record does not contain a primary key.

No logging.

Too many users are using C-ISAM.

Dbspace not found.

There is not enough free disk space.

Delete unnecessary files.

The ISAM record is too long.

No more locks exist for ISAM.

ISAM demo limits have been exceeded.