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


  • Subject: Re: RPGS36 Conversions
  • From: "James W. Kilgore" <qappdsn@xxxxxxxxxxxxx>
  • Date: Wed, 23 Feb 2000 09:50:43 -0800
  • Organization: Progressive Data Systems, Inc.

Mike,

When you compile the screen S&D specs it automatically creates the DDS, but it's
ugly and I've never found it worth using.

You can change the RPG member type from RPG36 to RPG and run it through the
conversion to RPGLE, compile and start debugging from there.

The times that I have tried this, I have always found it to be less frustrating
to just start from scratch and do it right.

Probably -not- what you want to hear, just my personal experience.

Mike Silvers wrote:

> Has anybody used the IBM supplied programs to convert System 36 RPG and DSPF
> code to a more current version of RPG?  I have some 'old' RPG36 source that
> I need to convert for the 400.  We are currently running the programs in S36
> mode (ugh!) and would like to change that.  Any suggestions or help will be
> appreciated!!
>
> Mike
> _________________________________

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.