×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Yeah, 32 was the limit, because that was also how many files could be named in 
a JOIN logical. At V5R1 the number of files you can use in a view is still 32, 
at V5R3 that went up to 256. At V4R4 the number of files you could join in a 
statement went up from 32 to 128, at V4R5 the number of files you could join in 
a statement was 256, same for later releases. So the boundaries have been 
moving, kind of leap-frog.

Go to www.iseries.ibm.com/support and put "maximum capacities" in the search 
box - you'll find all this stuff by digging around there.
-------------- Original message -------------- 
From: "Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx> 

> I know limit used to be 32 for the longest time. I thought it was raised to 
> 256 on V5R3, but for the life of me I can't find an IBM link stating that. 
> What OS are you at? 
> 
> Elvis 
> 
> -----Original Message----- 
> Subject: QM CPD4396 Error 
> 
> I've got a HUGE QM that I need to load a file which is encountering a 
> problem. 
> 
> Is there some limit on the number of Unions that can be done? I need to 
> have 39 in all, but when I hit 33, I get CPD4396...SQL System Error. 32 
> Unions works. 
> 
> Any ideas? 
> 
> Thanks, 
> 
> Matt 
> 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
> 

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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