RE: RPG III program calls faster than RPG IV????

Hi Charles,

You may want to run TRCJOB over the relevant calls in a loop of say 3 and
look at the result. We found in specific instances (the length of the
process status data structure and setting on LR - did not check not setting
on LR) that under the covers when the RPGIV called program was starting up
that it was calling QUSRJOBI (yes the exposed API - not something more
optimised) twice (we didn't ask why), while the RPGIII had a different way
of obtaining what was presumably the same information. Something about this
is documented in the RPGIV Programmer's Guide, I think. This is only really
relevant when the called program is fairly trivial, as in your case. Don't
ask how I know!

Regards,

Kevin Wright.

-----Original Message-----
From: Wilt, Charles [mailto:WiltC@xxxxxxxxxx]
Sent: Monday, 28 July 2008 11:32 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: RPG III program calls faster than RPG IV????


So anybody else have any thoughts?

I realize it's probably not that important in the scheme of things, but I'm
curious as to what's going
on.


Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Wilt, Charles
Sent: Thursday, July 24, 2008 10:23 AM
To: RPG programming on the AS400 / iSeries
Subject: RPG III program calls faster than RPG IV????

All,

I was doing some benchmarking on an unused 515 running v5r4, and I'm
seeing some results that
surprised me...

                        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 of the called programs and the called procedure simply RETURN.


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.

Does anybody have a explanation?


Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307
wiltc@xxxxxxxxxx



This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a
named addressee you are hereby notified that you are not authorized to
read, print, retain, copy or disseminate this communication without the
consent of the sender and that doing so is prohibited and may be unlawful.
Please reply to the message immediately by informing the sender that the
message was misdirected. After replying, please delete and otherwise
erase it and any attachments from your computer system. Your assistance
in correcting this error is appreciated.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a
named addressee you are hereby notified that you are not authorized to read,
print, retain, copy or disseminate this communication without the consent of
the sender and that doing so is prohibited and may be unlawful. Please
reply to the message immediately by informing the sender that the message
was misdirected. After replying, please delete and otherwise erase it and
any attachments from your computer system. Your assistance in correcting
this error is appreciated.