You have laid the ground work to be able to use SSL in your program, however, the next step is the difficult part. You will have to reengineer your application to create the SSL environment and make secure calls. As others have suggested, AT-TLS is the route to follow here. You will be able to use a secure connection without rewriting your code.
Regards. -- Donald Grinsell, Systems Programmer Enterprise Technology Services Bureau SITSD/Montana Department of Administration 406.444.2983 (D) "If you think training is expensive, try ignorance." ~ Peter Drucker > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Munif Sadek > Sent: Friday, June 09, 2017 8:22 PM > To: [email protected] > Subject: changing batch job to use SSL > > Dear Listers > I have a pure COBOL batch job that uses socket programming (EZASOCKET) to > fetch some sensitive data from an external server. I would like to change > this IP connection between Mainframe (Client) and External server > (Specialized Application Server that does support SSL/TLS) to be secure. > > > I have installed Server Public Certificate ( with CA certificate /TRUST) to a > key ring and made this batch user the owner of the ring. Still the batch job > is not trying to communicate SSL. > > We are z/OS 2.1 and z/OS HTTP / HTTPS enabler is not available to us. Can > Cobol program support SSL? > > If I must implement TLS, can someone please give me some pointers. > > regards Munif. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
