Re: Commitment Control -- MIDRANGE-L

See archive article http://archive.midrange.com/midrange-l/200305/msg00024.html for more on the topic of journaling performance. Turns out that just turning on commitment control will speed things up. Journaling by itself can be slow.

Vern

At 05:56 AM 5/7/2005, you wrote:

Journaling was introduced in CPF Release R04M01.  Commitment control was
introduced in CPF R05M00.  For low volume transactions journaling has no
performance problems.  As volume got higher, a User ASP helped.  Now with
the newer IOA's, (2757/2780), generally User ASP's become unnecessary.

Commitment control is another animal.  Updates records remained locked
under commitment control until a COMMIT or a ROLLBACK (these are the terms
in CL, shorter terms exist in RPG where these are more frequently used) is
issued.  These performance problems, due to locking, can be major, and are
completely controllable with coding style.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

"i" comes before "p", "x" and "z"
e gads

Our system's had more names than Elizabeth Taylor!

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com
http://www.as400connection.com


             Rob Dixon
             <rob.dixon@erros.
             co.uk>                                                     To
             Sent by:                  Midrange Systems Technical
             midrange-l-bounce         Discussion
             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>
                                                                        cc

             05/07/2005 04:33                                      Subject
             AM                        Re: Commitment Control


             Please respond to
             Midrange Systems
                 Technical
                Discussion
             <midrange-l@midra
                 nge.com>


James

I have journalled all my files since the facility first became available
in the early days of the System/38 and used commitment control when that
became available (a little later?).  I have always used commitment
control to ensure that there are no duplicate ID's in a file.  There was
little choice of method 20 or so years ago and, as it has worked without
problem, I haven't "fixed" it.

As for performance, I have never had any problem and I always thought
that the performance problems associated with journalling were a myth.
If DASD is an issue, you can archive the journal receivers.

Rob Dixon
www.erros.co.uk
www.boarstall.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.