Jon, The program can be easily modified to aggregate records based on the user exit flags. for example adding exitPtr.uexitvalue = sindx. Eny record having a user exit value will be handled by extracting the value, getting the sindx to the log array and chain the current record to it.
BTW, I updated the program to print commands listed in syslog which are not black listed (for example SE in eoj. ITschak *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522 986404 **|* *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|* On Thu, Jul 24, 2025 at 8:12 PM Jon Perryman <jperr...@pacbell.net> wrote: > On Thu, 24 Jul 2025 08:56:42 +0300, Itschak Mugzach < > i_mugz...@securiteam.co.il> wrote: > > >My code solves the issues with multiline msgs, allow search, and lookup of > >task number to task name. see below, it is free! > > You should take great pride in this program but you need to be honest > about what it can achieve. Your program uses syslog which cannot solve > "all" multi-line message issues. If we can't do it in automation products > with all information available, then you can't completely solve it with > minimal information. There's a reason why some automation products provide > the ability to process secondary messages as single messages, single > message related to the primary message or as a complete MLWTO. > > I suspect that for most people, your solution will meet the needs for most > people but they should always keep in mind that if something doesn't feel > right, then they need to dig deeper. > > As an alternative, OPERLOG gives you much of the information seen by > automation products but remember there will still be a few situations not > easily solvable and operlog overhead may outweigh its benefits. In > addition, OPERLOG requires the use of a program interface. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
