On Tue, 8 Jan 2013 14:34:08 -0500, Farley, Peter x23353 wrote: >Quite true. In my case the resync points (after ignoring or stripping header >lines) can be as little as a blank line followed by a single matching record >in the areas of the file where the differences occur, so maybe SuperC isn't >seeing enough lines of resync to work correctly. > >OTOH the GNUWIN32 diff utility on my laptop found all of the differences >without a problem, so it can be done, just not apparently by SuperC. > >Peter > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On >Behalf Of Joel C. Ewing >Sent: Tuesday, January 08, 2013 2:23 PM > >This is a inherent problem with any algorithm which attempts to >flag/detect changes between files and do it with minimum resource >consumption. Your typical algorithm compares two files and when a >difference is detected starts looking through subsequent records in both >files for a "resync" point ... > That's somewhat old technology. If from the ISPF SuperC panel, 3.13, you press HELP, then ENTER, then 17 (Notes and Limitations), then 1 (Technical Overview), you can read a description of what SuperC tries to do.
-- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
