|
Booth Martin wrote:
Then the issue must reside in this one program, not in the data?
No, the problem is that (maybe only if it happens on the very first
CHAIN, in an INZSR), a "not found" result on this particular CHAIN
produces a nonsensical error that had me tearing my hair out.
The problem is that the program was told to look, in its INZSR (the only
place that file for a record that wasn't there. As soon as it was no
longer being told to do that, it worked fine. And so long as the record
is there, it finds the correct one consistently.
--
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.