TREG'ers, As compliance guy, I have been tagged with responding to our customers' Year 2000 questions. One of these make specific reference to a BSI spec on the subject, DISC PD2000-1. This is a 2-page document that invokes the following four rules.
1. No value for current date will cause any interruption in operation. 2) Date-based functionality must behave consistently for dates prior to, during and after year 2000. 3) In all interfaces and data storage, the century in any date must be specified either explicitly or by unambiguous algorithms or inferencing rules. 4) Year 2000 must be recognized as a leap year. Our software meets rules 1 & 2 with no problem, as it does not use the date for any calculations or algorithms. We do, however, use PC's which provide file creation dates for both programs and for customer-generated data bases. We have no control over the format for these dates, as they depend on DOS or Windows operating systems which use 2 digits for the year, and are thus ambiguous with regard to century. A) Even though our system operates fine with any date set in the computer (before, during, or after 2000), do we violate rule 3 (or perhaps rule 4) by using DOS or Windows which create 2-digit file creation dates? B) Can anyone provide names, E-mail address, and phone numbers for someone who could answer the above? I'd especially appreciate answers from BSI who created the spec, or from others facing the same question. advTHANKSance Pete ---------------------------------------------------------------------------- Peter Van Raalte | Email: [email protected] Compliance Engineer | V-Band Corporation | Phone: 914-789-5117 565 Taxter Road | Elmsford NY 10523 | FAX: 914-347-3432 ---------------------------------------------------------------------------
