|
Thanks, Rory, that's a good option.
As long as I'm in there monkeying with the procedure, I think I'll add a
callback option also. There have been many times that such capability would
have been useful, for more than just this.
I do like your suggestion of optional parm to indicate how far up the stack
to send, but I'm not convinced that the caller should need to concern itself
with such counters. Still, I will implement that cuz it just makes sense!
:)
Strange that I seem to be the only one who feels IBM made ILE message
handling unnecessarily complex and cumbersome. Must be a personal problem.
:)
++
Dennis
++
"Man does not live by words alone, despite the fact that sometimes he has
to eat them."
-- Adlai Stevenson
Sent from my Galaxy tablet phone. Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++
"Rory Hewitt" <rory.hewitt@xxxxxxxxx> wrote:
Dennis,
I have a similar procedure and I use QMHMOVPM. I use optional
parameters to
my execCmd() to specify how far up the call stack the messages should
be
moved.
Rory
On Fri, Oct 28, 2011 at 7:03 AM, Dennis <iseries@xxxxxxxxxxxx> wrote:
I'll admit it: The QMH* APIs use of Call Stack is strange andunnecessarily
complex, it seems to me. In that line, this has eluded me foryears, and I
hope someone has found a solution.messages
Situation is that a procedure (known as excCmd) in a Service Program
executes arbitrary commands. As one might guess, a huge variety of
may result from such arbitrary commands - and there are times whenthe
caller of excCmd could benefit from acessing those messages.However, I
have never found a suitable combination of parameters that will allowcaller of
QMHRCVPM to retrieve any of those resultant messages within the
excCmd (or further up the stack, for that matter). Conceivably, thismay be
accomplished by having excCmd push the messages up the stack(QMHMOVPM), but
there just might be a better way. (I thought of adding a callbackprocedure
capability to excCmd, which would likely be a workable solution, butif
there's a cleaner way, I'm for it.)mailing list
Any suggestions out there?
++
Dennis
++
Thought for the day:
"Smile", they said, "it could be worse!" So I did, and it was.
Sent from my Galaxy tablet phone. Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++
--
This is the RPG programming on the IBM i / System i (RPG400-L)
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.
--
Rory Hewitt
http://www.linkedin.com/in/roryhewitt
--
This is the RPG programming on the IBM i / System i (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 is the RPG programming on the IBM i / System i (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 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.