×
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.
Years ago, we did a large amount of RPG36=>RPG=>RPGLE conversions. We'd change the member type from RPG36 to RPG, made sure it compiled, and then ran CVTRPGSRC. We had a few cases where the RPG36=>RPG required some code changes (F-specs IIRC), but I don't recall ever having a valid RPG source member that wouldn't convert to RPGLE. If we had multiple left-hand indicators, it was ugly, but it worked.
-----Original Message-----
From: Dan [mailto:dan27649@xxxxxxxxx]
Sent: Friday, October 06, 2017 1:43 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Maintaining old RPG 2 or 3 code on RDi
On Fri, Oct 6, 2017 at 2:29 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
Unless you happen to be using one of the few op-codes that don't
convert, there's little excuse not to convert. And if you do use one
of those non-converting op-codes...you're probably using it wrong
anyway ;)
I was pretty certain that any valid RPG-III code would always convert to compilable RPG-IV code using CVTRPGSRC. But, it's been so long since I've had to deal with that, I'm not sure. I know that /free calcs obsoleted some of the obscure opcodes, but a plain vanilla conversion using CVTRPGSRC should always convert to compilable code.
- Dan
midrange.com
