|
In our development environment, we have a development message file (ARDEV/DEVMSGF), and a QC-level message file (ARQCOBJ/QCMSGF). The message could be in those or in the regular message file. We want to show the development message (if it exists) before the QC message, and the QC message before the production message in SYSMSGF. So this program (SNDMSG) is called whenever a program needs to send a message subfile message: PGM PARM(&MSGID) DCL VAR(&MSGID) TYPE(*CHAR) LEN(7) MONMSG MSGID(CPF0000) OVRMSGF MSGF(SYSMSGF) TOMSGF(ARQCOBJ/QCMSGF) OVRMSGF MSGF(QCMSGF) TOMSGF(ARDEV/DEVMSGF) SNDPGMMSG MSGID(&MSGID) MSGF(SYSMSGF) ENDPGM OVRMSGF has no errors even if QCMSGF and DEVMSGF don't exist. So we use this program on production as well. I guess you can use the principal to override to a language-specific message file. If it does not exist, then it will just use the file specified in SNDPGMMSG. Francis Lapeyre IS Dept. Programmer/Analyst Stewart Enterprises, Inc. E-mail: flapeyre@xxxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles Sent: Tuesday, July 25, 2006 9:18 AM To: Midrange Systems Technical Discussion Subject: RE: Do you still use *MSGF exclusively?
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Al Mac Sent: Tuesday, July 25, 2006 9:33 AM To: Midrange Systems Technical Discussion Subject: RE: Do you still use *MSGF exclusively? Also MSGF* does not seem to have the usual *LIBL rules. Suppose I have two similar MSGF* in *LIBL and let's suppose message 1234 is in the first but not second object it gets to in *LIBL ... OS/400 gets to the first MSGF* does not find message 1234 and stops, does not go looking in any later MSGF* in the *LIBL.
I disagree with the statement that MSGF doesn't have the usual *LIBL rules. Consider a regular file that exists in two separate libraries both of which are in the library list. When you chain to the file with a given key, only the first file is checked, because that's the only one that was opened. Display files, printer files, everything works the same way. The only exception I can think of is /include files in RPG. With include files, if the specified member isn't found in the first file found in the library list, then the next file found in the library list is checked. I'm not sure that behavior makes sense for anything else. I can kind of see where it would be helpful for message files, but having the OS perform a search every time a message is sent seems like a very costly proposition. Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.