Open System Services System Calls Reference Manual (G06.29+, H06.08+, J06.03+)

open(2) OSS System Calls Reference Manual
The function call specified the O_CREAT flag but did not specify the
mode parameter.
The O_CREAT flag is set and bits other than the file permission and
appropriate file type flags are set in the mode parameter.
Both the O_TRUNC flag and O_RDONLY ag are set.
None of the access flags O_RDONLY, O_WRONLY,orO_RDWR are
set.
The function call attempted to create a Guardian file (that is, a file in the
/G le system), but the pathname cannot be mapped to a valid Guardian
lename.
The function call attempted to open a Guardian file of a type other than
those permitted.
The function call attempted to create a Guardian temporary file.
[EIO] A physical input or output error occurred. The device where the file is stored
might be in the down state, or both processors that provide access to the device
might have failed.
Data might have been lost during transfer.
[EISDIR] One of these conditions exists:
The named file is an OSS directory, and write access is requested.
The named file is a Guardian directory (/G or a directory in the /G file
system).
[ELOOP] Too many symbolic links were encountered in translating the path parameter.
[EMFILE] The system limit for open file descriptors per process has reached the maximum
permitted.
[ENAMETOOLONG]
One of these names is too long:
The pathname pointed to by the path parameter
A component of the pathname pointed to by the path parameter
The intermediate result of pathname resolution when a symbolic link is
part of the path parameter
You can call the pathconf() function to obtain the applicable limits.
[ENETDOWN]
The call was blocked during access to a FIFO, and communication has been lost
with the remote node containing the other end of the FIFO.
[ENFILE] One of these conditions exists:
The maximum number of file descriptors of this file type (socket, pipe,
etc.) for this processor are already open.
512 Hewlett-Packard Company 527186-023