One caveat about Message Files and Printer Files . . . and Soft-Coding of messages extracted from a message file

MSGCON - - where it is compiled into the screen at compile time (old way) and
" If you change the message description, you will have to create the file again if you want the display file to contain the updated message."

MSGID - - where it is dynamically extracted at runtime
CCS0037037 37A O 11 2MSGID(CCS 0037 PLMSGC)
and even the &MSGF can be a variable . . . nice !

- - Our vendor software (Infor Infinium) internationalized the codebase using message files when they introduced Open fields in the DDS.
But it turns out the Printer Files do not do message files nicely like screens, so there is a subproc in the RPG code in every report pgm to retrieve the message's 1st-level-descriptor)
CCS00441 =getmsg1st('CCS0044':'*LIBL/PLMSGC':message_repl);

MSGCON (loads at compile) works for DSPF and PRTF
MSGID (load dynamically at runtime) only works for DSPF

J Voris


message: 2. . .
. . . Column titles (1 row, 2 row) (mostly reports but surely some DSPF's too) are a particular issue.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.