"MXD is the same as POS and HI" - Agreed, when you look at the generated
code within a program. I'm not disputing this.
I naively expected QPRCRTPG to enforce instruction-specific synonyms for the
indicator/branch forms in the IRP (e.g. POS on ADDN is OK, but MXD and HI
From: mi400-bounces@xxxxxxxxxxxx [mailto:mi400-bounces@xxxxxxxxxxxx] On
Behalf Of James H. H. Lampert
Sent: 30 April 2010 19:17
To: MI Programming on the AS400 / iSeries
Subject: Re: [MI400] QPROCT and QPRODT
Richard Thomas wrote:
My question is: Given that QPRCRTPG is responsible for converting "the
symbolic representation of a machine interface (MI) program into an OPM
program object." - (i.e. from the IRP) - then surely its IRP
should flag /MXD as an invalid indicator/branch form for the ADDN op-code?
But "MXD" is the same as "POS" and "HI."
They're just synonyms for the same configuration of the condition flags,
provided purely for the sake of source code readability: surely you'd
have trouble, without profuse comments, understanding that a ZC
condition meant "greater than" on a comparison, "positive" on a numeric
operation, and "mixed" on a TSTBUM. The synonyms allow us to use result
mnemonics that match what we're conceptually testing for, rather than
just matching the actual flags.
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.