You may wish to join the TCPIP list. They may also be able to help
TCPIP To subscribe, send mail to lists...@vm.marist.edu with the
command (paste it!) in the e-mail message body:
SUBSCRIBE IBMTCP-L
Or this url and go to the bottom of the webpage:
http://www2.marist.edu/htbin/wlvindex?IBMTCP-L
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Denis
> Sent: Thursday, June 15, 2017 9:24 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: changing batch job to use SSL
>
> Hi Tony,
>
> This is new for me, can you point me to docs how to set up at-tls on windows
> for a tcpip c client program connecting to z/os?
>
> Thanks,
> Denis.
>
>
> -----Original Message-----
> From: Tony Harminc <t...@harminc.net>
> To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU>
> Sent: Thu, Jun 15, 2017 05:05 PM
> Subject: Re: changing batch job to use SSL
>
>
> On 15 June 2017 at 08:02, Denis <
> 000001664d8ede6c-dmarc-<a
> href="mailto:requ...@listserv.ua.edu";>requ...@listserv.ua.edu</a>> wrote:
>
> > AT-TLS is only for the server side, so you also need something for the
> > client side, e.g. stunnel (I am mentioning it, because I have worked
> > with
> > it) or others.
>
>
> This is not right. AT-TLS works fine at the client or server end. You can
> configure it for either or both for any given TCP application. AT-TLS is a
> big thing to understand the details of, and the configuration and debugging
> are particularly and annoyingly difficult, but conceptually it's quite
> simple.
>
> Tony H.
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
