>Since our host servers are not mainframes, can we let customers use >AT-TLS, and what do we need to do on our side?"
Yes, and probably nothing. It's just TLS. >asked to provide a job to customers to use AT-TLS on their mainframes. It's not a "JCL problem" on the client end. It is a Policy Agent configuration chore. Charles On Wed, 13 Nov 2024 14:58:37 +0000, Billy Ashton <bill00ash...@gmail.com> wrote: >Hi all, I was asked by a friend of mine at another company to ask a >question here about using FTP client jobs with AT-TLS. He works for a >major company and wants to see how others do this. > >His question is this: "We currently handle support tickets from >customers, and they often need to send mainframe files to us. Right now, >we allow plain old FTP (using port 21) and secured FTP (also port 21 >plus some other random port, using the AUTH command), and we also >support the use of SFTP from the Unix side via port 22. We have been >asked to provide a job to customers to use AT-TLS on their mainframes. >Since our host servers are not mainframes, can we let customers use >AT-TLS, and what do we need to do on our side?" > >I have done a lot of things over the years, but networking isn't my >skillset, and doesn't sound like a bundle of fun. Can any of you fine >folks help my friend Jim? If it is only some JCL needed and you wold >share a sample, that would be great. Or if you have a website or pdf to >help him and me understand this better, please pass it on! I keep >hearing more about AT-TLS, so I figure I might want to learn a little >bit about it. > >Thank you and best regards, >Billy Ashton > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN