Re: %decpos

This is another example of my frustration with BIFs - that we can't use variables for some parameters. %date, %time, %edtc, etc., have the same problem.

Here is the documentation on %DEC - The precision and decimal places must be numeric literals, named constants that represent numeric literals, or built-in functions with a numeric value known at compile-time.

So it appears that SOME parameters need their value known at compile-time, but not all - that makes no sense. I mean, the first parameter is a numeric expression - NOT know at compile-time.

OK - enough grousing - this kind of thing relative to the %edtc is in a requirement to IBM from COMMON. Working on it.

Vern

On 7/24/2012 8:22 AM, rob@xxxxxxxxx wrote:

Why can I do this:
d mydecimal s 2p 0 inz(*zero)
mydecimal=%dec(rplAry(x):%size(mydecimal):0);
but not this
mydecimal=%dec(rplAry(x):%size(mydecimal):%decpos(mydecimal));
RNF0329: The third parameter for %DEC or %DECH is not valid.

IBM Rational Developer for Power Systems Software
5724-Y99, 5733-RDG, 5733-RDH, 5733-RDJ, 5733-RDC
Licensed Materials - Property of IBM

Version: 8.0.3

Rob Berendt