Scott,
I was looking for some "green screen" command that would tell me.
I don't need an API.
I did find it.
Message file: QPQMSGF Library: QSYS
To load my message monitor config, once and done.
Message IDs . . . . . . . . PQT3073 PQT4140
Message file . . . . . . . QPQMSGF Name, *ALL, F4=Prompt
Library . . . . . . . . . QSYS Name, *LIBL
ASP group . . . . . . . *SYSBAS Name, *SYSBAS, F4=Prompt
Thanks
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Tuesday, April 10, 2018 4:55 PM
To: Midrange Systems Technical Discussion
Subject: Re: How does one determine what message file a particular message is from - PQT3073 , PQT4140
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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
