In your Pagent config, on the TcpImage statement, are you coding the FLUSH and PURGE options?
If so, when you recycle Pagent, it should then pick up the new settings. You can also use the Modify Refresh command which should flush the old settings, so that you don't have to stop/start the started task. David -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Skippy the Ancient Sent: Wednesday, August 5, 2020 2:33 PM To: [email protected] Subject: Pagent hangover I'm working with Pagent, adding an FTPS started task and port. (because the client said so) It was getting some sort of TTLS rule error. I saved the current ATTLS member off and pulled in the sample ATTLS from /usr/lpp/tcpip/samples/pagent_TTLS.conf. I issued a refresh. PASEARCH shows the changes have been picked up. Or have they? I turn debug logging on for my FTPS demon. I see a handshake error, just as before. In fact, the log shows it's using the old ATTLS values. PASEARCH still shows the changes I expect. OK. Fine. Drop all these started tasks; FTPD, FTPSD, PAGENT, SYSLOGD. Start all. PASEARCH shows the new changes. Debug still shows old rule values that aren't even in ATTLS member any more. What am I doing wrong? Thank you for your time, Skippy the Ancient. And puzzled. ---------------------------------------------------------------------- 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
