× 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.


  • Subject: RE: RPG and SQL Compilers
  • From: bmorris@xxxxxxxxxx
  • Date: Wed, 10 Jan 2001 09:29:44 -0500
  • Importance: Normal


>Date: Tue, 9 Jan 2001 17:22:19 -0600
>From: "Richard Jackson" <richardjackson@richardjackson.net>
>
>Ahhh, Jon.  When the problem is encountered with RPG3, it is caused by the
>number of ODT entries - the number of database, screen, etc fields in the
>program.  Those RPG3 JDE programs that blow the compiler have more fields
>than will fit into the ODT - seems to me like the limit is 32k fields.
But
>this is a creature of the program template and I think that there are two
>sizes.  Are you saying that switching from IRP to W-code avoids the
problem
>or that using a program template that supports more than 32k fields avoids
>the problem?  I think that RPG4 uses the larger template version.

Richard, using w-code brings a whole new set of limits (usually much
harder to reach).  w-code is a completely different architecture from
MI.  If you do a DSPMOD, you can see some of the limits.  I imagine
the "Dictionary mapping table" is sort of equivalent to the ODT,

Barbara Morris


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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.