× 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.



An approach I've taken in my message handling *SRVPGM is to specify a call
stack entry value of *PGMBDY and and a call stack entry qualification value
of '*NONE ' + the name of my caller. I use the Retrieve Call Stack
(QWVRCSTK) API to determine the name of my caller. This seems to work
pretty well (or at least no one has complained).

Bruce Vining

On Wed, Oct 15, 2014 at 2:36 PM, Joep Beckeringh <joep.beckeringh@xxxxxxxxxx
wrote:

Hi Scott,

Yes, I used something like that as well. But instead of counting the call
stack entries I had the caller pass its name (from the PSDS) as a
parameter, so the call to QMHSNDPM can use *PGMNAME with the call stack
entry qualification parameter.

Joep Beckeringh



Op 15 okt. 2014, om 19:57 heeft Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
het volgende geschreven:

Hi there Joep,

Yes, that has always been a dilemna for me as well. Unfortunately,
there's no perfect solution. In some applications using *PGMBDY 1 works
nicely -- because I want to send to whomever called my service program.

But, for the other circumstance where I have a "send error" utility
called from a program, and I want to send to that program's caller, there's
no easy solution. The best I've come up with is to accept a parameter with
the number of call stack levels. So the "send error" procedure accepts
this parameter, and uses call stack '*' and call stack count is the
parameter. That way, my program can specify 2, 3, 4... whatever it needs
to go to the level that program desires.

Of course, that's clumsy because I have to count the call stack levels,
etc, but it's the best I've found.

*CTLBDY could work nicely if you always use ACTGRP(*NEW) (or in some
other way put every program in a diff activation group) -- but there are
many circumstances where this isn't practical, either.

-SK


--
This is the RPG programming on the IBM i (AS/400 and 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.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.