×
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.
Interesting.
The ILE RPG code equivalent to the point of failure,
FHPADLPUA IF F 1243 DISK
D RECORD DS 1243
C 1 SETLL HPADLPUA 121314
C READ HPADLPUA RECORD
exhibits exactly the same behavior as the failing MI program.
What's even more interesting is that without the indicators on the
SETLL, the version using the DDS LF crashes at that statement!
Hmm.
*IN13 is the one that gets set on, so it's an error condition.
Hmm.
I just tried inserting a SETGT into both versions of the test RPG,
conditioned on *IN13. They also returned with error conditions, on both
the DDS LF and the SQL VIEW, and once again, the READ on the DDS LF
worked, but the one on the SQL VIEW didn't.
So it seems that on a DDS file, we're protected from being left at an
undefined position, but not with an SQL file.
Could this have something to do with the whole business of DDS files
checking data validity on READ, but SQL files checking them on WRITE?
--
JHHL
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
