RE: Indicator Redux

I do it with a pointer, because I often have to condition things on the
output specifications. But it will work on display files, as well.

 

       // Define indicators

     D P_Indicators    S               *   Inz(%ADDR(*IN))

     D Indicators      DS                  Based(P_Indicators)

     D Update_Mode                         Like(*IN)
Overlay(Indicators:01)

      Begsr *INZSR;                                  
                                                     
      // List or update mode?                        
      Update_Mode = (%PARMS > 0 And P_Update = 'Y'); 
      Endsr;                                              

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 Turnidge, Dave
Sent: Wednesday, December 6, 2006 10:12 AM
To: RPG programming on the AS400 / iSeries
Subject: Indicator Redux

I have looked through the archives having to do with Indicator Arrays,
and am confused. It appears that there are two arrays(?): one for
display file indicators, and one for RPG indicators.

When I started on my current project I was told that I didn't need to
use the "pointer method" to define my indicators, but now I am running
into a problem. I have set up variable "ExcludeSys" for position 27 in
my indicator data structure. However, when I turn ExcludeSys *ON, *IN27
is not *ON, and, I WANT it to be on. 

Please help me understand the difference (if there is one) and/or how to
be able to use a variable name and have the action continue on to the
indicator. Also, if there is a page in a Redbook (or equivalent) that
explains this from IBM's "easy to understand" viewpoint <G> a link would
be nice...

Thank you,

Dave