Explanation
An unformatted statement statement
was executed for a unit that was connected for formatted Input/ Output
operations.
An unformatted I/O statement is recognized by the
absence of an FMT specifier. For example, these are unformatted I/O
statements:
WRITE (10) A, B
READ (7, END=88) A, B
These are formatted I/O statements:
WRITE (FMT=*, UNIT=8) A
WRITE (8, FMT=*) A
READ (8, NL1) A
READ (8, *, END=77) A
PRINT 10, A, B, C
The file was connected for formatted
Input/ Output operations because either:
- A value of FORMATTED was given for the FORM specifier on the OPEN
statement,
- The FORM specifier was omitted from the OPEN statement for a file
that was connected for sequential access, or
- The first I/O statement that was executed for a preconnected file
was a formatted I/O statement, that is, an I/O statement with an FMT
specifier.
System action
If neither the ERR nor the IOSTAT specifier is
present on the I/O statement, the condition is signaled. If the condition
is unhandled, the application is terminated.
Qualifying Data:
The basic set of four qualifying data for I/O conditions as shown
in Table 1. Within this basic set, parm_count has
a value of 4.
| Name |
Action Taken sfter Resumption |
|---|
| RN |
The I/O operation is ignored, and execution continues. |
Programmer response
Determine if you want to perform formatted
or unformatted Input/ Output operations on the file. If you want to
use formatted I/O statements, remove or change the unformatted I/O
statements.
If you want to use unformatted I/O statements,
then:
- For an OPEN statement that connects a file for sequential access,
provide a FORM specifier with a value of UNFORMATTED.
- For an OPEN statement that connects a file for direct or keyed
access, either omit the FORM specifier or provide one with a value
of UNFORMATTED.
- Do not execute a formatted I/O statement for the unit.
Symbolic Feedback Code
FOR1200