× 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: RPG IV Performance
  • From: Douglas Handy <dhandy1@xxxxxxxxxxxxx>
  • Date: Fri, 19 Jan 2001 19:18:08 -0500

David/Lisa,

>It sounds like he was comparing an plain observable OPM program to a ILE
>program will all debug views included (which includes full source for a
>program so you can debug it without having the original source code
>available).

And not only that, but the increased size of debug views doesn't even affect
normal performance.  The debug view data is kept in separate pages, and unless
you are running under debug the *only* difference (as I understand it) is in
DASD size.  On the systems where I've worked, the DASD swallowed up by
application data dwarfs the program libraries, even in RPG IV with *LIST debug
view, so the extra size for debug views is a great asset for debugging while not
really adversely affecting DASD usage.

And in the specific case of triggers, I can't imagine a preference for RPG III
over RPG IV.  Without pointer support I think you'd be hard pressed to make a
trigger which ran faster in RPG III...

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