Re: Indicator Redux

If you are using the INDARA in your display file, and the INDDS keyword in your 
program to specify the data structure for  the indicators, you do not need the 
*INxx for anything.
the INDDS keyword maps the indicator data structure to the display file, so by 
setting position 27 in the INDDS to *ON, you effectivly set *IN27 on FOR THE 
DISPLAY FILE ONLY.
This does NOT effect anything else, although you can use the variable that you 
defined for the indicator as you would any other variable.
 
Jeff Young 
Sr. Programmer Analyst
Dynax Solutions, Inc.
A wholly owned subsidiary of enherent Corp.
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2 
IBM  Certified Specialist- e(logo) server i5Series Technical Solutions Designer 
V5R3
IBM  Certified Specialist- e(logo)server i5Series Technical Solutions 
Implementer V5R3 


  
 





----- Original Message ----
From: "Turnidge, Dave" <DTurnidge@xxxxxxxxxxxxxxxxxxxx>
To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, December 6, 2006 11:28:45 AM
Subject: RE: Indicator Redux


I have INDDS and INDARA... So, it appears that in order to get indicator
*IN27 turned on with a data structure, I have to use the "pointer
method".... Is that correct? 

-----Original Message-----
From: rpg400-l-bounces+dturnidge=oldrepublictitle.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+dturnidge=oldrepublictitle.com@xxxxxxxxxxxx] On
Behalf Of Wilt, Charles
Sent: Wednesday, December 06, 2006 10:26 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Indicator Redux

Dave,

The only time there's more than one set of indicators is when the INDDS
keyword is specified on a (display/printer) file's f-spec to go along
with the INDARA keyword in the file's DDS.

Otherwise, there is only one set.

*IN27 always(*) refers to the RPG indicators, which via the "pointer
method" could be given readable names.

If you're not using INDDS, then *IN27 would be shared with the display
file.  

Sounds like you are using INDDS, thus the only way to reference the
display file indicator 27 is via the name ExcludeSys assigned via the DS
specified with INDDS.

*note: "always" may not be correct as I imagine you could play some
pointer games.  But without doing that, I think "always" is correct.

HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer Mitsubishi Electric Automotive
America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Turnidge, Dave
Sent: Wednesday, December 06, 2006 11: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

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing 
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, 
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a 
moment to review the archives at http://archive.midrange.com/rpg400-l.