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



In a nutshell. Nicely put, Charles.

Brian.

On 16/07/2020 22:31, Charles Wilt wrote:
Here's my 0.02...

I break down RPG coding into the following
RPG III
RPG III+ (RPG III run through CVTRPGSRC)
RPGIV (some free form/new op-codes & BIFs)
ILE RPG (service program & procedures)

Continuing to use the RPG III compiler when making modifications to an
existing program, instead of running the source through CVTRPGSRC is just
stupid. Both on the part of management for insisting on it, and on the
developer(s) willing to go along with it.

Heck, when I had RPG III code around in the past, I'd usually run it
through CVTRPGSRC just to look at it. Simply so I could take advantage of
the outline view in RDi.

Perhaps there's an exception for third party code...but even there, I can't
believe a vendor would still be shipping updates written in RPG III. And
if you're not getting updates, then the code is yours now, regardless of
where it came from.

CVTRPGSRC is about the safest thing you can do on the IBM i, there's only
two op-codes that don't convert FREE and DEBUG. And those aren't often
used.

As long as you compile with DFTACTGRP(*YES) the behavior between RPG III
*PGM and the converted RPGLE *PGM is exactly the same.

Charles


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.