Re: Commitment Control & Journalling

[Rich Duzenbury <rduz@xxxxxxxxxxxxxxxxxxx>]

>Do I need to start journalling for a physical file If a program that uses 
>the file is coded for commitment control?

Yes.  The journal is the mechanism that allows commitment control to keep a 
list of the changes that occurred in your transaction.

>
>Do I need to use commitment control within a program for a physical file 
>that has been started for journalling?

No.  Journaling merely keeps a record of what happened to the file.  It has 
other uses besides commitment control, for instance, you can use it to 
speed up daily backups by only saving the changes made to your files, 
rather than the complete files.

>
>What are the consequences when a program that does commitment control on a 
>physical file is executed and the physical file journalling was ended 
>prior to running the program?

It errors out as I recall.  You may be able to code around this, but I 
haven't had any reason to try.

>
>What are the storage issues with journalling?

Journal receivers take space, but you can certainly manage it.  We change 
the receivers daily, or you can have the system change them when they reach 
a certain size.  Once backed up, they can be deleted from the system.

>
>When using interactive SQL, do you need to start journal for the file used 
>to start commitment control?

If you want to use commitment control, the file must have active 
journaling.  I believe you have to be able to exclusively lock the file to 
stop journaling, and perhaps to start it.  It is not something that one 
normally turns on and off at will.

>
>Thanks,
>
>Dare

Regards,
Rich

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---