I am posting this brief note, which was posted on Peter de Jager's forum on June 2. It speaks for itself. In order to keep the fellow from getting fired, I am not posting his name or his address.
What you read here is not typical -- not that many companies are as far along in the y2k repair as this one. Remember, we are not limiting our discussion to the United States. Every mainframe computer must be repaired, in every nation.
If you think this worldwide problem in coordination will be fixed, read this. When you read it, consider this: the White Paper of the State of California says that the inventory phase of the repair constitutes only 1% of the cost of the overall project. It should take one month.
* * * * * * * * * * * * * * * * *
Date: Mon, 02 Jun 1997 12:38:41 -0500 From: .... To: firstname.lastname@example.org Subject: re: Year 2000 Project Office
Currently, my company is in our impact assessment phase. My title is Year 2000 Project Manager but I currently manage only myself. We have an estimated 10.5 million LOC of COBOL running under OS/VS, 24 programmers in the programming dept., about 620 employees in the whole company, about 240 networked pc workstations. My efforts so far (with the assistance of a team of 10 others on the Y2K Task Force, assembled from various departments in the company) have been to conduct a non-COBOL software inventory, establish vendor and client databases for purposes of communications, business partner communications, internal communications and begin preliminary inventory of the COBOL source code using CA's Impact 2000 tool. The 10 working with me each have other full-time regular assignments within the company.