iTP Active Transaction Pages (iTP ATP) Programmer's Guide

Introduction
iTP Active Transaction Pages (iTP ATP) Programmer’s Guide—522292-002
1-7
Restrictions
For a list of conversion routines, refer to the Guardian Programmer’s Guide, and for
more information about conversion routines, refer to the Guardian Procedure Calls
Reference Manual.
Restrictions
When IEEE floating-point support is enabled, the following restrictions are applied to
ATP 2.1:
•
No NonStop Tuxedo support is available. The NonStop Tuxedo software supports
only Compaq floating-point values. All Tuxedo-related objects, such as
atp.fml_field, atp.fml_buffer, and atp.fml_table, become
undefined. Once the installation process detects IEEE floating-point support on the
target system, the NonStop Tuxedo installation options are disabled automatically.
•
Conversion routines are invoked internally, as described under Conversion Routines
on page 1-7.
Conversion Routines
Compaq and IEEE floating-point conversion routines are invoked internally for
SQL/MP functions. The precision of conversion, which is handled by ATP, depends on
NSK system functions, such as:
•
NSK_FLOAT_TNS64_TO_IEEE64_
•
NSK_FLOAT_TNS32_TO_IEEE64_
•
NSK_FLOAT_IEEE64_TO_TNS32_
•
NSK_FLOAT_IEEE64_TO_TNS64_
Pathway Data Buffer
The atp.buffer.ieee property enables you to specify the floating-point format of
the Pathway data buffer.
The atp.buffer.ieee property is a JavaScript Boolean type variable. The default
value is false, which means that the Compaq floating-point format is used and that
conversion routines (described previously) will be invoked if the target system supports
IEEE floating-point format.
To communicate with the IEEE floating-point enabled Pathway server, you must set the
atp.buffer.ieee property to true prior to using the setData or setBinary
methods.