Re: What message file?

On 31/03/2008, at 11:38 AM, Jim Wiant wrote:

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

Probably because:
a) They don't know
b) They are hedging their bets

The 'others' depends on the API in question.
o HTTP APIs send messages from QHTTPMSG in QHTTPSVR or a language library.
o Certificate APIs send messages from QICSMSGF in QICSS or a language library.
o List processing APIs send messages from QGUIMSG in QGY or a language library (note these APIs moved to QSYS at VRM510)

There may be more.

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.

My solution was to derive the message file name from the message ID prefix. Not fool-proof but close enough. I check if the derived message file is in *LIBL otherwise I qualify with the appropriate product library. I determined all the prefixes used by the various message files and wrote code to convert a message ID to a message file. Either hard-code or drive it from a database file.

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.

You still need the message file for QMHSNDPM or SNDPGMMSG to work.

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?

Is there more? Pah! Are there more! No there are not. I agree it is an oversight not to include the message file in the error structure. Seems a DCR may be in order.


Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------