Hewlett-Packard Company and the Year 2000
Web Site for the HP Year 2000 Product Compliance Definition:
http://www.hp.com/year2000/compliance.html
Background
With an increasing number of companies providing services to help you transition into the next century, it is important to know what it means to be Year 2000 Compliant. The purpose of this data sheet is to provide you with information that will help you understand HP’s definition of compliance.
Year 2000 Compliance Definition
A "Compliant" product accurately processes date data (including, but not limited to: calculating, comparing and sequencing dates), from, into and between the twentieth and twenty-first centuries, the years 1999 and 2000, and leap year calculations, when used in accordance with its product documentation, and provided all other products used in combination with the product properly exchange data with it. For the few products that are Compliant and require specific customer action, such actions will be clearly detailed.
Products that do no date related processing ("NDRP") are considered to be Compliant. Any product that is not deemed to have a status of Compliant or NDRP is assigned a status of "Non-Compliant."
HP encourages 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. HP also encourages its customers to take responsibility for addressing needed changes as quickly as possible.
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.
Listed below in Table 1 and Table 2 are the mandatory Year 2000 test cases and checklist items required for all new HP products to validate their Year 2000 compliance.
Table 1: Mandatory Test Cases for a Product to be Compliant |
|
Dec 31, 1998 to Jan 1, 1999 |
Test for border line (beginning and ending of a year) for year prior to year 2000 • System rollover in both powered-up and powered-down states, or • Program rollover in both executing and non-executing states. |
Sept 9, 1999 to Sept 10, 1999 |
Tests related to 9-9-99 • System rollover in both powered-up and powered-down states, • System date can be set to before date. • System re-initializes from cold start on before date, or • Program rollover in both executing and non-executing states. • Program retrieves/accepts before date in executing state. • Program re-initializes from non-executing state on before date. |
Dec 31, 1999 to Jan 1, 2000 |
Test for critical transition of 1999 to 2000 • System rollover in both powered-up and powered-down states, • System date can be set to both before and after dates. • System re-initializes from cold start on both before and after dates, or • Program rollover in both executing and non-executing states. • Program retrieves/accepts both before and after dates in executing state. • Program re-initializes from non-executing state on both before and after dates. |
Feb 28, 2000 to Feb 29, 2000 |
Test to verify year 2000 is identified as a leap year • System rollover in both powered-up and powered-down states, • System date can be set to after date. • System re-initializes from cold start on after date, or • Program rollover in both executing and non-executing states. • Program retrieves/accepts after date in executing state. • Program re-initializes from non-executing state on after date. |
Feb 29, 2000 to Mar 1, 2000 |
Another Year 2000 leap year test • System rollover in both powered-up and powered-down states, or • Program rollover in both executing and non-executing states. |
Dec 31, 2000 to Jan 1, 2001 |
Test for transition from 12-31-00 to 1-1-1 • System rollover in both powered-up and powered-down states, or • Program rollover in both executing and non-executing states. |
Table 2: Mandatory Checklist for a Product to be Compliant |
|
Basics |
1. Data Structures Within the Product a. Database Structure b. File System Structure c. Holding or Working fields 2. Date Manipulation Routines 3. Called System Intrinsics 4. Date Comparison Routines 5. Date Fields on Report |
Module Interfaces Internal Date Data Exchanges |
6. Data Structures for Interfaces Inbound to each Module 7. Data Structures for Interfaces Outbound from each Module. |
Product Interfaces External Date Data Exchanges |
8. Data Structures for Interfaces Inbound to the Product 9. Data Structures for Interfaces Outbound from the Product |
Product Environment |
10. Third-Party Utilities or tools used by/with the Product 11. Date Logic Embedded in the JCL or Run Logic of the Product |