RE: audit source member adds/mods/deletes

[CWilt@xxxxxxxxxxxx]

Dan,

Sounds to me like you (and your auditors) would be better served by having a
Change Management System in place.

Seems like you're thinking of spending a significant amount of CPU and DASD
resources tracking this information live.  When I would imagine all you
really want to be able to do is answer the question who changed what when.
With logging, automatic archive, and built in ways to compare versions of
source, most if not CMS software will easily answer those questions.  

Aldon and Turnover come to mind.

Charles


> -----Original Message-----
> From: Dan Bale [mailto:dbale@xxxxxxxxxxxxx]
> Sent: Monday, June 28, 2004 9:01 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: audit source member adds/mods/deletes
> 
> 
> 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.
>