Here are my AUTOLOG statements from the TCP/IP profile: AUTOLOG 5 PAGENT ; AT-TLS Policy server GPMSERVE DELAYSTART TTLS ; RMF Server TSOFRONT DELAYSTART TTLS ; TSO Startup TN3270E DELAYSTART TTLS ; TN3270 Server FTPD JOBNAME FTPD1 DELAYSTART TTLS ; FTP Server CSFTTKE DELAYSTART TTLS ; TKE Server CFZCIM DELAYSTART TTLS ; CIM Server SSHD DELAYSTART TTLS ; SSH Server ENDAUTOLOG
Notice we hold the startup of the started tasks until PAGENT is running. Matthew On Fri, 16 Sep 2022 08:53:55 -0500, Jantje. <jan.moeyers...@gfi.be> wrote: >Esteemed Listers, > >As we are required to support TLSv1.2 for our TN3270 sessions, we are now >implementing AT-TLS. Using the 'IBM Personal Communications and IBM z/OS TTLS >Enablement' Redpaper, I have the configuration of the PAGENT, TCPIP and TELNET >regions going. Remains to decide what is the correct way of starting it all >up... > >The Redpaper says I have to add an AUTOLOG statement for PAGENT to the TCPIP >profile. However, the 'AUTOLOG considerations' paragraph in the 'IP >Configuration Guide' gives a complicated explanation from which we take away >that I should not be using the AUTOLOG because in our installation, it will >not be listening on any port. > >The Redpaper states that 'The task (PAGENT) should remain up.' However, when I >stop it after TCPIP has come up, nothing harmful seems to happen and new >TN3270 sessions can start up quite fine. > >So, what is the best practice, please? > >Thanks and very best regards, > >Jantje. > > >P.S. We have System Automation and can use that for starting and stopping if >needed. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
