|
Steve, >so we spend most of the processing time converting from flat files to externally described files and back again. When faced with a RPG II to RPG IV conversion where the file layouts did not remain compatible (for example due to true date fields in the new files), I set up bi-directional triggers. The S36EE file trigger would keep the native version in sync in real-time, reformating as necessary, and the native file trigger would do the opposite, propagating changes back to the corresponding S36EE file. This lets either file be used during the transition period and programs replaced and implemented gradually instead of having a mass cut-over weekend. If your file layouts can remain the same, the RPG II programs can access an externally described file just fine (when properly defined as a program described file). Of course, as Bob pointed out that gets more complicated when the program described file used multiple formats. Doug
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.