×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I seem to recall a few problems when I converted from RPG III to RPG/400 using CVTRPGSRC.
If I recall, *LIKE DEFN did not work the same for numerics. I think it was the RPG III that was wrong defining some numerics as packed when they had been defined like zoned numerics, or maybe it was the other way around, and when RPG/400 correctly defined those variables, it caused parameter mismatches on CALL operations where those misdefined variables had been used as parameters.
Another problem was with error processing. When an error occurred in an RPG III program, I would get an error message in the program where the error occurred. In RPG/400, if an error occurred, it would not display a message and would instead jump back to the most recent program in the call stack that did a call with an error indicator. It made it difficult to find where the error actually occurred or that an error had occurred.
I know I had others but can't recall what they were now.
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
