Re: Named indicators (was DOW vs DOU)

["James W. Kilgore" <qappdsn@xxxxxxx>]

David Gibbs wrote:
> There's no reason you can't move *ON to any 1 character field... 
> 
> D rnfINP30      S                       LIKE(*IN90)
> .
> .
> .
> C                            CHAIN    INR30                     90
> C                            EVAL       rnfINP30 = *IN90
> .
> .
> .
> C                           IF  rnfINP30 = *ON
> .
> .
> .
> C               ENDIF
> .
> .
> 
> Get my meaning?
> 
Yes, that does work.  In our shop we use a single indicator for ALL
chain and read operations and move the result to a unique variable by
record retrieved. (ie: CUSThit, ITEMhit)

Just a personal preferance to use a variable that responds with yes/no
instead of on/off.

I suppose it's how you name the variable-- 
===================================================
James W. Kilgore   | Progressive Data Systems, Inc.
President          | 311 31st Ave SE
(206) 848-2567     | Puyallup, Washington 98374 USA
qappdsn@ibm.net    | http://www.ultimate.org/PDS
===================================================
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *