Re: RPG COMP HiLoEq

[Bruce Vining <bruce.vining@xxxxxxxxx>]

*IN10 is essentially Not *IN20 in your example.

I'm pretty sure, and Barbara can certainly correct me :), but the general
flow is:

1.  Turn off the indicators defined as resulting indicators (10 and 20 in
your case)
2.  Turn on the indicator meeting the comparison condition

So *in10 should be on in a true low comparison.

Did this ever bring back old memories :)  Anyone remember 'A' in column 66,
or '__ __ 99' when scribbling RPG on a pad of paper (for later entry when
in the office as there was no access to the system from home in the
70s/early 80s)? lol

On Sun, May 17, 2020 at 2:54 AM Booth Martin <booth@xxxxxxxxxxxx> wrote:

> That was the original assumption.  The issue came up because we're
> finding a LO condition does not turn on *in10.  So there is something
> else going on.
>
> On 5/16/2020 10:31 PM, midrange wrote:
> > If high then *IN10 = '1'
> > If low then *IN10 = '1'
> > If equal then *IN20='1'
> >
> > Could also be like this...
> > C    A    COMP B                  101520
> >
> > Jim
> --
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com