Re: audit source member adds/mods/deletes -- MIDRANGE-L

Dan

You can have new object creates audited, as well. You could them wait on the journal and check for object attributes, etc., to decide whether it was a source physical file that was created.

HTH
Vern

At 08:00 AM 6/28/2004, you wrote:

Good Monday morning!

There's gotta be a way...

I want to be able to automagically track the user ID that changes any given
source member.

Because we are moving towards using the WDSC source editor, it can't be
something that only hooks to SEU.

I know a little about object auditing, but the problem there is that the
source physical file must already be known (defined for audit) before member
adds/mods/deletes can be audited.  Am I wrong about that?  Case in point:  I
create a new source physical file, or restore one from backup, and I need it
to be immediately audited.

Thinking "out loud": Could I stick a journal on QADBXREF and a never-ending
batch job that RCVJRNE from that to catch new files to audit?

Is there a more "elegant" solution?

TIA, db
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.