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


  1.  Home
  2. RPG400-L
  3. February 2012

Re: %SUBARR compile error

Gary,

Why do you think you cannot compare two variables for the DOW loop? The loop is controlled by an expression that can contain as many variables as you like, e.g.: DOW ((a < b) and c = d) or (e > f and g = h)).

Joep Beckeringh

Op 29-02-12 16:26, Gary Thompson schreef:
Agreed, testing a variable value against an array
without specifying the array element would be an error.
In this case, bf@ is defined as an Integer and is used as an
index on array bf#:

EvalR BrkFldRt# = %Subarr(bf#: bf@ + 3: bfEle);

However, your change DID work: Thank you!

Not sure I understand why I cannot compare two variables
to control the Dow loop. A quick read of ILE RPG
Language Reference did not penetrate my skull.

I admit, that is more prone to error, so using a CONST,
in this context, works fine for me.

Also, RNF5343 "Array has too many omitted indexes; ...",
in this context, was and is a confusing message for me.

Again, thank you for your help.



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