× 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: RPT vs RPG
  • From: "James W. Kilgore" <qappdsn@xxxxxxxxxxxxx>
  • Date: Tue, 09 May 2000 08:53:13 -0700
  • Organization: Progressive Data Systems, Inc.

With RPT you can use /COPY members that contain multiple source types and they
will be automatically sorted into their proper sequence.

/COPY for RPGLE does not do this.

For example, in RPG/400 we have a /COPY for each file that contained the key 
list
('C' spec) and data structures ("I" spec) and by specifying RPT as the source
type, the 'I' and 'C' specs would be put in their proper place.

Since RPGLE is the way to go, we created two /COPY members, one with the key 
list
('C' spec) and one with the data structures ('D' specs) and put the /COPY
statements at the point in the program where the code belongs.

HTH

Khouw Thiam Hok wrote:

> Hi,
> Can anyone explain RPT vs RPT differences ( when to apply, advantage and
> disadvantage).

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

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.