My current site uses a lot of custom menus, created via SDA. At present there is no way of knowing if the user's environment is live, test, development or whatever and I'd like to use a message literal to provide a header line in the top row of all menus making the environment explicit. All I could manage today was a MSGCON which obviously pulls in the literal at compile time, meaning each environment would need its own menu. If I manually add a MSGID keyword, it gets deleted when the menu is compiled.
I remember this being an issue years ago. Perhaps someone reading this has found a way around it.
If I manually add a MSGID keyword, it gets deleted when the menu is compiled.
That's right. If you compile it through the SDA menu option after making changes or simply after running through the process without changing the display image, the display source is rewritten by SDA to contain only the keywords that the option supports.
But you can edit the DDS for the display image (the MNUDDS member) and compile just that part as a simple DSPF.
You might create a 'work' member that holds just the MSGID() specification that you want. After compiling the menu, copy the 'work' member line over the top of the MSGCON() line and compile the DSPF. The menu will use that DSPF as long as its name and library are correct.
With a little thought, I suppose the customization steps could be automated.
Tom
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!
Discuss This Question: 1  Reply