Re: Indicator Arrays in /FREE

["Nick Leonessa" <nleonessa@xxxxxxxxxxxxxxxxxxx>]

Thank you.

This technique does make coding and readability a lot better.


----- Original Message -----
From: "Mary and Jim" <mmjlow@xxxxxxxxxxxxxxxxxx>
To: "'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx>
Sent: Saturday, April 05, 2003 4:19 PM
Subject: RE: Indicator Arrays in /FREE


> I would agree with Mr. Martin - and take it one step farther...
>
> When you must communicate with your screen for attribute control, why not
> use the file level keyword INDARA in your DDS.  When that is done, you
then
> can control your attributes by something more meaningful than *IN90,
*IN91,
> *INnn.  This is done by defining, on the "F" spec associated with the
> workstation, the INDDS(INDVAL).
>
> Doing this will permit communication in a verbal, understandable method:
>
> DINDVAL DS
> D acctNbrError 31 31
> D soundAlarm 36 36
> D globalErrOccured 90 90
> D nonDisplayFld 91 91
>
> D True S 1N Inz( *On )
> D False S 1N Inz( *Off )
>
> When your read to use them, you can even define a True/False data element,
> and establish your description during calculations (very simplified, but
> demonstrates one possible scenario - among hundreds.)
>
> /Free
> Dou keyInput = exitKey;
> // ------------------------------------- *
> // Process screen input *
> // ------------------------------------- *
> Select;
> When keyInput = enterKey;
> .
> .
> . (process screen input)
> .
> If errorHappened;
> soundAlarm = True;
> acctNbrError = True;
> Iter;
> EndIf;
>
> When keyInput = exitKey;
> .
> . (process exit routines)
> .
>
> When keyInput = lookUpAcct;
> .
> . (process lookup)
> .
> Other;
> .
> . (nonstandard key processing)
> .
> EndSl;
> EndDo;
>
>
> Jim Low
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Booth Martin
> Sent: Saturday, April 05, 2003 1:08 PM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Re: Indicator Arrays in /FREE
>
> If you are converting, why not really convert and do away with Indicators
90
> and 91 altogether unless its for a screen format?
>
>  ---------------------------------------------------------
> Booth Martin   http://www.MartinVT.com
> Booth@xxxxxxxxxxxx
> ---------------------------------------------------------
>
> -------Original Message-------
>
> From: RPG programming on the AS400 / iSeries
> Date: Saturday, April 05, 2003 13:47:42
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Indicator Arrays in /FREE
>
> >> I am trying to convert the following to /free format...any suggestions.
>
> >> MOVEA'10' *IN,90
>
> If you only have one such instance, then use separate statements i.e.
> *In90 = *Off;
> *In91 = *Off;
>
> If you have multiple instances of this kind of thing, overlay a DS on the
> *IN array and use meaningful names e.g.
>
>
> D pIndicators S * Inz(%Addr(*In))
>
> D Indicators DS 99 Based(pIndicators)
> D ErrorInds 2a Overlay(Indicators: 90)
> D NameFor90 N Overlay(ErrorInds)
> D NameFor91 N Overlay(ErrorInds: *Next)
>
> /free
> ErrorInds = *Off;
>
> This has not been tested but you should see the idea. I always hated the
> MOVEA to indicators bit - I find this more obvious once you understand the
> basics. You create as many groups as you need. They can overlap one
> another if required.
>
> Jon Paris
> Partner400
> www.Partner400.com
>
> _______________________________________________
> 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.
>
>