|
Scott, I to am sharing the S36 files with ILE RPG. I was going to ignore the flame, but since you responded. Here is our approach to re-writing the old S36 applications to new fancy native ILE applications with minimal impact. 1. Create external definitions for the S36 files - using exact record layout. 2. Convert the RPG II source to RPG III, minimal changes needed. 3. Convert the OCL to CLLE re-doing the logic. (The hardest part, IMHO) 4. Convert the RPG III to RPG IV and take advantage of the native file descriptions, Opps, have to rename the file now kus the compiler won't allow the dot in the file name. Now you have a completely native application that you can add all the bells and whistles to. Oh by the way the changes we done with very little impact on the system and very little IS resources used to implement. -----Original Message----- From: Scott Klement [mailto:infosys@klements.com] Sent: Friday, October 29, 1999 10:37 AM To: RPG400-L@midrange.com Subject: Re: EXTNAME questions... 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... Rob Berendt <rob@dekko.com> wrote: > > But do you see people banging out ILE RPG for the S/36 environment? > +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.