RE: audit source member adds/mods/deletes

db:

Can you elaborate? E.g., is auditing your primary interest? or are you more 
interested in avoiding multiple developers stepping on each others' work? or 
some other concern entirely?

If audit is a requirement, I have to recommend OS/400 auditing, perhaps at the 
developer (user) level. Also auditing for *SAVRST can give you notice when new 
source files/members are restored.

I definitely don't recommend trying a trigger program. If you want to see the 
result, just create a source file, put some trivial member with half a dozen 
lines in it, add perhaps a delete trigger and then update one of the lines with 
SEU and save the member. The trigger program can be a trivial CL that simply 
does a SNDMSG to you when fired.

Note that SEU _deletes every source line_ and rewrites the entire member. I 
imagine every editor does the same.

I also would be very wary of anything like a journal on a system file such as 
QADBXREF. AFAIK, these files should _not_ be interfered with. I'm not even 
interested in trying to attach a journal to see if it would even work. 
Ultimately, these files are for OS/400's and DB2's use, not ours. (...although 
I suppose "ultimately" gets back around to being for our use, but...) As long 
as I can avoid it, I don't even query these files; I will use the views 
supplied for queries instead.

In any case, it comes down to your objectives. Perhaps switching to WDSC and 
the support for teams is all you need. Or perhaps a strong audit is indeed 
needed. Perhaps a CMS is called for. I'm not clear on it yet.

Tom Liotta

midrange-l-request@xxxxxxxxxxxx wrote:

>   6. audit source member adds/mods/deletes (Dan Bale)
>
>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?

-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertech.com


__________________________________________________________________
Switch to the New Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need. 

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp