|
As I said on WDSC Michael - we need to know more about the type of programs (on-line, batch, etc.) before we can give a you a feel for the scope. In terms of data types the biggie is usually that the meaning of COMP is different on the two platforms. It means binary on mainframe and packed on System i. As a result COBOL redefinitions involving such fields can be "interesting. Hardest thing is creating the external file definitions to match the internal defs in the current COBOL code. If you make extensive use of COPY books and the definitions are well done this can be semi-automated. There have been a couple of tools around in the past - don't know if they still exist. Google may turn up something. Hardest part of the conversion? Learning not to waste time looking for "how to do" things that simply don't need to be done on a System i! Jon Paris Partner400 www.Partner400.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.
midrange.com
