|
From the REDBOOK - Striving for Optimal Journal Performance on DB2Universal Database for iSeries sg246286..
<quote>
In the CL
program that calls the batch program, specify the files that use commitment
control and open them. Start a commit cycle in the CL program before
calling the batch program. In the application program(s), change the file
description to specify that commitment control is in use. Once the program
returns to the CL program, end the commit cycle to force any pending file
I/O to complete.
</quote>
This might not work, if there is concurrent workload working with the same
file!!! The lock contentions of the long lasting recordlocks slows down all
up to doing nothing or breaking down your batchjob. This won't work with
concurrent save activities, I would be very very very carefull to follow
such recomendations!!!
D*B
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.