| |
Since Eloquence relies on the underlying operating system
(especially libc) to function correctly, a Year 2000 compliant
operating system is also required.
Eloquence versions below A.05.12 are Not Compliant and will
Not be Made Compliant. Those versions include a DATE$ function which
returns the wrong year after Year 2000 (the year returned is
relative to 1900 instead of two digits as documented). This
problem was corrected with the A.05.12 release.
The QUERY application included with Eloquence is not vulnerable
to the Y2K transition. While the QUERY application optionally
deals with date values in the database it uses a format which is
not affected by Year 2000 (number of days since 1972).
When printing or validating date values, QUERY is (currently)
restricted to a two digit date value. Any year value below 72 will
be considered relative to 2000 (e.g. 50 means 2050).
Please be aware that applications written on top of Eloquence
may still be vulnerable to Y2K transition problems. This is like
any other programming language - when the programmer decided to
save a date value in YYMMDD format the application might need
modifications.
HP has made every effort to ensure the accuracy of our product
testing. However, because each customer's environment is different
from HP's laboratory test environment, it is the customer's
responsibility to validate the Year 2000 readiness of these
products in their own environment. Therefore, information about the
Year 2000 status of HP products is provided "as is" without
warranties of any kind and is subject to change without notice.
HP makes no representation or warranty respecting the accuracy or
reliability of information about non-HP products. Such information,
if any, was provided by the manufacturers of those products and
customers are urged to contact the manufacturer directly to
verify Year 2000 readiness. The information provided here constitutes
a Year 2000 Readiness Disclosure for purposes of the Year 2000
Information and Readiness Disclosure Act.
Hewlett-Packard and Marxmeier Software encourage customers to be fully
aware of the potential impact that the Year 2000 could have on their
business environment and their ability to compete in the 21st century.
We also encourage our customers to take responsibility for addressing
needed changes as quickly as possible. We have made every effort to
ensure the accuracy of our product testing.
Known Issues
- Eloquence A.05.12
- Temporary license keys generated during installation
after Dec 1, 1999 of Eloquence A.05.12 will not work correctly.
The correct function of Eloquence A.05.12 is not affected.
Impact:
Temporary license keys generated during installation after Dec 1, 1999
will not work correctly.
Solution:
Use Eloquence A.05.20 for new installations (recommended)
or request a license key after installation.
As an alternative you can also apply the A.05.20 patch PE52-9912030
(see below).
- Eloquence A.05.20
- Temporary license keys generated during installation
after Dec 1, 1999 of Eloquence A.05.20 will not work correctly.
The correct function of Eloquence A.05.20 is not affected.
Impact:
Temporary license keys generated during installation after Dec 1, 1999
will not work correctly.
Solution:
Patch PE52-9912030 is available for download.
It introduces the new mktmplic tool which allows generation of a
temporary license key after installation.
As an alternative a license key can be requested
after installation.
- Eloquence A.06.00 and A.06.01 (Windows NT server installation)
- Temporary license keys generated during installation
after Dec 1, 1999 of Eloquence A.06.00 and A.06.01 on the
Windows NT server side will not work correctly.
The correct function of Eloquence is not affected.
Impact:
Temporary license keys generated during installation on Windows NT
after Dec 1, 1999 will not work correctly.
Solution:
Either use Eloquence A.06.10 or above for new installations (recommended)
or request a license key after installation of
Eloquence A.06.00 or A.06.01 on the Windows NT server is complete.
- Eloquence A.06.10 and A.06.20 (Windows NT server installation)
- Temporary license keys generated during installation
after Dec 1, 1999 of Eloquence A.06.10 and A.06.20 on the
Windows NT server side will not work correctly.
The correct function of Eloquence is not affected.
Impact:
Temporary license keys generated during installation on Windows NT
after Dec 1, 1999 will not work correctly.
Solution:
For Eloquence A.06.10 and A.06.20, a new setup.exe file is available
on the ftp server which can be used for new installations.
The new setup.exe should be used as a replacement for the setup.exe
delivered with Eloquence. Please note, that the setup.exe and the *.z
package files need to be present in the same directory.
As an alternative a license key can be requested
after installation of Eloquence A.06.10 and A.06.20 is complete.
Important Note:
All information herein is subject to modifications and we strongly recommend to
check back on a regular basis.
|
|
