× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



-----Message d'origine-----
De : rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Scott Klement
Envoyé : jeudi 14 janvier 2010 18:40
À : RPG programming on the IBM i / System i
Objet : Re: rpg style question

Charles Wilt wrote:
Short answer is you can't do it. RPG treats 1 character fields
different than indicators and you can't define a indicator
field in a
file.

I hadn't thought of that. Maybe that was a reason for not recording '1' or '0' instead of 'Y' or 'N'.

That's true, but the only part that won't work is the part where you
code "if MyFlag;". If you change it to "if MyFlag = *ON",
it'll work
just fine.

D x s 10i 0 inz(14)
D MyFlag s 1a
/free

myFlag = ( x = 14 );
... write to file ...

... then later, read MyFlag from file, and ...

if MyFlag = *on;
do stuff
else;
don't do stuff
endif;

So the only thing you have to add above and beyond coding
exactly what David asked for is the "= *on". Is that really
a show-stopper?

I hadn't thought of that either and that convinces me. Why the hell create a kind of pseudo boolean Y or N? In fact, we have one old file, that has Y, N, blank and O recorded. O meaning <Oui>. The blank looks like an error. The program using this field tests for field<>'N'. Luckily, that means different from <no> AND different from <non> and if it ain't blank, it ain't Yes nor Oui!

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.