×
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.
Where's what I had...
#Iterations
5M 50M
OPM calling OPM 6s 62s
Dynamic Program Call 12s 122s
Bound Procedure 1s 4s
In the first case, an RPG III *PGM was calling another RPG III *PGM
(which returned with LR = *OFF).
In the second case, an RPG IV *PGM was calling another RPG IV *PGM
(which returned with LR = *OFF).
In the third, an RPG IV *PGM was calling a RPG IV procedure in a *SRVPGM.
Both called programs and the called procedure simply RETURN.
I was going to check to see how much of the 12s was from the dynamic
call vs. the RPG cycle, by replacing the called RPG program with an
ILE C program, but the system I was testing on, a 515 running v5r4,
didn't have the C compiler installed.
I'm a little surprise to see RPG III program calls performing better
than RPG IV program calls.. I thought perhaps it was activation group
related. Initially, I had *NEW calling *CALLER. I tried changing
both program to run in the same named activation group. That had no
effect. So I tried changing both to DFTACTGRP(*YES). That had a
little effect, lowering the times to 11s and 110s.
Charles
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Timestamp vs Date/time Decimal fields, Overhead in RPG programs..., (continued)
This mailing list archive is Copyright 1997-2025 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.