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

On 10/29/2011 12:52 PM, CRPence wrote:

On 28-Oct-2011 14:51 , Buck wrote:

<<SNIP>> 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.

The journal data of the file being updated would record the Program
Name [JOPGM] information. Built-in auditing of the I\O [STRJRNPF if not
already], instead of writing a [trigger] program get that information.

Yes, absolutely.

I'm not using the trigger for the post-mortem, I'm using the trigger for
replicating from a production system to a parallel system (which has a
new database with similar information stored in 3rd normal form!) The
problem is that the trigger program was throwing errors when it tried to
process a row from the old system that had invalid decimal data. I
wanted to add the program name to the post-mortem error log that the
trigger program is now writing.

An unnatural curiosity coupled with an unhealthy desire to be complete
drove me to wonder about the possibility of Java or PASE updating my
database; particularly whether my employer could possibly purchase a
third party application in Java (or perhaps some PHP-ish software) that
would update the QSYS.LIB file system. I don't think that seems very
likely.

Thank you all for your thoughts,
--buck