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



No...I'm pretty sure RPGII had those toward the EOL of the S/36. I remember
the RPGII 1/2 release had those...I think.

On Thu, Mar 4, 2010 at 8:07 AM, Vern Hamberg <vhamberg@xxxxxxxxxxx> wrote:

Well, it's been so long, I probably added those. I actually started out
on a 38 with III.

That just makes II even worse!!

Vern

Terrence Enger wrote:
On Tue, 2010-03-02 at 21:07 -0600, Vern Hamberg wrote:

LOL - any code from RPG II land is probably going to have a slough of
indicators and CABxx and CASxx - the command is not going to change
those - you need the extended functionality of Linoma's tool for that.
It will change a lot of that stuff for you. Maybe even Craig Rutledge's
tool will do some of it, not sure.


Hmm, this is a real memory test for me, but are you sure that RPG II had
the CABxx and CASxx opcodes? I only remember these from RPG III.

CVTRPGSRC, of course, does not claim to work for RPG II.

Cheers,
Terry.



--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



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.