The information in this document should be read in conjunction with other information about MathSoft products, including but not limited to MathSoft's Year 2000 Test Criteria.

Any statements made to you by MathSoft or contained herein in the course of providing Year 2000 related fixes are subject to the Year 2000 Information and Readiness Disclosure Act (112 Stat. 2386). In case of a dispute, this Act may reduce your legal rights regarding the use of any such statements unless otherwise provided by your contract or tariff.

This Year 2000 Readiness Disclosure document supersedes all previous Year 2000 Readiness Disclosure documents concerning these products.

Testing Criteria and Product Assessment

Axum 6 is Year 2000 compliant as defined by Rules 1 - 4 below, subject to the following restrictions and exceptions:

• The operating system and hardware on which these products are running must themselves be Year 2000 compliant
• Axum provides a general purpose programming language in which it is possible for users to write their own date handling objects and routines. Such objects and routines are not necessarily compliant. It is strongly recommended that users examine their code to ensure compliance.
• No claims of compliance are made about unsupported code distributed by MathSoft (for instance, the library chron) or by anyone else.

Rules for Compliance

Rule 1: The product will operate into the 21st century.

Rule 2: Date-based functionality will behave consistently for dates prior to, during, and after year 2000.

Rule 3: If the product allows the user to enter a 2-digit short cut for the year, the year is recognized consistent with a 4-digit format.

Rule 4: Year 2000 is recognized as a leap year.

MathSoft has not received notification from any users regarding Year 2000 compliance problems to date for the following supported products:

• Axum 5.0

MathSoft has not conducted its own year 2000 compliance of the above supported products and modules and can make no representations and warranties regarding their Year 2000 compliance.

Rule 1: The product will operate into the 21st century.

The Axum 6 has been tested with the clock date set beyond 1 January 2000 without any interruption to operation.

Rule 2: Date-based functionality will behave consistently for dates prior to, during and after year 2000.

Axum 6 supports a dates object for representing calendar data.

Axum 6 uses Julian dates (the number of days since a fixed origin date) as the internal representation for dates objects, and therefore allows creation of date objects specifying dates before and after 1 January 2000 and correctly performs calculations involving dates which span this date. The Julian origin for dates objects is stored along with the dates using a full 4-digit year.

In the example below, dates objects are created for 20 December 1999 and 9 January 2000 (the latter correctly calculated as being 20 days after the former).

> date1 <- dates("20/12/99",format="d/m/y", out.format="day month year")

> date1

[1] 20 December 1999

> date1 + 20

[1] 09 January 2000

Rule 3: If the product allows the user to enter a 2-digit short cut for the year, the year is recognized consistent with a 4-digit format

When converting character data using the dates function, the full 4-digit year is used if present. If only the last two digits of the year are given, a 19xx year is assumed. (In Axum 6, the user may specify a different default by using the optional century argument to dates, as explained in documentation.) For example:

> dates("1/4/25",format="d/m/y", out.format="day month year")
 [1] 01 April 1925

> dates("1/4/25",format="d/m/y", out.format="day month year",century=2000)
[1] 01 April 2025

When importing text data from files in Axum 6 using the import.data() function (or using the File … Import Data menu option), the century cutoff for 2-digit dates is 1930. (The date order is month/day/year or day/month/year as specified by the Regional Settings control panel utility in Windows.)

Rule 4: Year 2000 is recognized as a leap year.

The dates function returns a valid dates object for February 29, 2000. (They return the missing value code NA for invalid dates.)

> dates("29/2/2000",format="d/m/y",out.format="day month year")

[1] 29 February 2000

Calculations across leap days are also correct. For example, dates objects recognize that March 1, 2000 is 2 days after February 28, 2000:

> date2 <- dates("28/2/2000",format="d/m/y", out.format="day month year")

> date2 + 2

[1] 01 March 2000