RE: Who envoked that trigger program?

["David Morris" <David.Morris@xxxxxxxxxxxxx>]

Phil,

On our system we wrap file updates in a database access program. The
same database access program wraps triggers so you have access to static
information on both sides of the update. When access goes around the
database access program and comes directly through the trigger, it can
be detected and the expensive test to see what is updating the record is
performed.

Missed the user thread, so maybe this was covered. Because the psds has
both users if you swap profiles in the file server exit you can get to
the real user.

David Morris


>>> sublime78ska@yahoo.com 12/20/01 18:21 PM >>>
...The rpg trigger pgm calls this CL only once.  But, the two api's are
called
many times which slows things down considerably.  In my environment it's
not
perceptible by the user but if I were writing millions of records this
would
suck.

Last week there was a thread on USER vs CURRENT USER.  If you want to
know
who updated a file via Ops Nav ISQL (for example), you can't use the
PSDS
because it will contain QUSER....