RE: usage of indictators with menu options

[qsrvbas@xxxxxxxxxxxx]

rpg400-l-request@xxxxxxxxxxxx wrote:

>   1. usage of indictators with menu options (Douglas W. Palme)
>
>We have been using indicators with our menu options to turn on or off 
>certain functions, programs, etc. based on a users security settings.  As an 
>example, our Billing Menu uses *IN51 if it is set to *ON then the user can 
>access that menu, if not, it is not even displayed for them.

Douglas:

I might not be understanding correctly. It seems to me that you simply 
shouldn't use indicators for any new menus or menu options. Instead, use the 
DSPATR keyword with P-Fields to indicate non-display of the option(s).

Create a P-field named something like ND_opt1 and specify it as 
DSPATR(&ND_opt1) on the field on the display. Put hex '27' in it when you don't 
want it to display and hex '20' when you want it displayed normally.

The DDS documentation for the DSPATR keyword shows examples.

In short, your program would set the hex value in the P-field instead of 
setting an indicator on/off.

If you do this for new options/menus, you shouldn't have to make any changes 
for existing ones. You could phase out indicators over time.

Tom Liotta