|
Hmm...why is this simpler than INDARA? I only use numeric indicators with display files and printer files and that's where INDARA/INDDS is used. I wouldn't use a numeric indicator anyplace else - I would use a Named Indicator. What am I missing? Why would one use an *IN indicator outside of display/printer files? On 12/6/06, Lapeyre, Francis <FLAPEYRE@xxxxxxxx> wrote:
Dave:
You would use it instead of the INDARA or INDDS, yes. Essentially you
are renaming *IN01 - *IN99 to the names of your choice.
In my example, *IN01 is renamed to Update_Mode. You can add similar
lines for any of the other 98 indicators and name them whatever you
want.
For example, I do this a lot:
D Sflclr Like(*IN)
Overlay(Indicators:20)
I have *IN20 conditioning the SFLCLR keyword in the display file, and
now I know exactly what SFLCLR does in the RPG. Don't have to scratch my
head trying to remember what the heck *IN20 does.
Of course, you still have to use the numeric indicators in O-specs,
printer files, and display files, but there is no getting around that,
anyway.
This is just simpler than using INDARA, and more flexible.
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:44 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Indicator Redux
This "pointer" thing is new for me, as far as USING it is concerned. If
I'm reading your code correctly, you are setting up a data structure
over the *IN array. Yes? Where or how does this get related to the
INDARR and INDDS? Would I use the *IN pointer method INSTEAD of INDARR
and INDDS, or use both?
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Lapeyre, Francis
Sent: Wednesday, December 06, 2006 10:34 AM
To: RPG programming on the AS400 / iSeries
Subject: 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
--
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.
--
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-2025 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.