I am not very knowledgeable on this sort of thing. Is AT-TLS something different from SSL? I don't really know. In the z/OS 1.12 Comm Server manuals, I found:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1d490/3.5.3.6 But, me being me, have you considered using the ADDRESS SYSCALL "spawn" to run the curl UNIX command as a child process? Assuming you have the curl ported tool available. It can do SSL encryption. You can set up a couple of pipes to send data to / receive data from the spawn'd curl command. Let it do the "heavy lifting" of TCPIP and SSL. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/BPXZB6A0/3.122 Oh, BTW, I have _not_ done this myself. I have done similar things, but not this specific work. I don't much care for curl. But it does work. On Fri, Jun 21, 2013 at 5:07 PM, Longnecker, Dennis < dennis.longnec...@courts.wa.gov> wrote: > Is it still true you can't encrypt (i.e. SSL) Socket Calls in REXX? I > have some code which does a HTML GET on a webpage on port 80 and the > webmasters want me to run it on port 443 encrypted now. I've been doing > google searches and I found an older reference to it doesn't support it, > but some of the newer manuals reference it. > > Thanks, > > Dennis > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
