RE: cant save v5r1 rpg pgm to *prv release

>And saving to a previous release should just
>work at the common p/w/whatever code level, no?

Hi Steve!

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.

If there's enough demand from the ver. 7 folks, I might re-write the API to
work over other, less efficient ver. 7 files.  Then I could ship the new
ver. 8 functionality to them, but at the cost of penalising the ver. 8
performance.  So I make two versions of the API: one targeted to ver. 7 and
one to ver. 8.  I have an internal 'switch' that says which is to be used
when we build the CD for delivery.

I believe this is roughly equivalent to TGTRLS on the CRTBNDRPG command.  It
tells the compiler to 'link' to the current internal APIs or to the previous
set.
  --buck, speculating away...