RE: system event trigger whenever a source file member is updated

>It would operate asynchronously from the member changes, which is
>also different from triggers. That might be a consideration.

You lost me.  What do you mean by "operate asynchronously"?  FWIW, I have
never done triggers, but I think I have the concept.

- Dan Bale

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of R. Bruce Hoffman, Jr.
Sent: Wednesday, March 13, 2002 10:29 AM
To: midrange-l@midrange.com
Subject: Re: system event trigger whenever a source file member is
updated


----- Original Message -----
From: "Dan Bale" <dbale@samsa.com>
To: <midrange-l@midrange.com>
Sent: Wednesday, March 13, 2002 9:23 AM
Subject: RE: system event trigger whenever a source file member is updated


> Would it be relatively easy to set up an audit journal for every source
file
> on the system?  I looked at a regular file journal, hoping that I could
> limit the entries going into it to open & close, file/member creation and
> deletions, but obviously not.  The file creations & deletions could be
> handled by file auditing the QADBXREF file.  Where do I find out more info
> on object auditing?

Well, you would only set up the one journal. You would execute the change
object audit against each source file only once. And yes, the regular file
journaling would not be what you want. That's record oriented as well. The
audit journal is object oriented (not as in OO though ;-).

The receipt and processing of the journal entries would be the ongoing and
repetative thing. A program to filter the entries and handle the processing.
It would operate asynchronously from the member changes, which is also
different from triggers. That might be a consideration.

As for information, I would think it's in the security reference.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - iSeries Administrator
 -- IBM Certified Specialist - RPG IV Developer