Re: Compare Physical File Member (CMPPFM)

Also -
Remember that file compare utilities are _not_ infallible...

CMPPFM has to try to figure out what lines to compare in order to determine
what changed.  Sometimes, if you have made extensive modifications to a
source member, it will flag lines as changed that really haven't changed.  I
have experienced this problem on more than one occasion.

Steve

----- Original Message -----
From: "Joe Pluta" <joepluta@PlutaBrothers.com>
To: "Midrange Systems Technical Discussion" <midrange-l@midrange.com>
Sent: Friday, January 24, 2003 11:14 AM
Subject: RE: Compare Physical File Member (CMPPFM)


> > From: Lim Hock-Chai
> >
> > Thanks Steve and here is the original message.
> >
> > Hi! everybody.
> >
> > does anybody know of a way to get rid of the following not match
> > find by CMPPFM with *LINE compare type?  The line below is
> > obviously match between the compare from and to source member.
> >
> > I -     D #NewDate        C                   CONST('NEWDATE   ')
> > D -     D #NewDate        C                   CONST('NEWDATE   ')
>
> Check for unprintable characters.  Sometimes people stick hex values in
the
> first five positions of the record to change the color of the line.
>
> You should probably dump the records from each source member in hex and
> compare them.
>
> Joe
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>