Reply to:   RE>>TAA and Year 2000 Requir

Chris,

The voluntary or mandatory question refering to a standard is not always 
defined. But the impact of the year 2000 makes the ISO 8601 a mandatory 
requirement for any one company's borders. Even if your company has solved the 
problem, your customers' and suppliers' bad data ultimately could pollute your 
2000-enabled systems...."
Consider the following issues when the century digits change to "20" and "00":
- Invoices old accounts,
- Taxes wrong effective dates,
- Manufacturing systems archive and retrieve old jobs,
- Pharmacies will lock up because all of their drugs will have expired and 
their systems won't dispense them,
- Bank machines, security systems, employee seniority could  change by 99 years 
overnight,
- Etc.......

Some known compliancy problems are:
- In DOS version 6, the date command does not accept two digits years between 
00 anf 79,
- Foxpro is not compliant,
- MS Access version 2 is not compliant,
- Quicken version 3 is not compliant,
- CICS/MVS will not be supported in the year 2000,
- Leap year calculation routine that does not recognize 2000 as a leap year.

So, you see, this standard requirement is mandatory! BE PREPARED! THE YEAR 2000 
IS NOT VERY FAR!!!

Regards and Good Luck,

Bao Tran
Bao_Tran @ nt.com

--------------------------------------
List-Post: [email protected]
Date: 3/14/97 10:30 AM
To: Bao Tran
From: Chris Olliffe/Wat/GB/Cray_Comm
   ----- E X T E R N A L L Y  O R I G I N A T E D  M E S S A G E -----

Reply to:   RE>TAA and Year 2000 Requirements?

Bob,

You recently posted a reply on this issue saying the following:-

>Year 2000 is coming. All product softwares must be compliant with
International Standard ISO >8601 "Data Elements and Interchange
Formats-Information Interchange Representation of >Dates and Times"

Could you tell me what reason you have for saying  "..must be compliant.." ?
This seems to infer a mandatory requirement.
I thought that ISO standards were voluntary.?

Has there been some notification regarding the compliance of this standard?

Any information would be gratefully received.

Many thanks

Chris Olliffe  (Case Technology  EMC Lab) http://www.case.co.uk

------------------ RFC822 Header Follows ------------------
Received: by nrchq1.rich1.nt.com with SMTP;14 Mar 1997 10:27:59 -0500
Received: from ruebert.ieee.org by ntigate.rich.nt.com with SMTP (PP);
          Fri, 14 Mar 1997 16:22:12 +0000
Received: (from daemon@localhost) by ruebert.ieee.org (8.7.5/8.7.3) id KAA06026
          for emc-pstc-list; Fri, 14 Mar 1997 10:38:16 -0500 (EST)
Message-Id: <9703142338.AA2417@gb_wat_nv01.anite.com>
To: emc-pstc <[email protected]>
From: Chris Olliffe/Wat/GB/Cray_Communications <[email protected]>
List-Post: [email protected]
Date: 14 Mar 97 15:38:16 GMT
Subject: Re: TAA and Year 2000 Requir
Mime-Version: 1.0
Content-Type: Text/Plain
Sender: [email protected]
Precedence: bulk
Reply-To: Chris Olliffe/Wat/GB/Cray_Communications <[email protected]>
X-Resent-To: Multiple Recipients <[email protected]>
X-Listname: emc-pstc
X-List-Description: Product Safety Tech. Committee, EMC Society
X-Info: Help requests to [email protected]
X-Info: [Un]Subscribe requests to [email protected]
X-Moderator-Address: [email protected]


Reply via email to