• Subject: Re: IDDU, S36 & AS/400 SQL & RPG
  • From: "James W. Kilgore" <qappdsn@xxxxxxx>
  • Date: Wed, 10 Dec 1997 05:47:05 +0000
  • CC: midrange-l@xxxxxxxxxxxx
  • Organization: Progressive Data Systems, Inc.

Prince Etrigan wrote:

> So I should create definitions for my S/36 data files, create "blank"
> physical files, make the files "external" in the RPG IV program and use
> OVRDBF in the CL program that calls the RPG program?

You could, but then again there is nothing prohibiting a S/36 program from
processing an externally described file.  It's just program described because of
compiler limitations.  BTW it's no different than program describing an 
file in RPGIV.

The program has to make sure as to not introduce data decimal errors.

During our transition we noticed such nice things like a program described 
file with EXT for key start postion would use an external  logical with more 
than 3
key fields bypassing the BLDINDEX limitations.

We sort of thought of S/36 RPG compiler as the same as the RPGIV compiler with
certain opcodes flagged as unavailable.  Maybe the same way that release
compatability is managed.

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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].