|
Using INDDS you have 2 sets of indicators 1 -99. One set (the INDDS) is used to control the display file functions & the others (*IN) are usable only by the RPG program. Setting on the excludesys will not in anyway affect the indicators in the *IN set of indicators. Personally I don't use INDDS...I just overlay the *IN set with meaningful names so I can reference either *IN27 or ExcludeSys. For example: D IndArrPtr s * Inz(%Addr(*In)) D ds Based(IndArrPtr) D Sfl1_Dsp 30 30 D Sfl1_DspCtl 31 31 D Sfl1_Clear 32 32 D Sfl1_End 97 97 D Sfl2_Dsp 40 40 D Sfl2_DspCtl 41 41 D Sfl2_Clear 42 42 D Sfl2_End 98 98 This will overlay the *IN indicators so now I can reference *IN30 or SFL1_DSP & "both" are turned on since they are actually the same indicator ( place in memory) Thanks, Tommy Holden -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan Sent: Wednesday, December 06, 2006 10:38 AM To: RPG programming on the AS400 / iSeries Subject: Re: Indicator Redux No. I wouldn't use the pointer method at all. I haven't used it since named indicators came out in V5R1? If you have INDARA specified in your display file, and you have an INDDS in your RPG program, you're making the association between the numeric indicator in your display file and the named indicator in your RPG program. It's the same indicator. If this isn't working, you're not using INDARA/INDDS correctly. Post some code... On 12/6/06, Turnidge, Dave <DTurnidge@xxxxxxxxxxxxxxxxxxxx> wrote:
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.
-- 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. -- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.