Kolusu, this leads to some intriguing things, and there are a lot of
possibilities here.
I would like to ask one extension to this, if you please. I would like
to be able to further screen the syslog by Jobname, but knowing that
there could be multiple job numbers, I would need a way to capture
those, too.
So in using this example, I would want to see HASM* messages, but only
if they were in any job ABCDE123. If so, it would be great to see all
the ABCDE123 messages, but I suspect that this is now a two-step job of
some kind.
What do you think? Is something like this remotely possible here?
Billy
Sri h Kolusu wrote on 12/20/2021 11:22:
If we put them together, the output isn't what we need.
Jason,
It is quite easy to get the multi-line messages. Looks like you are
interested in extracting messages which begins with HSAM...
Basically a multi-line message will NOT have the date and time for the
continuation lines. And the message id are at fixed position on the first
line (position 58)
Assuming your syslog is FBM and LRECL=133 here is a job that would extract
the HSAM.. messages (single and multi-line)
//STEP0100 EXEC PGM=SORT
//SYSOUT DD SYSOUT=*
//SORTIN DD DISP=SHR,DSN=Your Input Syslog/Operlog
//SORTOUT DD SYSOUT=*
//SYSIN DD *
OPTION COPY
INREC IFTHEN=(WHEN=GROUP,
BEGIN=(21,5,CH,GT,C' '), $ IF DATE IS > ' '
PUSH=(134:58,08)) $ MESSAGE ID
OUTFIL BUILD=(01,133), $ ORIGINAL LRECL
INCLUDE=(134,4,CH,EQ,C'HSAM') $ ONLY HSAM MESSAGES
/*
Thanks,
Kolusu
DFSORT Development
IBM Corporation
----------------------------------------------------------------------
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
