×
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.
When working with our Online System Screens(Green Screen), a CL at the
front does OVRDBF FILE(XXX) SHARE(*YES) then OPNDBF FILE(XXX) OPTION(*ALL
). This is used for speed so all the programs screen to screen don't have
to reopen the files.
When an outside user uses our Web Interface to rate, they go through the
same programs that the Online System Screens uses to rate, but there is no
OVRDBF or OPNDBF done like the online system. This caused rating on the
Online System to rate fine, but when testing through Web rating got a
record lock between two programs in the same job since no sharing done and
each program had its own Position on the File. We fixed the issue.
My question now is why not have the Web do the same as the Online system,
since same programs? Besides trying to be consistent (Web vs Online), If a
request from the Web comes through and we run through multiple programs
that are opening same files multiple times is using OVRDBF or OPNDBF speed
benefit worth it? Or are we talking a very insignificant benefit?
Just curious if anyone has experienced this or has any thoughts on the
matter?
Thanks,
Jeff
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.