Year 2000 Compliance
Definition
Year 2000 conformity shall mean that neither performance nor functionality is affected by dates prior to, during or after the year 2000. In particular:
- No value for current date will cause any interruption in operation.
- Date-based functionality must behave consistently for dates prior to, during and after year 2000
- In all interfaces and data storage, the century in any date must be specified either explicitly or by unambiguous algorithms or inferencing rules.
- Year 2000 must be recognized as a leap year.
These criteria are Year 2000 conformance requirements set out by the
British Standards Institute
in DISC PD-2000-1:1998 A definition of Year 2000 Conformity Requirements.
Compliance statement
JobScheduler for Oracle Version 3.1 and later is Year 2000 compliant as defined by the conformity requirements above.
Other comments regarding JobScheduler’s Year 2000 Compliance are summarized below:
| Year 2000 compliance issue |
JobScheduler for Oracle status |
|
Handle date information before, during and after 1st January 2000,
including, but not limited to, accepting date input, providing date
output and performing calculations on dates or portions of dates
|
Yes, for all versions |
|
Function accurately and without interruption before, during and
after 1st January 2000, without any change or disruption in operations
associated with the advent of the year 2000 and the new century
|
Yes, for all versions |
|
Respond to two digit year input in a way that resolves the ambiguity as to
century in a disclosed, defined and predetermined manner
|
Yes, for Version 3.1 (no longer accepts 2-digit dates, which would get
expanded to 20xx in some fields, and 19xx in others)
|
|
Process two digit year information in ways that are similarly unambiguous
as to century
|
Yes, in Version 3.1 |
|
Recognize and respond to fact that the year 2000 is a leap year
|
Yes, for all versions |
|
