|
|
Year 2000
Compliance and Operating Systems
Assoft's products derive date and time
information from the operating system of the computer upon which they are running.
This information is procured by standard system calls. If the computer's operating
system is not year 2000 compliant, Assoft's products will reflect this operating
system shortcoming inasmuch as they will report the incorrect date provided by the
operating system in response to standard system calls. Thus, it is imperative the
operating system is year 2000 compliant.
Information on achieving year 2000 compliance for our major hardware partners may be
obtained on the World Wide Web.
If the hardware and operating system software are not in a state of year 2000
compliance, we cannot be held responsible for any problems encountered in the
functioning of our software in time and date related routines. Also, Assoft. cannot
test every possible use of our software with third party applications and operating
systems to assure lack of problems in the year 2000 transition.
Testing method
Assoft. has performed detailed code
reviews and testing to verify that our software operates normally in general
operation and functionality, in processing dates and date-dependent data, and in the
functioning of license management. The following test methods were used to ensure
year 2000 compliance:
-
Verification that our license manager (1332.05) functions correctly with
dates greater than December 31, 1999 and during the transition between the 20th
and 21st centuries.
-
Writing, reading and displaying data sets with dates greater than
December 31, 1999.
-
Reading and displaying data sets on dates greater than December 31, 1999
but with these data sets saved prior to December 31, 1999.
-
We believe that this letter and the information contained within should
address all your concerns. Due to the large number of inquiries we are
receiving, we regret that we will not be able to supply individual responses or
fill out custom questionnaires.
|
|