×
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.
There was an ancient, ancient S/38 bug that sounds very similar:
Take 2 jobs. One opens the file I/O, the other Input only. Write
records through the I/O program, and you won't see the new records
with the Input access path until you close and re-open the access
path.
For that reason, we got in the habit of always opening files I/O,
whether or not we needed the "O" or not. This, of course, led to the
problem of excessive record locks, because every program had records
"open for update" whether they needed them that way or not.
*sigh*
I was never sure if this problem was put to rest or not-- we were so
in the habit of working around the problem that we never went back to
test for a cure.
--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
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
