• Subject: Re: DB2/400 limit: 32 tables in one SELECT
  • From: Dave Shaw <dshaw1@xxxxxxxxxxx>
  • Date: Tue, 26 May 1998 14:48:34 -0400

-----Original Message-----
From: Mark Lazarus <mlazarus@ttec.com>


>Rudolf,
>
>At 01:47 PM 5/22/98 +0200, you wrote:
>>Hi MidRangers!
>>
>>One of our programmers fell over a restriction of DB2/400:
>>SQL0129 = Not more than 32 tables allowed in a SELECT...
>
> I don't know if this will work, but you can try creating a *LF that links
>32 files, then another, etc.  So if this technique works, you can
>effectively access 1,024 files (32 * 32).

It doesn't work, the limit correctly stated is 32 physical file members open
in a single join.  Join logicals can simplify the SQL statement, but they
can't circumvent this limit.  Someone here said the limit has been present
since the introduction of QDBQUERY in CPF Release 7, but it's actually been
a limit on logicals since Project PACIFIC days (S/38 development project -
"Performance Ain't Critical If Function Is Complete").

(BTW, I'm not _really_ old enough to know this first hand, I got it at
COMMON from someone who is.  Honest.  Lessee, that was the COMMON in the
fall of 19** - oops, darn line noise... :)

Dave Shaw, General Nutrition, Greenville, SC (just down the road from BMW -
Bubba Makes Wheels :)
The opinions expressed may not be my employer's unless I'm sufficiently
persuasive...


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].