Dear Massimo and Kolusu, Thank you for your help. I got the results I wanted. The results are as follows. MSGID NUMREC $HASP000 20 $HASP001 10 .............. ---->DISTINCT COUNT: 530
I also appreciate Kevin McKenzie's reply. The reason why I counted how many times each unique msgid appeared in a day is to compare today's operlog with yesterday's operlog and see which msgids are new and which ones increased more than yesterday, such as by 30%. I got a list of msgids that need special attention. I used this list to extract the specific content of today's OPERLOG to find out the possible risks of the system in time. I have two questions: 1.The first question is whether there is a better way or tool to analyze operlog. 2. The second question is whether sort can delete the numbers marked by line breaks in the multi-line records of MSGID to facilitate deduplication of multiple lines. See the information below: •M.... 00000090 HZS0002E CHECK 423 •E... 423 00000090 IXCH0602E The sysplex couple data set has insufficient The second line 423 indicates a line break of the first line 423.. I want to delete 423 of the first line. REXX processing is very easy but too slow because my operlog for one day is very large. Can sort or other tools handle it? Any suggestions is greatly appreciated Jason Cai ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
