Re: Converting from scientific to integer/decimal

"M. Lazarus" wrote:
> 
> Barbara,
> 
>   I actually had decided on using %DecH().  The business application is
> data originally coming from an Excel spreadsheet.  I wanted to make a
> generic routine (*Module in a *SRVPGM) out of this conversion.   Since I
> don't know ahead of time what the length being passed might be, I was
> hoping that %Dec and %DecH might allow a runtime value to be used as the
> length (2nd parm in the BIF), but unfortunately, that value must be
> available at compile time.
> 
>   I'm at v5r2.  Has this changed in v5r3.  If not, are there any plans to
> allow it?
> 

There are no current plans to allow a variable for the %DEC/%DECH length
and decimal places.  It would be extremely complex to generate code to
do arithmetic operations using numeric values whose length is not known
at compile time.  
As Scott said, you can just use the maximum length for the digits and
pick some value for the decimals that gives you enough decimal precision
while maximizing your integer places.

In V5R3, the maximum for digits is 63, so you could handle the full V5R2
(len,dec) range of (31,0) to (31,31) by using 63,31 as the length and
decimals.  If you need more than 31 digits of integer places, you would
have to "sacrifice" some of the decimal precision ...