× 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.



Hi Dennis,

You're probably missing nothing at all! I was just surprised that the
QPRCRTPG API doesn't flag /MXD, /HI, /NOR, /TR or /ZC as an invalid
branch/indicator keyword for the ADDN(IS) statement - that's all. I was
expecting a more rigorous syntax check from QPRCRTPG.

Based on the documentation provided by IBM, the valid branch/indicator tests
for ADDN are POS, NEG, ZER and UNOR - correct?

My question is why does QPRCRTPG see no fault with /HI, /MXD, /NOR, /TR, and
/ZC on the ADDN(IS) statements? My assumption is because the /POS
branch/indicator belongs to the same Keyword Group as /HI, /MXD, /NOR, /TR,
and /ZC. All six ADDN(IS) statements shown below result in the same
generated code:

ADDN(IS) MYVAR,1 /POS(INDICATOR);
ADDN(IS) MYVAR,1 /HI(INDICATOR);
ADDN(IS) MYVAR,1 /MXD(INDICATOR);
ADDN(IS) MYVAR,1 /NOR(INDICATOR);
ADDN(IS) MYVAR,1 /TR(INDICATOR);
ADDN(IS) MYVAR,1 /ZC(INDICATOR);

It's Friday and I'm probably disappearing up my own orifice looking into
this.

Richard




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2021 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.