What message file?

I searched the archives and spent a little time at the IBM site but to
no avail...

I would like to have a routine that would translate ERRC0100 error
parameters from an API call to displayable text.
Naturally, I went to the QMHRTVM API to do so.

However, there is nothing in the ERRC0100 parms that include the message
file the message id came from (unlike most of the QMH API's which do).
Generally, messages are in QCPFMSG. And I read some nice posts that said
that almost all messages are there. But no-one explain about 'the
others'.

Is there a definitive way to know what message file contains a
particular message ID, or (specifically) if an API trips an error what
message file that message comes from? Answers like 'almost all' really
bother me when I'm attempting to define a department standard.

I thought about taking the message as returned from the API through the
ERRC0100 data structure and sending that as a message (QMHSNDPM or
such), then receiving that message thereby having the message file used
that most message API's return. But that seems a little silly to me. The
system returned me the error ID in the ERRC0100 structure - surely it
knows at that point where the message file is? The ERRC0200 structure
also doesn't include that data. Is there more formats available?

Looking for a maintainable solution.

Thanks

James P. Wiant
Testing Coordinator
Foodstuffs, Auckland, Ltd.
60 Roma Road
Auckland, New Zealand
09-621-0774
jim.wiant@xxxxxxxxxxxxxxxx



If you forget you have to struggle for improvement you go backward.
Hickson, Geoffrey


This message has been sent from Foodstuffs (Auckland) Limited ("Foodstuffs").

The information contained in this message and or attachments
is intended only for the person or entity to which it is
addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other
use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended
recipient is prohibited. If you received this in error,
please contact the sender and delete the material from any
system and destroy any copies.

The views and opinions expressed in this message may be those
of the individual and not necessarily those of Foodstuffs,
and are not given or endorsed by it.

Please note that this communication does not designate an
information system for the purposes of the Electronic
Transactions Act 2002.