×
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.
We have a file that was designed to restrict order entry access so that only one person can be entering/updating an order at a time. Works great, except from day-one (decades ago) the file has had the default WAITRCD value of 60 seconds. This means that any interactive session that encounters the locked order stalls out for 60 seconds before it gives control back to the user, along with a helpful message that indicates the record is in use by another job.
I could use an OVRDBF to change this on a per-program basis, but...
I'm proposing we use a CHGPF to set that file's WAITRCD time to 2 or 3 seconds, so the user can get on with their life, and I don't have to go looking for other places that need the OVRDBF treatment.
I was asked to inquire about possible adverse impacts that others may have encountered in using this more global approach to do this.
Note that I'm not proposing (yet) that we change the default value across the system -- just this one file.
Thanks for your thoughts.
-- Michael
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.
midrange.com
