Re: QWVRCSTK - CSTK0200 for 'what program fired the trigger'

On 10/28/2011 1:17 PM, CRPence wrote:

On 28-Oct-2011 08:59 , Buck wrote:

I'm implementing QWVRCSTK in a trigger program for the usual reason:
to find the name of the program that performed the database update
that caused the trigger to run.

And my usual response... If a trigger needs to know the answer to the
question of effectively "Who called?", then there might be a design
issue that needs to be resolved. An answer to that question should not
need to be asked generally; best if only asked in some rare
security\auditing scenarios.

Concur. There is no business rule, it's a post-mortem. My trigger is
sort of replicating data from an old application to our rewrite during
our parallel testing period. The old code is dropping decimal data
errors in the old file and rather than stop and look at every one of the
potential culprits, I thought it'd be easier to put the name of program
that did the update in the post-mortem error log.

What does the stack look like when an I\O is requested from a JAVA
stored procedure? A JAVA toolbox I\O even without an SQL procedure?

create procedure ...
language JAVA parameter style JAVA
external name ...

Just as any native code can access a database file member via IFS
naming, so too can a PASE process.? Something as simple as redirection
could open and write.?

The stack I posted was a Java app running in QShell, using the JT400
API. Late in the day here; I'll look on Monday. Am at V5R4 and will be
for at least a year. Don't know if I can even create a Java SP but that
sounds like a promising place to start. Thanks for the advice. You're
a treasure!
--buck