System i: Programming Secure Sockets APIs - IBM
System i: Programming Secure Sockets APIs - IBM
System i: Programming Secure Sockets APIs - IBM
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Error Messages<br />
Message ID Error Message Text<br />
CPE3418 E Possible APAR condition or hardware failure.<br />
CPF9872 E Program or service program &1 in library &2 ended. Reason code &3.<br />
CPFA081 E Unable to set return value or error code.<br />
Usage Notes<br />
1. You must do a gsk_secure_soc_close() if a prior gsk_secure_soc_open() was successful.<br />
Related Information<br />
v “gsk_secure_soc_init()—Negotiate a secure session”—Negotiate a secure session<br />
v “gsk_secure_soc_misc()—Perform miscellaneous functions for a secure session” on page 41—Perform<br />
miscellaneous functions for a secure session<br />
v “gsk_secure_soc_open()—Get a handle for a secure session” on page 44—Get a handle for a secure<br />
session<br />
v “gsk_strerror()—Retrieve GSKit runtime error message” on page 62—Retrieve GSK runtime error<br />
message<br />
API introduced: V5R1<br />
Top | UNIX-Type <strong>APIs</strong> | <strong>APIs</strong> by category<br />
gsk_secure_soc_init()—Negotiate a secure session<br />
Syntax<br />
#include <br />
int gsk_secure_soc_init(gsk_handle my_session_handle);<br />
Service Program Name: QSYS/QSOSSLSR<br />
Default Public Authority: *USE<br />
Threadsafe: Yes<br />
The gsk_secure_soc_init() function is used to negotiate a secure session, using the attributes set for the<br />
SSL environment and the secure session. This API does the SSL handshake to the remote peer; upon<br />
successful completion, you have a secure session established.<br />
Parameters<br />
my_session_handle (Input)<br />
The handle for this secure session that was obtained through the gsk_secure_soc_open() API call.<br />
Authorities<br />
Authorization of *R (allow access to the object) to the certificate store file and its associated files is<br />
required. Authorization of *X (allow use of the object) to each directory of the path name of the certificate<br />
store file and its associated files is required.<br />
Return Value<br />
gsk_secure_soc_init() returns an integer. Possible values are:<br />
38 <strong>System</strong> i: <strong>Programming</strong> <strong>Secure</strong> <strong>Sockets</strong> <strong>APIs</strong>