Using floating point numbers in RPG - Revision history

PoC: +Link

2023-02-23T21:27:47Z

+Link

← Older revision		Revision as of 23:27, 23 February 2023
Line 19:		Line 19:

	Do not attempt to use <code>MOVE</code> for copying floating point data between variables. If you do, the compiler will give you error RNF7547. You must use <code>EVAL</code> as shown above.<ref>This raises questions about how to program with floating point variables in pre-ILE RPG.</ref>		Do not attempt to use <code>MOVE</code> for copying floating point data between variables. If you do, the compiler will give you error RNF7547. You must use <code>EVAL</code> as shown above.<ref>This raises questions about how to program with floating point variables in pre-ILE RPG.</ref>

			== See also ==
			*[[Using timestamps in RPG]]

	== Weblinks ==		== Weblinks ==

PoC: Typo

2023-02-23T21:18:44Z

Typo

← Older revision		Revision as of 23:18, 23 February 2023
Line 1:		Line 1:
	Using ''' floating point numbers in RPG''' is not as straightforward as using character, or decimal fields.		Using '''floating point numbers in RPG''' is not as straightforward as using character, or decimal fields.

	Not unlike date/time/timestamp fields, RPG has an ''internal'' way to handle those data types, which is incompatible with the ''external'' representation in externally described fields, such as database- and display files. While adding the internal date/time handling routines is a compile time option, this isn't the case for floating point operations.		Not unlike date/time/timestamp fields, RPG has an ''internal'' way to handle those data types, which is incompatible with the ''external'' representation in externally described fields, such as database- and display files. While adding the internal date/time handling routines is a compile time option, this isn't the case for floating point operations.

PoC: New

2023-02-23T21:16:19Z

New

New page

Using ''' floating point numbers in RPG''' is not as straightforward as using character, or decimal fields.

Not unlike date/time/timestamp fields, RPG has an ''internal'' way to handle those data types, which is incompatible with the ''external'' representation in externally described fields, such as database- and display files. While adding the internal date/time handling routines is a compile time option, this isn't the case for floating point operations.

== Example ==
* PF:
A S_TEMPVAL 4F 1

* DSPF:
A S_TEMPVAL$ 4Y 1O 16 52EDTCDE(P)

* RPGLE:
C EVAL S_TEMPVAL$ = S_TEMPVAL

=== Pitfalls ===
If you derive the DSPF field by referencing the PF field, the compiler will give you error RNF7452.

If you create an unreferenced DSPF field with type <code>F</code>, you'll get output in ''scientific'' notation with numbers and an exponent. If this isn't what you want, define the field as pure numeric <code>F</code> as shown in the example above.

Do not attempt to use <code>MOVE</code> for copying floating point data between variables. If you do, the compiler will give you error RNF7547. You must use <code>EVAL</code> as shown above.<ref>This raises questions about how to program with floating point variables in pre-ILE RPG.</ref>

== Weblinks ==
* [https://www.ibm.com/docs/en/rdfi/9.6.0?topic=SSAE4W_9.6.0/com.ibm.etools.iseries.ilerpg.doc/RNF7452.html RNF7452], IBM Rational Developer for i
* [https://www.ibm.com/docs/en/rdfi/9.6.0?topic=SSAE4W_9.6.0/com.ibm.etools.iseries.ilerpg.doc/RNF7547.html RNF7547], IBM Rational Developer for i

== Footnotes ==
<references />

[[Category: Programming]]