Re: Commitment Control

["Al Barsa, Jr." <barsa2@xxxxxxx>]

At 08:47 AM 7/13/98 -0400, you wrote:
>We are in the midst of doing some conversions to old software.  One of
>the programmer/consultants we brought in is arguing against setting up
>commitment control.  I feel that it is a feature we should be using. 
>
>He feels that there may be too much overhead on the system.  We are
>going to enable journaling on all these files anyway. 
>
>We are on a Model 170 2164.  We just moved from an F10 so we can afford
>some overhead in processing time.
>
>What is the general feeling on this ?  If we are posting a batch of 500
>records should we commit on every record, every 10th record or after the
>entire batch ?

Commitment control provides a method of committing transactions.  You
should commit after every completed transaction.  Uncommitted updates are
automatically rolled back after an abnormal IPL.

Users from other heritages (i.e.:  not IBM) typically think that
programming without commitment control is a heresy.  If you are already
paying the overhead of journaling, then I would encourage to use commitment
control wherever possible.  It does take a different approach in
programming, but it's worth it.

Al

Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.  
400 > 390

Phone:  914-251-9400
Fax:    914-251-9406





Private mail should be sent to barsa@ibm.net
+---
| 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
+---