Hello Matt...
The iSeries admin has our production library files going to the same
journal. I do not believe he is engaging in any journal processing after
the fact but I cannot be sure at the moment. I will forward this to the
other developer who is covering that side of the analysis. If there is
nothing preventing it, then a separate journal may be a good option to
implement to cover the auditing needs.
Have a good day.
Blake Moorcroft
Developer - Corporate
Russell A. Farrow Limited
1980 Ambassador Drive, PO Box 333, Windsor, Ontario N9C 3R4
Bus: 519-966-3003 ext. 566, Fax: 519-966-9870
blake.moorcroft@xxxxxxxxxx
Blake,
Are you doing some sort of journal processing that requires it to go to the
same journal as the other files? If not, it would be pretty easy to create
a new journal for the file.
Matt
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Blake.Moorcroft@xxxxxxxxxx
Sent: Thursday, November 13, 2008 9:36 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Identifying who deleted records - trigger programs
The use of the journals for data retrieval is being investigated by another
developer. However, there are considerations about how long the data in
the journals is available due to the volume of data being processed. The
auditors are looking for control over one file and governmental regs
require stored data to be *immediately* available for a period of no less
than 7 years (and displeasing a government auditor who can yank your
operating license immediately is not conducive to business operations).
The journals that would encompass this file also contain record changes on
close to 90 other files. While it would be a preferred option, it may not
be a viable option.
So, to cover the bases, I'm assigned to check the option of triggers, which
leads back to the original question of user and program identification from
inside a trigger event.
Have a good day.
Blake Moorcroft
Developer - Corporate
Russell A. Farrow Limited
1980 Ambassador Drive, PO Box 333, Windsor, Ontario N9C 3R4
Bus: 519-966-3003 ext. 566, Fax: 519-966-9870
blake.moorcroft@xxxxxxxxxx
Jerry Adams
<Jerry@bwwholesal
e.com> To
Sent by: RPG programming on the AS400 /
rpg400-l-bounces@ iSeries <rpg400-l@xxxxxxxxxxxx>
midrange.com cc
Subject
11/13/2008 08:49 RE: Identifying who deleted records
AM - trigger programs
Please respond to
RPG programming
on the AS400 /
iSeries
<rpg400-l@midrang
e.com>
Why not just do journaling?
Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Blake.Moorcroft@xxxxxxxxxx
Sent: Thursday, November 13, 2008 7:44 AM
To: RPG programming on the AS400 / iSeries
Subject: Identifying who deleted records - trigger programs
Hello all...
I'm wondering if anyone has ever run into this situation before. Any help
would be appreciated.
A request has been made to track record activity on a file. Specifically,
auditors are looking to see who is deleting or updating records and what
changes are being made.
The option to use a file trigger has come up and would provide the option
to evaluate changes for updated records. The issue that is being
encountered is identifying what program or procedure caused the trigger to
kick off, and more importantly, what user profile was associated to the
program or procedure.
Have a good day.
Blake Moorcroft
Developer - Corporate
Russell A. Farrow Limited
1980 Ambassador Drive, PO Box 333, Windsor, Ontario N9C 3R4
Bus: 519-966-3003 ext. 566, Fax: 519-966-9870
blake.moorcroft@xxxxxxxxxx
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.