After "Sam L" and I both found the answer to percolating error messages, when I tried it on the real program, and discovered that I was percolating a whole lot of *unwanted* completion messages, *burying* the one I *wanted* to percolate.

And just as I was framing the question, I looked through the QMH-series API calls, and found QMHRMVPM.

And so, given that I had absolutely no interest in the other messages being percolated, now, before I call the program that creates the message to be percolated (and assuming QMHRMVPM is prototyped as RMVPGMMSG),
CALLP RMVPGMMSG('*':0:' ':'*ALL':ERRORCODE)

and then after the call, I have the QMHMOVPM call,

CALLP MOVPGMMSG(' ':'*COMP':1:'*':2:ERRORCODE)

and now, I get the intended result, without the huge amount of chaff.

Maybe I'm not quite as incompetent as I think I am.

--
JHHL

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