I'm not convinced that MI allows such behaviour - but, as always, I'll be
happy to be proven wrong.
From: mi400-bounces@xxxxxxxxxxxx [mailto:mi400-bounces@xxxxxxxxxxxx] On
Behalf Of Dennis Lovelady
Sent: 30 April 2010 16:39
To: 'MI Programming on the AS400 / iSeries'
Subject: Re: [MI400] QPROCT and QPRODT
I can't see the subtle difference you allude to - but that means very
I mean that those are the result flags that are set. You are assuming that
MI limits you to test only the flags that are set by the most recent
instruction. I am suggesting that you can test for things that were not set
by this instruction.
I used to do this in TRS80 assembler. I forget now the exact situation (and
instructions), but I used to do something like:
ADDC RESULT,12 Add 12 to RESULT, with carry
CMP RESULT,16 Compare RESULT against 16
JMP MYTAG,EC Jump to MYTAG if equal or carry
Assume that carry was not set nor reset by CMP. I could still test for it
Now I realize this is not TRS80 assembler (thankfully). I also realize that
I'm not doing a branch on the same instruction line as compare (TRS lacked
that). But I imagine similar rules apply.
"United Nations: Where America feeds the hands that bite it."
-- Gregory Nunn
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MI400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
As an Amazon Associate we earn from qualifying purchases.