C/C++ Programmer's Guide (G06.25+)

Run-Time Messages
HP C/C++ Programmer’s Guide for NonStop Systems—429301-008
22-23
Environment Messages
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
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 the following 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
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.
Effect. The run-time library terminates your program.
Recovery. Make sure the only defined errno in a program is the one defined in the
native CRE shared run-time library.
276
Cause. environ is defined in the user’s object file. The native CRE reports this error
if environ has been defined in the object file, and it is not the same environ defined
by the native CRE shared run-time library instance data item environ.
Effect. The run-time library terminates your program.
Recovery. Make sure the only defined environ in a program is the one defined in the
native CRE shared run-time library.
Spooler job already started
Ambiguity in application of errno
Ambiguity in application of environ