C/C++ Programmer's Guide (G06.27+, H06.08+, J06.03+)

83
Operation incompatible with file type or status (error)
Cause
The program attempted an operation on a file whose type or current status is unsuitable for
execution of that operation. For example, a COBOL program calls a file manipulation utility for
a file that is using Fast I/O. error, if present, is as file-system error number.
Effect
Program behavior is language and application dependent.
Recovery
Change the program so that it does not attempt the operation on an unsuitable file.
90
Open conflicts with open by other language
Cause
Routines written in two different languages—for example, COBOL and FORTRAN—attempted
to open a connection to a file using the same logical name. This error is not reported for standard
files.
Effect
Program behavior is language and application dependent.
Recovery
Modify your program to use different logical names or coordinate logical names between the
two routines so that they do not open the same logical file at the same time.
91
Spooler job already started
Cause
A FORTRAN routine attempted to open a spooler but the spooler was already open with attributes
that conflict with those in the current open. This error is reported only for an open to standard
output and only if one or more of these are true:
• The spooling levels of the two opens are different.
• The new open specifies any level-2 arguments.
Effect
If the rejected request was initiated from a FORTRAN I/O statement that includes either an
IOSTAT or ERR parameter, control is returned to the FORTRAN routine. Otherwise, the FORTRAN
run-time library terminates the program.
Recovery
Coordinate how routines in your program use standard output.
Environment Messages
275
Ambiguity in application of errno
Cause
errno is defined in the user’s object file. The native CRE reports this error if errno has been
defined in the object file, and it is not the same errno defined by the native CRE shared run-time
library instance data item errno.
Environment Messages 381