× 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.



Vern and Joe:

Thanks for the kind words. ;-)

Jerry:

> Jerry Adams wrote:
Works fine if the OPM ("heritage") compiler you're talking about is RPG/400 (III). I had about a dozen RPG/400 programs left over from a contractor that preceded me here; took about five minutes to convert (moving to /free was a bit harder because of the MOVE's). Not so straightforward with RPG36 (II).
Point duly noted. Customers with really old legacy code (e.g. RPGII) should probably invest in a tool to convert those programs to "native" RPG/400 or RPG IV, or manually rewrite them, or just pony up the extra $$$ to IBM to continue to license the OPM compilers.
Also, there are some important differences between the way that CL and CLLE function. These have been discussed before so I'm sure one could find them in the archives. I know that the OVRDBF command bit me a time or two, but that was because of my lack of understanding at the time of activation groups.
I did not suggest that a customer would need to convert all CLP *PGMs to CLLE right away. IBM has never charged extra for the CL compilers (CRTCLPGM, CRTBNDCL and CRTCLMOD commands). Since "CL" is the command language of i5/OS and OS/400, the CL compilers were included with the "base" OS license, and so I expect this would not change. Note also that CRTBNDCL has a default of ACTGRP(*DFTACTGRP), aka. "OPM compatibility mode."


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.