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

System Functions (w) write(2)
• The processor for the disk process of the specified file failed during an
input or output operation, and takeover by the backup process occurred.
• The open file descriptor has migrated to a new processor, but the new
processor lacks a resource or system process needed for using the file
descriptor.
The file descriptor specified by the filedes parameter can only be closed.
For all other error conditions, errno is set to the appropriate Guardian file-system error number.
See the Guardian Procedure Errors and Messages Manual for more information about a specific
Guardian file-system error.
RELATED INFORMATION
Functions: creat(2), creat64(2), fcntl(2), lseek(2), lseek64(2), open(2), open64(2), pipe(2),
socket(2), spt_writez(2), ulimit(3).
STANDARDS CONFORMANCE
The HP implementation does not generate the SIGXFSZ signal.
The POSIX standards leave some features to the implementing vendor to define. These features
are affected in the HP implementation:
• Calls to the write() function with the nbytes parameter equal to 0 are supported for all
regular and nonregular files.
• After reading from a device that is incapable of seeking, the value of the file pointer is
always 0 (zero).
• Specifying a value for the nbytes parameter that is greater than SSIZE_MAX causes the
write() function to return -1 and set errno to [EINVAL].
• errno can be set to [EIO] if a physical I/O error occurs.
HP extensions to the XPG4 Version 2 specification are:
• The errno values [ECONNRESET], [EFAULT], [EGUARDIANLOCKED], [EINVAL],
[ENETDOWN], [ENOTCONN], [ETIMEDOUT], and [EWRONGID] can be returned.
• For systems running J06.07 and later J-series RVUs or H06.18 and later H-series RVUs,
the errno value [ENOMEM] can be returned when there is not enough system memory
available to complete the operation.
The use of this function with the POSIX User Thread Model library conforms to industry stan-
dards as follows:
• IEEE Std 1003.1-2004, POSIX System Application Program Interface
• When a signal arrives during a call to a thread-aware write( ) function, the thread-aware
write() retries the I/O operation instead of returning the errno value [EINTR] with the
following exception. If the thread-aware fork() function is called by a signal handler
that is running on a thread performing a thread-aware write( ) call, the thread-aware
write() call in the child process returns [EINTR] to the application.
527186-023 Hewlett-Packard Company 10−19