RE: cant save v5r1 rpg pgm to *prv release

-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Buck Calabro

>I can't speak for the compiler team, but I have a similar situation using
>production code in our ERP product.

>Imagine version 7 of the product installed at a customer site.  That
version
>has it's own database file structure, etc.  In the course of development
for
>ver. 8 I create an internal API that is built over information stored in
>database files that were changed from ver. 7.  My ver. 7 customers would
>love to have that functionality, but I can't ship it to them because it
>would require me to change part of their database to ver. 8.

Hi Buck,

But if your product was modular, that is each module is self contained, does
not depend on the other modules ... your v8 database module would provide
interfaces that could be used by a v7 code module.

That is what ILE is touted as being. The p/w-code output by the v5r1 rpg
compiler should be able to be compiled down to the *prv release.

My technical question is, what is the technical reason for the this? Was
w-p-code enhanced in v5r1 to accomodate LIKEDS and QUALIFIED?

And even if the intermediate code was enhanced in v5r1, shouldnt ILE still
accomodate this.  One ILE ILE compliant machine code module calling another
through their established interfaces?

Steve Richter