RE: SQL vs V5R1 and service woes

Oh well, I tried.  At this point, you'll just have to keep your fingers
crossed that IBM figures out how to correctly combine the concepts of SQL
and library lists.  This has always been a bit of a problem.  "Standard" SQL
has no concept of a library list - that's purely an IBM midrange database
concept.  More than one OS/400 SQL implementation has been plagued by
library list issues.

Joe


> -----Original Message-----
> From: midrange-l-admin@midrange.com
> [mailto:midrange-l-admin@midrange.com]On Behalf Of rob@dekko.com
> Sent: Tuesday, September 11, 2001 5:21 PM
> To: midrange-l@midrange.com
> Subject: RE: SQL vs V5R1 and service woes
>
>
>
> No, the data was not going to the wrong files.  But I was think that was
> only because no records matched.  For instance, it fills each divisional
> PLLINE first, then each divisions PLLINE2.  It filled the PLLINE
> correctly.
> But when it tried to fill the PLLINE2 the records didn't match because it
> was using the wrong divisions PLLINE.  Maybe it was doing
> something complex
> because of the subselect or the concat's and that is when against
> the wrong
> path.  If it was a logical file issue then we would have to have a join
> logical in each divisional file that joined their PLLINE file back to the
> VDLINE file back in the central library.  And cross library logicals are
> everyone's idea of a good time, right?