System i: Programming Secure Sockets APIs - IBM

writeBuffer (Input)
The pointer to the user-supplied buffer from which the data is to be written.
writeBufSize (Input)
The number of bytes to be written.
amtWritten (Output)
The number of bytes written as a result of this API call.
Authorities
No authorization is required.
Return Value
gsk_secure_soc_write() returns an integer. Possible values are:
[GSK_OK]
gsk_secure_soc_write() was successful.
[GSK_INVALID_HANDLE]
The handle specified was not valid.
[GSK_INVALID_STATE]
The handle is not in the correct state for this operation.
[GSK_INVALID_BUFFER_SIZE]
The readBufSize is less than 1.
[GSK_WOULD_BLOCK]
Operation would have caused the process to be suspended.
[GSK_ERROR_SOCKET_CLOSED]
A close() was done on the socket descriptor for this secure session.
[GSK_AS400_ERROR_CLOSED]
The secure session was closed by another thread before the write completed.
[GSK_AS400_ERROR_INVALID_POINTER]
The writeBuffer or amtWritten pointer is not valid.
[GSK_INTERNAL_ERROR]
An unexpected error occurred during SSL processing.
[GSK_ERROR_IO]
An error occurred in SSL processing; check the errno value.
Error Conditions
When the gsk_secure_soc_write() API fails with return code [GSK_ERROR_IO], errno can be set to:
[EIO]
[ENOTCONN]
[ENOTSOCK]
Input/output error.
Requested operation requires a connection.
Secure Sockets APIs 61