RE: Job behaviour RPGLE vs CLLE -- MIDRANGE-L

× 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: Job behaviour RPGLE vs CLLE
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
Date: Mon, 20 Nov 2006 21:50:48 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

versus:
     MOVEL   'PGM001'   PGMNAM   10
     CALL      PGMNAM

This second case causes RPG to generate the full dynamic call that

"resolves" to the name on each call.  Note that there is more "overhead" for
doing it this way.

Unless the compiler has gone backwards this is not true Mark.  As part of a
performance improvement this was changed a long time back so that the call
is only resolved if the content of the variable (PGMNAM) has changed.


Jon Paris
Partner400

www.Partner400.com

As an Amazon Associate we earn from qualifying purchases.

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.