System i: Programming Secure Sockets APIs - IBM

One of the following occurred:
v numID cannot be set in the SSL environment after a gsk_environment_init() has been issued.
v numID cannot be set for a secure session after a gsk_secure_soc_init() has been issued.
[GSK_ATTRIBUTE_INVALID_ID]
The numID specified was not valid.
[GSK_ATTRIBUTE_INVALID_NUMERIC_VALUE]
The numValue specified was not valid.
[GSK_INVALID_HANDLE]
A handle was specified that was not valid.
[GSK_ERROR_UNSUPPORTED]
The numID is currently not supported.
[GSK_ERROR_IO]
An error occurred in SSL processing, check the errno value.
Error Conditions
When the gsk_attribute_set_numeric_value() API fails with return code [GSK_ERROR_IO], errno can be
set to:
[EINTR]
Interrupted function call.
[EDEADLK]
Resource deadlock avoided.
[ETERM]
Operation terminated.
If an errno is returned that is not in this list, look in “Errno Values for UNIX-Type Functions” on page 103
for a description of the errno.
Usage Notes
1. The following GSK_NUM_ID values may be set in the SSL environment after
gsk_environment_open() and before gsk_environment_init(). They are used as defaults for
subsequent secure sessions:
v GSK_V2_SESSION_TIMEOUT
v GSK_V3_SESSION_TIMEOUT
v GSK_HANDSHAKE_TIMEOUT
v GSK_OS400_READ_TIMEOUT
2. The following GSK_NUM_ID values may be set for each individual secure session after
gsk_secure_soc_open() and before gsk_secure_soc_init(). These values will override values set in the
SSL environment:
v GSK_FD
v GSK_HANDSHAKE_TIMEOUT
v GSK_OS400_READ_TIMEOUT
3. The following GSK_NUM_ID values are currently not supported in the i5/OS ®
implementation:
v GSK_V2_SIDCACHE_SIZE
Secure Sockets APIs 29