Re: Recompiling menus: How can CMDLIN and DSPKEY settings be set automatically

Thank you

It is easy to determine the attributes. The easiest way is to display the
menu GO xxxx and observe whether the command line is short, long, or none
and to observe whether function keys are displayed or not.  Then write that
down and use later when compiling.
        
It just seems like these settings (CMDLIN and DSPKEY) are as much a part of
the menu as the commands and display text are.
 (CRTMNU could easily derive these from the menu source)
So it seems like this information is 'lost' when using SDA in that SDA
ignores this information.
I suppose this is a feature. :-)        It just uses the options you used
last time when using SDA.

I have 100 menus to make small changes to and recompile so what I am doing
is to display the menu before I change it and note how the CMDLIN and
Function Keys are set and then when I compile the menu, change the options.
The menus were not all compiled with the same options originally.

Do you have a web site for a change management system?

Dave Pate
----------------------------------------------------------------------------

Either you get a change management system (mucho bucks) or you write some CL
build programs that set the parameters as you want them. There is no command
or API that will show you these attributes - you COULD, I suppose, dump the
object and try to figure out where this information is set, but that sounds
like work.

HTH
Vern
-------------- Original message -------------- 

> It seems that when you recompile a menu it would be nice if it
> remembered how the menu was compiled last time (CMDLIN and DSPKEY options)

> without you having to check how the menu displays currently and 
> then having to change the prompt options for each menu on the CRTMNU 
> command. 
> It is easy to compile the menu the 'wrong' way and have lines 19 
> and 20 not show up where they did show up before. 
> 
> So is that the way you have to do it or is there something I'm
> missing.