It depends on how you implement told. If you use at-told, write a rule to exclude the source, target, or port and refresh at-Tal. If you are using the web enablement, you can use a par to ignore Tal's setup. We use the enablement toolkit and have parm to control the protocol.
*| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**: [email protected] **|* *Mob**: +972 522 986404 **|* *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|* בתאריך יום ב׳, 14 באפר׳ 2025 ב-20:55 מאת Phil Smith III <[email protected]>: > Is there a way to turn off GSK (System SSL)? We have a customer who had a > problem where our STC suddenly wouldn't start: it would try to connect (to > a server off z/OS) and that would fail. Connectivity SEEMED ok otherwise, > and of course "nothing has changed". A gsktrace produced nothing. After > some back-and-forth, they reIPLed and now it's fine. (Which I 50% wish they > hadn't done, so we could get more info; and am 50% glad they did, of > course, since it fixed the problem!) > > All I can think is that GSK was broken somehow. If there was a > GSKsomething STC I'd kill that and try, see if I got the same symptoms, but > there isn't. Is it just baked into TCP/IP? Any other ideas about something > I can kill that would break GSK? I can do anything I want on our system and > then reIPL if needed. > > Thanks for any ideas. > > ---------------------------------------------------------------------- > 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
