A decent automation package should be able to handle autolog processing. I negotiated without our network folks to create a "null" autolog policy so I could add those tasks to our automation: AUTOLOG ENDAUTOLOG
The TCPPARMS is composed of several INCLUDE statements, referencing different members, so it was an easy process to OBEYFILE that specific "nullification" member at conversion time, while still having a fully defined autolog policy for backout. On Thu, Aug 18, 2022 at 11:41 AM Lionel B. Dyck <lbd...@gmail.com> wrote: > It is and that is the plan for if nothing else works. And I suspect that > will be the solution. The other option is to determine if our automation > product can replace the autolog. > > > Lionel B. Dyck <>< > Website: https://www.lbdsoftware.com > Github: https://github.com/lbdyck > > “Worry more about your character than your reputation. Character is what > you are, reputation merely what others think you are.” - - - John Wooden > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
