RE: Match program object to source member; CAN'T use source last update timestamp in object

Good point.  I'll tuck that one in my checklist.

The only gotcha is when someone only deletes statements to a member and does
not modify existing lines or add any.

Well, the other gotcha is when someone modifies an existing "live"
statement, but only modifies the comment area of the line.  I've seen that
happen before, too.

- Dan Bale
(I am *NOT* "Dale"
http://archive.midrange.com/midrange-l/200105/msg00281.html )
SAMSA, Inc.
989-790-0507
DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Bernard Burchell
Sent: Friday, April 26, 2002 9:26 AM
To: midrange-l@midrange.com
Subject: Re: Match program object to source member; CAN'T use source
last update timestamp in object

Dan,

You could read the source member and find the highest source change date
SRCDAT.  Compare this to the source date in DSPOBJD *SERVICE.  If the dates
match there is a high likelihood that the source matches the object.  You
won't get the change time but it may be good enough.

Bernard Burchell.