|
Vern, I tried it too. You're right. External indicators won't cut it. You did say you'd accept a CL program to get the menu. Create 3 message files with the same message number but with your 3 different messages. On your Menu SDA (Number 17 in PDM) put a +M (25) on the screen where you want the message displayed. It will prompt for the message file. library, and MSG Number. Write your CL to override the message file to the message file that holds the message you want displayed. In PDM for the menu press F1 and look for +M(nn). It'll explain the messages thing there. I ran out of time to test this, and am worried that the message may be snatched at compile time and therefore this solutiion may fail. Still. it looks ok --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@MartinVT.com --------------------------------------------------------- -------Original Message------- From: Midrange Systems Technical Discussion Date: Friday, February 14, 2003 16:16:22 To: Midrange Systems Technical Discussion Subject: RE: Dynamic part on a standard menu Booth, how do you do this? There's nowhere in the SDA opt 2 to condition a constant. Putting * in front of a constant only gives display attributes and colors. You can always put them into the raw source, but how do you turn them on when you are not the app that's calling (using) the DSPF? Also, I tried U1 in the conditioning indicator location - you can only have 01-99. Regards Vern At 03:08 PM 2/14/2003 -0500, you wrote: >menu constant fields can be conditioned by indicators. I could not find if >allowed indicators include U-1 through U-8. If they are allowed then CL >would be a good solution to set U-1 through U-3 for your problem?
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.