Re: Information available when a db2 trigger fires off/calls an rpg program.

"If" you have your journal configured right, and include program, and
program library data, like this:
CHGJRN JRN(#MXJRN/BPCS_ALL) JRNRCV(*GEN)
RCVSIZOPT(*RMVINTENT *MAXOPT3)
FIXLENDTA(*JOB *USR *PGM *PGMLIB)

Then it becomes extremely easy to find out who modified the data outside
of BPCS.

SELECT journal_code, journal_entry_type, object,
x.current_user, job_name, job_user, job_number,
program_name, program_library,
remote_port, remote_address, system_name,
X.*
FROM TABLE (QSYS2.Display_Journal(
OBJECT_NAME => '*ALLFILE',
OBJECT_MEMBER => '*ALL',
OBJECT_LIBRARY => 'ERPLXF',
OBJECT_OBJTYPE => '*FILE',
JOURNAL_LIBRARY => '#MXJRN',
JOURNAL_NAME => 'BPCS_ALL',
STARTING_TIMESTAMP => TIMESTAMP(current date - 1 days),
STARTING_RECEIVER_NAME => '*CURCHAIN'
) ) AS X
Where program_library not in('ERPLXUSRO', 'ERPLXEC', 'ERPLXPTFO',
'ERPLXO');


Helping you out let me know that we have three of these but not *PGMLIB. I
may consider adding that.

Disclaimer: One might consult with their HA vendor prior to making any
journal changes. Adding additional data to your journals may affect
bandwidth to remote journals (if your HA vendor does that sort of thing).




Rob Berendt