This technique may be used if you are using a rules based system that is
modified without coding.
For example:
Having seen this in several pricing systems, it is useful when at the
time the order was placed, the order passed the rules then in force. If
at a later date when the order is finally processed you do not have to
try to "back-date" the rules processing. There are times when some
rules are at original entry versus at point of use.
HTH,
Sharon Wintermute
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Thursday, January 14, 2010 8:37 AM
To: RPG programming on the IBM i / System i
Subject: rpg style question
Hi,
Having to regularly determine the value of flags as 'Y' or 'N', then
record it in a PF.
This means having to code
IF rules satisfied;
MyFlag = gYES;
ELSE;
MyFlag = gNO;
Endif;
Then, maybe in another module,etc
IF MyFlag <> gYES;
Don't do stuff;
ELSE;
Do stuff;
Endif
Comments?
What's the reasoning behind this method?
I'd <like> to be able to use an indicator :
MyFlag = ( rules satisfied);
Then,
IF MyFlag;
do stuff;
ELSE;
Don't Do stuff;
Endif
Thanks.
As an Amazon Associate we earn from qualifying purchases.
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.