By parallel run, I mean letting the current, split-up behaviour remain the canonical way/source, and writing a secondary feed with wide records. This'll allow automation tools to switch over piece by piece (if & where needed), and then default to the wide records format.
Sent with Proton Mail secure email. On Thursday, July 24th, 2025 at 01:21, Michael Oujesky <[email protected]> wrote: > Define "parallel run". > > IEAMDBLG reads from the OPERLOG stream (SYSPLEX.OPERLOG), not JES2 SYSLOG. > > As long as the legacy tools accept a longer LRECL, they will work as > the record format is the same as JES2 SYSLOG (HCL for 2-digit years > or HCR for 4-digit years), but with a longer data length and fewer or > no continuation records. > > The 255 LRECL is driven by use of the MVC instruction to build the > output record and could be extended further by a more extensive > modification using looped MVCs or MVCL. > ** Local revisions: > * > * 1. LRECL of SYSLOG increased from 132 to 255 (could be longer, > * but moves would have to be changed from MVC) > * 2. COPY keywords "YESTERDAY" and "LASTWEEK" added > * 3. time/date capture moved to initialization > * 4. LOGBUF moved to end of data due to length > * 5. DCBR added to relocate sequential buffers above the line > * 6. original lines commented to allow regression checking > * 7. 0405 abend changed to warning message - see NOTEMPTY, > * GAPORDEL, LOSTDATA, and LOSTMSG portions of the code > * > > Michael > > At 08:59 PM 7/22/2025, kekronbekron wrote: > > > Hi Michael, > > > > By any chance, is this something that can be setup like a parallel run? > > Main recording is the default behaviour, 255 long is secondary > > write, so it helps analytics. > > This way, legacy tools won't be upset by the long lines and changing > > message format. > > > > - KB > > > > On Tuesday, July 22nd, 2025 at 22:12, Michael Oujesky > > [email protected] wrote: > > > > > Food for thought: > > > > > > I have mods to SAMPLIB(IEAMDBLG) that expands the record length to > > > 255 and those basically eliminate continuation messages. > > > > > > I also have some SAS code to search the expanded record length > > > log for multiple messages. It also handles MLWTO messages that have > > > records from other SYSPLEX images interspersed within the MLWTO text. > > > > > > Michael > > > > > > At 06:50 AM 7/22/2025, Lennie Bradshaw wrote: > > > > > > > Does anyone have any advice on tools to scan SYSLOG and/or OPERLOG > > > > for multiple messages? > > > > I am looking for something that understands continuation messages, > > > > and the structure of multiline messages. > > > > > > > > Lennie > > > > > > > > ---------------------------------------------------------------------- > > > > 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-MAINHi > > > > ---------------------------------------------------------------------- > > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
