> As Gil predicted, ICETOOL won the day with assist from Kolusu. Or else the other way around. Final control statements:
Skip, Glad to hear that proposed ICETOOL solution worked for you. :) >>With 22,807,898 lines in the file, it took a lot of 'inspection' to understand why our log print program was getting S0C7. The intrusive user junk always starts with 'J E S 2 J O B L O G'. OTOH every true syslog record seems to have an alpha character in position 1 that can be found with "f p'@' 1 word". Hence the relevant line numbers can be found easily with alternating ISPF browse commands. But very hard to turn into a simple algorithm. Just so you know DFSORT can identify the junk line and eliminate it programmatically instead of you manually finding the line numbers to be eliminated. If you are interested I can show you way to do it. You mentioned that you can identify the start of junk data. Can you also identify the end of junk data? Please send me an offline message with DCB attributes and I can show you a job to get the desired results Thanks, Kolusu DFSORT Development IBM Corporation ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
