Larry writes:
 
> > then I suppose this is the way to go.  If so, what application do I
> > need to "patch" to capture DBUPDATEs from ODBC?
> I think Stan has a program that can search for these.  Is this correct
> Stan?
 
I'm not sure, but if the ODBC stuff is already in XL.PUB.SYS, then...
probably not.  If the ODBC stuff is in a separate program file, then
yes, it should be intercepted with AIF:PE provided you armed PE for all
processes in the system (a choice you have).
 
NOTE:  No AIF:PE intercept of any IMAGE intrinsic will catch any calls
from CM!!!!
 
This is because CM IMAGE intrinsics switch to NM and call something
*below* the DBUPDATE/DB... intrinsic (e.g., on the order of: nmdbupdate,
which is the real worker for dbupdate.  THis linkage is somewhat
hardwired, and difficult to intercept.  I did some research a year or
two ago, and developed a method of intercepting the common routine that
the CM IMAGE intrinsics call on their way to the "worker" IMAGE
routine, but didn't do robust testing.
 
I started to urge HP to provide a more useful "hook" for intercepting
*all* IAMGE calls a few years ago, but the concept got lost in the
work on jumbo datasets.  With mostly documentation work, it would be
fairly easy to allow all IMAGE calls to be intercepted via AIF:PE
by documenting & "marking" a small set of routines, ala what AIF:PE
did for selected routines within NL.PUB.SYS.
 
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html