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



I agree that you should only touch What you need to touch When you need to touch it. Unless there is an overwhelming reason.

So the biggest thing that I endorse - whether RDi or SEU - is not converting your objects from OPM to ILE all at once,
but what I do encourage as a big up-front change is to make sure you have taken advantage of the longer source-file formats.
Be sure that the going into the future that you have your source files defined as 112 total in CRTSRCPF cmd.

Due to some corporate policies about change management, moving source all at once is discouraged as new source dates are generated. (Member dates change even though dates on individual source lines do not change. So you have the situation of both QRPGSRC (80 usable=92 total) and QRPGLESRC (100 usable=112 total) residing side by side, which fosters confusion for years when searching for members.

But I think the wider format is almost worth the aggravation.

- John Voris



If you're dealing with RPG, I'd start with the CVTRPGSRC command.

I do not convert all of my OPM to ILE. I do convert each individual program that I need to maintain.
I have a user action (which is very like a PDM action) that converts the syntax for me.
Right click a member > User Actions > Work with User Actions...
CVTRPGSRC FROMFILE(&L/&F) FROMMBR(&N) TOFILE(&l/QRPGLESRC) LOGFILE(*NONE)

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.