iSeries DB2/UDB V5R2 - troubleshooting system triggers

[Dave Sisk]

Hi Folks:

I've got this scenario:

User table/file....external triggers declared for *AFTER *INSERT, *AFTER
*UPDATE, and *BEFORE *DELETE. The 3 external triggers call a SQLRPG ILE
stub program which catches the trigger buffer and drops it into a data
structure, then the SQLRPG ILE program calls a SQL stored proc with the
right parameter list. The SQL stored proc actually does the work, which
includes inserting or updating rows in a change queue table.

The problem I'm having is that there may be 50 rows in the change queue, but
if I query the table the triggers are attached to I find that maybe 100 rows
have an updated date column (they should be 1:1...each updated row in the
user table should have one corresponding row in the change queue
table...there are almost no deletes). Apparently, the triggers are
encountering errors in some cases when they fire. Since the application
software does not run under commitment control, the application operation
completes OK, but the trigger operation does not. Or this is my best guess
anyway.

So, here's the question: where would I look to find errors from triggers
regardless of what called them on an iSeries platform? Is there one
location or CL command that I can use to scan all interactive and batch job
logs for trigger errors?

Any suggestions greatly appreciated!

Dave