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
+---