RE: Journaling question.....

I agree.

It's not that anything is 'missing' from the journal concept - just the
opposite.  It can be overkill

If you want to track specific information, and want to be able to quickly
get to that information, triggers writing to an audit file is very
effective.

If you need:
*       full-blown tracking of every row of every table, 
*       the ability to re-create any transaction, 
*       and the effort (in programming and retrieval time) is not an issue

Then by all means use journals.   

JN



> -----Original Message-----
> From: Rob Berendt [SMTP:rob@dekko.com]
> Sent: Wednesday, March 22, 2000 7:17 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Journaling question.....
> 
> My reply:
> <snip>
> However if you are going to use the journal receiver 
> to 'snoop' then maybe you want a different method of 
> deleting them.
> <endsnip>
> 
> 
> 
> 
> jhall@hillmgt.com on 03/21/2000 06:30:16 PM
> Please respond to MIDRANGE-L@midrange.com@Internet
> To:   MIDRANGE-L@midrange.com@Internet
> cc:    
> Fax to:       
> Subject:      Re: Journaling question.....
> 
> It depends on how much space you have available and your applications
> but I think if you get rid of the journals the next day you are doing
> yourself a great disservice.
> 
> Today for example I had a user insist she did not request certain items
> to be processed.  The computer "screwed up"  etc. etc. etc.  I did a
> dspjrn to an outfile.  Reviewed the outfile and was able to tell her
> every step she took with those certain items over the past week.  After
> she recovered from her temporary bout with amnesia she was very
> apologetic.  But even if it had been the software I could have traced it
> out to which user, which job, which program and at exactly what time the
> problem occurred.  This has proved very useful in tracking down data
> errors in very commonly used files where any of 100 programs could have
> been the culprit.
> 
> We group our files into journals by application.  We allow the system to
> automatically generate a new journal receiver when the current one
> reaches its limit.  
> 
> I'm curious as to what you find missing from the journal that triggers
> would provide in an audit trail ?
> 
> If you use an extern DS and offset it into the record from the journal
> file you have the exact record from the file.  
> 
> John Hall
> Home Sales Co.
> 
> Rob Berendt wrote:
> > 
> > Ah, yes.  Another question.  How to manage journal receivers?
> > Frankly I dig the trigger method better for auditing.  And then
> > using journalling for journalling and commitment control.  In
> > that case I would lock my files at night, then reset the journal
> > receiver.  Save the files and the journal receiver and delete
> > the old journal receiver.  However if you are going to use the
> > journal receiver to 'snoop' then maybe you want a different method
> > of deleting them.
> >
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
> 
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---