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

We're undergoing some stringent audits ourselves by our parent company.
Those journal queries are perfectly acceptable to them. And if you looked
at them you can tell we're running similar ERP.

I even have some queries to determine if anyone from our systems
department, or anyone with *ALLOBJ, updated any data in our ERP system as
that is verbotten.
SELECT journal_code, journal_entry_type, object, object_type, X.*
FROM TABLE (QSYS2.Display_Journal(
JOURNAL_LIBRARY => '#MXJRN',
JOURNAL_NAME => 'BPCS_ALL',
STARTING_TIMESTAMP => TIMESTAMP('2017-01-01-00.00.01'),
STARTING_RECEIVER_NAME => '*CURCHAIN'
) ) AS X
WHERE CURRENT_USER IN('ROB', 'ROBG', 'DARREN', 'DARRENS')
OR CURRENT_USER IN(SELECT AUTHORIZATION_NAME
FROM QSYS2.USER_INFO
WHERE ACCOUNTING_CODE LIKE('%- 1600%') -- Systems
Department
OR SPECIAL_AUTHORITIES LIKE('%ALLOBJ%'))
;

The only trick was then to prove that we have a year's worth of journal
receivers, either online or otherwise. Since we're using BRMS and it
keeps track of every journal receiver currently on "tape" I have some
extensive queries to prove that we do, without gaps. It's really fun when
I have to prove that we even have them for when we do a HA switch over to
our other machine and run there.

- Live to audit, audit to live!
Have I ever mentioned that my oldest brother is a retired senior systems
analyst from the IRS?


Rob Berendt