Commitment Control and Journaling Performance on iSeries

Jay Paff

Active Member
Hi All,

Well I'll start by saying a little knowledge is a dangerous thing. Now that I've said it I have immunity from JDE Island.

I just attended the iSeries Performance Tuning class. One of the topics that came up is the performance of your journals with regards to commitment control. Essentially, you want to have commitment control on because then writes become asynchronous. Without commitment control, writes are synchronous and thus slower performance.

The only place I can think of where you can define commitment control is in ODBC adminstration and the commit mode for a DSN via the configure option. Currently, most of ours are set to *none.

What do others do with regards to commitment control?
Is there another place where commitment control can be set?
Which Commit mode option is best, *NONE, *CHG, *CS, *ALL or *RR?
Does having commitment control in place really make a noticeable performance difference?
Am I wasting everyone's time and should my immunity be revoked?

Thank in advance, Jay
 
Back
Top