×
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.
Hi Paul,
I run into this problem a lot with calling IBM APIs, since the error
message data structure they return ("ERRC0100") does not contain the
message file, only the message ID. Therefore, in many cases, I
instruct it to send me a "real" escape message, monitor for it, and use
the QMHRCVPM API to retrieve the full message from the program message
queue, including the message file.
(This does not perform as well as using the error data structure, since
an actual exception is generated.)
You did not explain your situation very much... but perhaps the same
solution would work for you? From CL, you'd use MONMSG to catch the
error, and RCVMSG to retrieve the details (including the message file).
Or from an HLL, use the APIs that I mentioned above?
Or, if your goal is to re-send the message, you may not need to know all
of this.... there are APIs, QMHRSNEM, for example, that can re-send an
exception message from one queue to another.
-SK
On 4/10/2018 3:37 PM, Steinmetz, Paul wrote:
How does one determine what message file a particular message is from - PQT3073 , PQT4140.
When a new condition occurs that I need to monitor for, I need to specifically identify the *library/*msgf.
midrange.com
