System i: Programming Secure Sockets APIs - IBM

matched sets. If a client application writes 100 bytes of data using one or more of the socket send()
calls, then the server application must read exactly 100 bytes of data using one or more of the socket
recv() calls. This is also true for gsk_secure_soc_read() API.
3. Since SSL is a record-oriented protocol, SSL must receive an entire record before it can be decrypted
and any data returned to the application. Thus, a select() may indicate that data is available to be
read, but a subsequent gsk_secure_soc_read() may hang waiting for the remainder of the SSL record
to be received when using blocking I/O.
4. A FIONREAD ioctl() cannot be used to determine the amount of data available for reading by using
gsk_secure_soc_read().
5. SSL will ignore the out-of-band (OOB) data indicator. OOB will not affect the SSL application. OOB
will just be data to the SSL protocol.
6. For an SSL enabled socket, which must use a connection-oriented transport service (that is, TCP), a
returned value of zero in the amtRead field indicates one of the following:
v The partner program has issued a close() for the socket.
v The partner program has issued a secure close for the secure session. For example, if the partner
program was coded using the GSKit APIs, the partner issued gsk_secure_soc_close().
v The partner program has issued a shutdown() to disable writing to the socket.
v The connection is broken and the error was returned on a previously issued socket function.
v A shutdown() to disable reading was previously done on the socket.
7. When the secure session uses a blocking socket and GSK_OS400_READ_TIMEOUT was set,
GSK_OS400_ERROR_TIMED_OUT will be the return value if no data arrives before the timeout
expires.
Error Messages
Message ID Error Message Text
CPE3418 E Possible APAR condition or hardware failure.
CPF9872 E Program or service program &1 in library &2 ended. Reason code &3.
CPFA081 E Unable to set return value or error code.
Related Information
v “gsk_secure_soc_close()—Close a secure session” on page 37—Close a secure session
v “gsk_secure_soc_init()—Negotiate a secure session” on page 38—Negotiate a a secure session
v “gsk_secure_soc_misc()—Perform miscellaneous functions for a secure session” on page 41—Perform
miscellaneous functions for a secure session
v “gsk_secure_soc_open()—Get a handle for a secure session” on page 44—Get a handle for a secure
session
v “gsk_secure_soc_write()—Send data on a secure session” on page 60—Send data on a secure session
v “gsk_strerror()—Retrieve GSKit runtime error message” on page 62—Retrieve GSK runtime error
message
API introduced: V5R1
Top | UNIX-Type APIs | APIs by category
gsk_secure_soc_startInit()—Start asynchronous operation to negotiate
a secure session
Syntax
48 System i: Programming Secure Sockets APIs