× 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 guess inarticulate should be my middle name! Yes, I can do a straight conversion and use the compile time data reference at the bottom of the program (CTDATA & PERRCD() ALT()). What I wanted to do was move that data from the '**' position up into the 'D' spec.s. I have been able to clean up the compile time arrays but I can't see how to set up the data for TAB01/TAB02 in 'D' spec.s.
D.J.
message: 1
date: Mon, 27 Aug 2007 09:15:02 -0700
from: "Peter Dow (ML)" <maillist@xxxxxxxxxxxxxxx>
subject: Re: TAB01/TAB02 to "D" spec.s

Hi Dick,

I see Randy has already answered this specific question, so I'll just
note that you can find this out by using IBM's CVTRPGSRC command, which
converts RPG III to RPG IV. Let it convert the TAB01/TAB02 (or whatever
and see what it looks like.

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

dickjaz@xxxxxxx wrote:
I am helping a customer "modernize" their RPG II code. They use a lot of TAB01/TAB02 type look ups. I was trying to find some direction on how to move those to definition specifications. For the time being I converted them to parallel arrays and use a resulting subscript. This requires code changes and possible errors. Does anyone know where to look or have examples of using tables in "D" spec.s? I would like to get rid of the '**' loads.
TIA,
Dick J (AZ)


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.