Re: audit source member adds/mods/deletes

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Not if it does not exist yet.    ;-)

Vern

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

> Can you add a PF Trigger to a source physical file?
>
> Thanks,
>
> Mark
>
> Mark D. Walter
> Senior Programmer/Analyst
> CCX, Inc.
> mwalter@xxxxxxxxxx
> http://www.ccxinc.com
>
>
>
>
>                       "Dan 
> Bale" 
>
>                       <dbale@xxxxxxxxxxxxx        To: 
> <midrange-l@xxxxxxxxxxxx>
>                       >                           cc: 
>
>                       Sent by:                    Subject:  audit source 
> member adds/mods/deletes
>                       midrange-l-bounces@m 
>
>                       idrange.com 
>
>
>
>
>
>                       06/28/2004 09:00 
> AM 
>
>                       Please respond 
> to 
>
>                       Midrange 
> Systems 
>
>                       Technical 
> Discussion 
>
>
>
>
>
>
>
>
>
> 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 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.