|
At 03:57 PM 5/5/98 -0700, you wrote: >A company is upgrading from Advanced/36 to AS/400. They have files with >multiple record types and want to reuse as much code as possible (with >the necessary changes for the AS/400). Right now the plan is to use >external data structures to define the fields (for the new code) and >create logicals to define the fields for use with Query. However, some >of the fields are packed. What have others done in the past to handle a >similar situation? Any and all suggestions would be greatly appreciated! >Direct replies are OK to dkbrengle@juno.com. There are two good alternatives. First of all, do nothing and run in the *M36 mode. It ain't fancy, but it works, without recompilation. I have also used a package called TARGET/400, which takes S/36 code and makes it native. It handles multiple record formats well, although this can be a lot of work. If you want more info about this package, please call. Al Al Barsa, Jr. - Account for Midrange-L Barsa Consulting, LLC. 400 > 390 Phone: 914-251-9400 Fax: 914-251-9406 Private mail should be sent to barsa@ibm.net +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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-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.