Re: Indicator enhancements

[bmorris@xxxxxxxxxx]

>Date: Wed, 08 Mar 2000 19:05:01 -0600
>From: Gary Guthrie <GaryGuthrie@home.com>
>
>Consider that
>
>- -1 is a dead customer
>- -2 is a customer who never pays
>- -3 is an industrial spy
>
>So, the usefulness of *NEGATIVE and *POSITIVE figurative constants
>is in the ability to code a layer that is independent of the details.
>This would be clearer ...
>
Here's part of Gary's original append:
>>
>> I submit it might be clearer to:
>>
>>D Error        S      N  Inz( *Negative )
>>D ExistingCust S      N  Inz( *Positive )
>>D NewCust      S      N  Inz( *Off )
>>C              Eval     RtnCode = MyProc( MyParm )
>>C              Select
>>C              When     RtnCode = ExistingCust
>> * Perform existing customer processing
>> ...

Gary, I understand what you're getting at now, but this only makes
sense when you have 2 (3? using *OFF? 4? *ON) categories of return code.

Anyway, what's the difference between what you are suggesting and
coding if "rc < 0"?  Or, coding if "isError(rc)"?

Come to think of it, maybe I don't understand what you're suggesting
now.  Do you want to return specific return codes in an indicator
and have the values compare equal/not-equal to *NEGATIVE and
*POSITIVE, and also have them containing more specific values?

Maybe I'm missing something obvious here ...

Barbara Morris


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---