audit source member adds/mods/deletes

["Dan Bale" <dbale@xxxxxxxxxxxxx>]

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