×
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.
I'm having a weird (and embarrassing, since it's happening on a customer
box where it worked just fine in a test environment) problem in which I'm
attempting to chain to a record that should be there, yet somehow isn't.
I've got debugging code in the program, that logs the record ID and the
time in which access was attempted, if the RPG CHAIN statement fails. And
the program that writes the record I'm trying to read puts several
timestamps in the record itself. In every case in which I've been able to
find the record myself, the timestamps on the record have been either the
same second as the CHAIN, or a second or two earlier.
I'm thinking about double-checking that I really AM attempting to chain to
the record, but assuming I am, can anybody think of a reason why this
would happen, and yet wouldn't throw exceptions (as I might expect with a
lock collision)?
--
JHHL
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
