|
DSPPGMREF shows the service programs in use - these are the same as are
listed in the *SRVPGM detail of DSPPGM - and they do not have anything
special - there are 4, QRNXIE, QRNXIO, QRNXUTIL, and QLEAWI - these are
always there, I believe, and have always been - they must comprise the
RPG engine. I've not probed more deeply to see what procedures are in
any of those, maybe there are new ones.
In a way, I think the point is, you should not need to know. Except that
now we might WANT to know.
I ran DMPOBJ against both kinds of programs - the handler-type had an
entry in a string directory of QRNX_GET_HANDLER - the regular one did
not have that. Now the regular one also had no IO, and this procedure is
in QRNXUTIL
A program with a handler has QRNXUTIL in the list of service programs
when you DSPPGM. A program without a handler might NOT have that service
program, not sure, since there are more things in there.
So that's enough treasure-hunting for now. If you feel you need this,
perhaps make a service call and ask to have it added - or use the DCR
approach or the COMMON requirement approach.
HTH
Vern
On 3/25/2011 9:53 AM, Ken Sims wrote:
Hi Tom -
On Fri, 25 Mar 2011 08:19:09 -0400, "Tom Deskevich"
<thomas.l.deskevich@xxxxxxxxxxxxx> wrote:
Ok, I have tried DSPPGM DSPOBJD and cannot see anything that shows me definitively that my RPG program will use a handler.I'm not using handlers and I haven't been following the discussion
that closely so I don't know if they use bound calls or dynamic calls.
But if it is a bound call you should be able to see something in
DSPPGM or if it is a dynamic call you should be able to see something
in DSPPGMREF.
Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.
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.