×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 21-Sep-2015 14:19 -0600, Cornelia F Meyer wrote:
Check the FRCRATIO for the physical. If you want the records to be
written immediately you need to change it to 1 (one) or you can use
OVRDBF to change the value before calling the program.
The Force Ratio is unrelated to the record ordering.
Besides, use of the FRCRATIO(1) should be avoided, generally, and
journaling used instead; actually, should be avoided with any
specification other than the *NONE, with a meaning of "let the system
decide". Such misuse of the FRCRATIO often gives rise to
poorly-performing writes. Often the misuse is a heavy-handed means to
effect what is wanted, but without fully understanding by the programmer
of the true consequences and underlying effect. Whenever contemplating
use of the FRCRATIO for the perceived effects, consider instead the use
of either the Force End Of Data (FEOD) capability or the BLOCK(*NO)
file-declaration specification; those features are likely to enable the
desired effect, without the consequences\effects of what the
small-values specification for Force Ratio actually implements\intends.
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.
midrange.com
