RE: RPG and SQL Compilers

[D.BALE@xxxxxxxxxxxxx]

If we're talking S/36 hardware, the RPG compiler maxxed out at a 64K program
object size limit.  While there might have been a limit to the number of
source records that the compiler could read, I never ran into that.

Simple test for anyone still shackled with a S/36:
     E                    BIG      9999 80
     C                     MOVE *BLANKS   BIG,1
     C                     SETON                     LR

If it compiles on a S/36, I'll eat my shirt.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
It isn't an output size limit, it is a restriction on the number of records
the compiler will read from the source member.

Buck

> -----Original Message-----
> From: D.BALE@handleman.com
> Sent: Tuesday, January 09, 2001 4:21 PM
> To:   RPG400-L@midrange.com
> Subject:      RE: RPG and SQL Compilers
>
> Well, I speak from painful experience that S/36 RPG-II programs definitely
> had
> a 64K program object size limit.  Didn't matter what size S/36 you had.
> Though syntax errors bombed the compile within a few/several minutes, it
> took
> an hour for the compile to tell you that you had exceeded the 64K limit.
> Man,
> I don't miss those days!
>
> Dan
>
> -------------------------- Original Message --------------------------
> This would happen on very small .. AS400's.  I have never seen this
> happen,
> since the AS400 basically works with vertual memory, in the form of
> overlays... as RPG II and III did in the AS400 and prior systems from
> previous generations..
>
> Gene
+---
| 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
+---