What I ended up doing was to populate the printer's field in the C-specs, with the retrieved message body. In the end that allowed better control, anyway.

On 9/2/2014 6:34 PM, Jon Paris wrote:
I'm beginning to believe that the folks who did DDS for printer files never talked to the folks who did display files ...

Latest barrier in my conversion effort is lack of support for the MSGID keyword on printer files. MSGCON is supported but that is of no use to me since I need to be able to use the LIBL to control the message file that is used and MSGCON values are resolved at compile time as far as I can tell.

I know a number of you out there write apps that support multiple languages - how the heck do you handle that for printer files?

Jon Paris


Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact