John,
 
  I'm not very familiar with the AIF Procedure Exits, but
an old technique that you can use is to "trap" the DBUPDATE
call with your own 'DBUPDATE' routine that would reside in
a SL/XL outside of XL.PUB.SYS.  You can then have your routine
do whatever is needed with the buffers, and then pass that
along to the real "DBUPDATE" intrinsic by calling it in your
routine.  Keep in mind that using it this way, you may have
an update logged into your 'replicate' file that never took
place if a failure occurs in between the write to your file,
and the actual system DBUPDATE call.
 
  If "some" time delay can be tolerated, another way to do
this is to turn on Image logging, and read the updates
from the log files.
 
Regards,
Michael L Gueterman
Easy Does It Technologies
email: [log in to unmask]
http://Editcorp.nwinfo.net
voice: (509) 946-6179
fax:   (509) 946-1170
 
 
----------
From:   [log in to unmask][SMTP:[log in to unmask]]
Sent:   Wednesday, May 08, 1996 9:58 AM
To:     Editcorp
Subject:        AIF:PE Question
 
 
I am investigating the possible use of AIF:Procedure Exits to trap
calls to DBUPDATE on our production data bases in order to capture
"before" and "after" images of data set modifications for (almost)
real-time updating of a Microsoft SQL Server data warehouse which
summarizes the Image data.
 
...<snip>
 
John Schick
Manager/Technical Support
Times Mirror Higher Education Group