MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2013

Re: Journaling without commitment control (WAS iSeries and SSD drives)



fixed

<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





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact