Re: Problem with an SQL View that has selects/omits

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 is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.