Obviously, AT-TLS and Policy Agent is the long term direction for any services on z/OS. The one thing about GSKKIT, is that the API is multi-platform and policy agent ATTLS is not (that i know of) The cool thing about ATTLS. is a central control point that is not dependent on individual applications to keep their code up to date. I am wondering why not write the client side in java instead of C. On Jun 13, 2014 12:21 AM, "Timothy Sipples" <[email protected]> wrote:
> Oh, you're right, Dave, thanks. I was thinking of how IBM restructured the > TN3270E server to require a separate address space effective with z/OS 1.9 > and higher. That was also when AT-TLS support was introduced for TN3270E, > but it's not mandatory for TLS/SSL. I got those two things mixed up since > they happened in the same z/OS release. > > Anyway, I'm still in favor of AT-TLS for this use case for the other > reasons I cited. Or, at the very least, move on to other line items in the > development list and push that one to lower priority given that AT-TLS is > available. > > > -------------------------------------------------------------------------------------------------------- > Timothy Sipples > IT Architect Executive, zEnterprise Industry Solutions, AP/GCG/MEA > > -------------------------------------------------------------------------------------------------------- > > E-Mail: [email protected] > ---------------------------------------------------------------------- > 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
