I would have thought SAS is your friend.
RON HAWKINS Director, Ipsicsopt Pty Ltd (ACN: 627 705 971) m+61 400029610| t: +1 4085625415 | f: +1 4087912585 -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jesse 1 Robinson Sent: Thursday, 27 June 2019 07:44 To: [email protected] Subject: Re: [IBM-MAIN] Copying portions of a huge data set As I said earlier, I can 'browse forward' in the corrupted file to identify the beginning of each 'good' segment (syslog) and the beginning of each 'bad' segment (user job). Pointing to some random spot in the file may not tell me much about where I am at the moment. Ironically the bad segments (user output) all seem to end this way: ICE052I 0 END OF DFSORT I see that as just a coincidence of what the user is doing. I wouldn't try to count on that for a general case. It turns out we can prevent this problem in the future by turning off access to a RACF resource in JES2 Exit 6. That should have been done many years ago. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Ward Able, Grant Sent: Wednesday, June 26, 2019 3:49 AM To: [email protected] Subject: (External):Re: Copying portions of a huge data set This may be simplistic, but using REXX & EXECIO, as long as you can identify the errant data easily enough, you should be able to get this done fairly easily. Maybe not as quick as REPRO, but without much hassle. Regards – Grant. In theory, there's no difference between theory and practice. In practice, there is. There is no such thing as the Cloud. It is just somebody else’s computer. If you don't have time to do it right, when will you have the time to do it over? - John Wooden DTCC Internal (Green) -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jesse 1 Robinson Sent: 25 June 2019 23:31 To: [email protected] Subject: Re: Copying portions of a huge data set ATTENTION! This email originated outside of DTCC; exercise caution. 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. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jerry Whitteridge Sent: Tuesday, June 25, 2019 1:56 PM To: [email protected] Subject: (External):Re: Copying portions of a huge data set Can you only identify the bad data by the line numbers or is there a keyword in the log entries that you can include/exclude by ? Jerry Whitteridge Delivery Manager / Mainframe Architect GTS - Safeway Account 602 527 4871 Mobile [email protected] IBM Services IBM Mainframe Discussion List <[email protected]> wrote on 06/25/2019 01:07:12 PM: > From: Jesse 1 Robinson <[email protected]> > To: [email protected] > Date: 06/25/2019 01:08 PM > Subject: [EXTERNAL] Copying portions of a huge data set Sent by: IBM > Mainframe Discussion List <[email protected]> > > We have a file that contains one month's worth of syslog/operlog data. > Unfortunately a user's job output has infiltrated this file at random > points by inappropriate use of MSGCLASS. I want to copy the good data > (log stuff) to another file and leave the errant user stuff behind. It > seems simple, but I can't seem to tweak a utility like REPRO (with > SKIP and COUNT) to do what I want. I've browsed the file and > identified by line number where each good data starts/ends and where > the bad data starts/ends, like this: > > 0000000001 - log > 0000932964 - job > 0000933148 - log > 0001539016 - job > ... > 0022175585 - job > 0022176053 - EOD log > > The output file should contain just the 'log' data. Suggestions? > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office <===== NEW > [email protected]<mailto:[email protected]> > > > ---------------------------------------------------------------------- > 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 DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. ---------------------------------------------------------------------- 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
