RE: Indicator Redux

["Lapeyre, Francis" <FLAPEYRE@xxxxxxxx>]

Rory,

I see your point about not having to recompile the program, but our
change management application will do that automatically anyway. In any
event, we process everything in the program; we do not let the DSPF do
any validation, so any changes to the display file will require a change
to the program anyway.

Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rory Hewitt
Sent: Wednesday, December 6, 2006 1:29 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Indicator Redux

Francis,

Fair enough. I find it simple to have the INDARA keyword in my DSPF's, *
don't* specify INDDS for the display file in my RPG program and use the
following in my RPG programs:

D Indicators@     S               *   Inz(%addr(*IN))
D Indicators      DS                  Based(Indicators@)
D Inds                          99A
D   SflClr                        N   Overlay(Inds:20)
...

which works exactly the same as your method (named indicators etc.), but
allows the display file to be recompiled without the program also
needing to
be recompiled if I simply add another CA/CF command key to the DSPF...

I've never used the INDDS keyword with this method - there's no need.

Horses for courses, as they say in my homeland.

Rory


On 12/6/06, Lapeyre, Francis <FLAPEYRE@xxxxxxxx> wrote:
> It's just my preference. It is a lot easier for me to convert an old
> program that has *INxx to using named indicators this way. I never got
> the hang of using INDARA, and I never really saw the advantage to it.
To
> me, a separate area for the display indicators is not an advantage.
I'd
> rather have the variables global.
>
> Francis Lapeyre
> IS Dept. Programmer/Analyst
> Stewart Enterprises, Inc.
> E-mail: flapeyre@xxxxxxxx