S/36 to native transition was: EXTNAME questions...

Scott,

The way we handled the transition/coexistance was:

1) Create a brand new name for the externally defined physical file for native
use.
2) Create a brand new name for the primary unique logical file for native use.
3) Create a logical file named the same as what is used in the S/36ee OCL // 
FILE
LABEL-?????

This meant -no- changes to the OCL during development and all new development 
did
not have to follow and older technology naming convention.

Well, it worked for us anyway.

P.S. If the RPGII file name was ARCUST and the S/36 file label was AR.CUST we
made the brand new externally defined files record name ARCUST.  It's a little
thing, but it did reduce the number of changes when taking a program from RPGII
to RPGIII.

Scott Klement wrote:

> Sort of.  I share the same files between S/36 RPG and ILE RPG
> programs.  Fortunately, its rare that we use dots in our filenames :)
> Most of the Sys/36 stuff doesn't use a dot (tho there are a few
> exceptions)
>
> But, the ability for them to coexist on the same files is crucial...
>

+---
| 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
+---