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



>
>   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 guess I don't understand.  Why does the length on the %DEC() or %DECH()
need to be variable?  Can't you have it return a 31P 9 (or something like
that) and then let the programmer assign it to any numeric field he
pleases?

If the data is in an Excel spreadsheet, why are you extracting it from a
character string?  Last I checked, Excel stores numbers in 8F format, all
you'd need to do is an assignment.

If nothing else, couldn't you use LBCPYNV to convert the field from one
format to another?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.