|
To me, it seemed/seems redundant to add a msg file entry AND place
comments in the pgm that echoed (almost exactly) what the msgid was.
The solution to that is to use properly named constants instead of
literal message IDs.
D $FILE_NOT_FOUND C CONST('XYZ9801')
D $BAD_OPTION C CONST('XYZ1234')
/FREE
sndPgmMsg( $FILE_NOT_FOUND :
$PROD_MSGF :
$PROD_LIB :
msgDta :
$MH_MSGT_ESCAPE )
/FREE
Then the only time you need examine the message description is when
you format the msgDta or if you need to modify the text or
substitution data.
Note that if you're clever you can have the sndPgmMsg function accept
an open number of substitution values and it can build a properly
formatted msgDta structure based on information about the message
description retrieved directly from the message file.
Regards,
Simon Coulter.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
