FORTRAN Reference Manual

Run-Time Diagnostic Messages
FORTRAN Reference Manual—528615-001
G-11
Formatter Run-Time Messages
267
Cause. A routine tried to transfer a record that is larger than the maximum record
length specified for the unit. The maximum record length is established at the time a
unit is connected to a file. For more details, see the OPEN Statement on page 7-70.
Effect. If the program executed an I/O statement that includes an ERR clause or an
IOSTAT clause, the program retains control. Otherwise, the run-time library terminates
your program.
Recovery. Specify a larger buffer size either in a UNIT directive or in a TACL ASSIGN
command.
270
Cause. The formatter encountered a right parenthesis with more data remaining to be
formatted. However, no data was written as a result of the formats within the current
set of parentheses. In the following example, the WRITE statement never completes
because there are two values to write, I and J. The value of I is output but the
formatter would repeatedly scan the 2X specification and the value of J would never be
written:
WRITE(6, 100) i, j
100 FORMAT(1X, I4, (2X))
Effect. If the program executed an I/O statement that includes an ERR clause or an
IOSTAT clause, the program retains control. Otherwise, the run-time library terminates
the program.
Recovery. Modify your FORMAT statement to account for all data specified in the
WRITE statement.
271
Cause. An item in the data list of an I/O statement is incompatible with its
corresponding actual value or format edit descriptor. For example, a data item is a
REAL value but the current item descriptor expects an integer:
WRITE(6, 100) r
100 FORMAT(1X, I4)
Buffer overflow for unit nnn
Format loopback for unit nnn
Edit item mismatch for unit nnn