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



one way to look at this is to have a procedure tell its caller what it has
done. The procedure sends program messages to the *PRV call stack. A
procedure runs a command. That command sends back a completion or exception
message at the completion of the command. Instead of the procedure promoting
those messages, it can leave them there and send its own completion or
exception message back to its caller. Presumably, the procedure being called
to run a command is there for a reason. The messages it sends back can
provide context information to what is being done. "program ABC deleted by
the application that promotes objects to production"

-Steve

On Fri, Oct 28, 2011 at 10:03 AM, Dennis <iseries@xxxxxxxxxxxx> wrote:

I'll admit it: The QMH* APIs use of Call Stack is strange and unnecessarily
complex, it seems to me. In that line, this has eluded me for years, and I
hope someone has found a solution.

Situation is that a procedure (known as excCmd) in a Service Program
executes arbitrary commands. As one might guess, a huge variety of messages
may result from such arbitrary commands - and there are times when the
caller of excCmd could benefit from acessing those messages. However, I
have never found a suitable combination of parameters that will allow
QMHRCVPM to retrieve any of those resultant messages within the caller of
excCmd (or further up the stack, for that matter). Conceivably, this may 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 callback procedure
capability to excCmd, which would likely be a workable solution, but if
there's a cleaner way, I'm for it.)

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

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.