BTW, hopefully by "with SSL" you mean "with the GSK SSL library." SSL the protocol is totally deprecated (all versions). Fortunately, GSK supports TLS (and BTW is a GREAT package -- spoken by someone with experience with both GSK and with OpenSSL, which is a roughly "competitive" package).
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Robin Atwood Sent: Thursday, March 10, 2016 5:10 AM To: [email protected] Subject: Linking C module with SSL I am trying to convert an XL/C module to use SSL. From the pre-link-edit step I get messages like: @ST00010 gsk_environment_init and then from the link-edit: IEW2456E 9207 SYMBOL @ST00010 UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY. The routines I need are in SYS1.SIEALNKE(GSKSSL). I have added this library to SYSLIB in both the pre-linker and link-edit step, included it in the SYSIN and SYSLIN, but nothing works. The manual says: Include the /usr/lib/GSKSSL.x or /usr/lib/GSKSSL64.x sidedeck in the prelink or bind step input. But that is not very helpful with JCL (and eventually SCLM). Has anyone any idea how to do this? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
