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



A "little simpler" way to handled workstation programs in RPGII is
to fire up S36ee and compile the source as per normal. One of the
side benefits of doing that, is the compiler will also create a
new source member using the program name and place the resulting
DDS source in a file called Qs36ddssrc. You then have the regular
old DDS you are familar with and proceed with the conversion.

Some of the conversion aids work well, but the resulting source code
looks pretty bad with miserable field naming like FLD01,FLD02,etc,etc.

Using the DDS and some minor changes(most of the time), you can convert
a typical RPGII to RPGIII with little trouble. Yes, you can then
run the CVTRPGPRG and produce some ILE "like" code.



Jim Langston wrote:
>
> One way I would do it is to copy the source member to a different object, and 
>change the type to RPG (RPG-III) and then run CVTRPGPRG on it.
>
> Then I would fix the F specs.
>
> This works for the majority of RPG II programs, but doesn't work well for 
>display programs.  RPG II seems to have handled display files quite a bit 
>differently than RPG III or IV.  Sometimes if it was a simple display, it 
>would work.  If it was a subfile, it wouldn't.
>
> Or you can go out and get a tool to convert from RPG II to RPG III, convert 
>to III, then run CVTRPGPRG to convert to IV.
>
> Regards,
>
> Jim Langston


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.