Y2K (Year 2000) Background, Information and Compliance

Click here for your CTI Software Up-Grade Order Form


According to Jim Seymore (Consultant and Columnist - pictured at left), "Y2K will be the single biggest business crisis many of us will face in our lifetime." This maybe overstated, I don’t know, but since our software interfaces into mainframes all over the world, CTI has tested and updated its software for Year 2000 compliance. 
jesseberst.gif (3413 bytes)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

According to Jesse Berst, Editorial Director ZDNet AnchorDesk (February 27, 1998 - pictured at left), "It’s worse than you think. The Year 2000 (Y2K) bug, often seen as a problem only for unlucky mainframe programmers, actually holds dangers for the rest of us. How about this for starters: a) failed transportation systems, b) disruption of financial institutions, c) a government breakdown or even d) a devastating recession." Click here to obtain article.

11th Hour Y2K Cheat Sheet (December 29, 1999)


For the last 12 months I've warned you about Y2K. Tried to get you ready for the date change at work and at home. Attempted to separate the Chicken Little hysteria from the Y2K debunkers. (If you've missed any of this, go to Page 2 for a recap.)

Bottom line: I thought I'd pretty much said it all. Until the Team was talking earlier this week about holiday gatherings they'd been to. And how Y2K was the topic du jour. And Y2K naivete surprisingly rampant. So I asked them to help me put together a non-judgmental, super-simple, do-it-yourself Y2K compliance workbook. It starts with PC basics, followed by a New Year's Eve primer:

PC BASICS
The whole Y2K issue revolves around an old programming practice of saving space by using two digits to represent the year. Which means there are four things you should worry about as the calendar turns to 00:

BIOS. In a nutshell, this is software that sets a PC's internal clock. If you have a Windows PC purchased in the last two years, you should have Y2K-compliant BIOS. PCs made in 1996 and 1997 are a crapshoot. And those made before '96 likely have non-Y2K-compliant BIOS. The ZDNet Help site recommends a free tool that will both check your BIOS and automatically apply fixes as needed.

Applications. Some older software simply can't handle Y2K and never will; some can be updated. Any software purchased in the last two years should already be Y2K-compliant. But you need to know for sure. Your first click should be to the manufacturer's Web site. Microsoft, for instance, has a Y2K portal where you'll find extensive resources. The ZDY2K site has numerous direct links to software and hardware companies' Y2K info.

Dated files. Spreadsheet or database program files that use two-digits to indicate the year could cause problems. It may be time consuming, but you will rest easier if you go through and change them to four digits.

Y2K viruses. Beyond the Year 2000 bug itself, there's concern virus writers and malicious hackers will find the millennium change a tempting time to wreak havoc. If you don't have anti-virus software, get it and install it now.  If you do, be sure to grab any necessary updates as events dictate.

NEW YEAR'S EVE PRIMER
For those of you who took care of computer-related Y2K issues long ago, I asked the AnchorDesk crew for other ways to prepare for the New Year and New Millennium. Here's what they came up with:

Executive Producer Liz Enbysk. A banker friend told her he's going to take out $1,000 in cash -- just in case. He's not worried about banks being Y2K-ready, but has concerns about getting goods and services from all the small businesses who say they're taking a wait-and-see attitude about Y2K. Our resident Mom figures a little extra cash, a full tank of gas and some auxiliary water jugs, batteries and candles can't hurt.

Managing Editor Nicci Noteboom. Seattle's mayor canceled the annual New Year's Eve hoopla at the Space Needle over concerns it would be a target for terrorists. But our resident party girl will not be deterred. Her advice for like-minded revelers: Have enough money for a martini and cab fare home. And wear comfortable shoes.

Associate Editor Neil Strother. When last heard from, Neil had packed up the family and was driving his Suburban toward Montana. But no, Mr. Sunshine hasn't adopted a Doomsday mentality. He's hot tubbing and skiing away his last vacation of the millennium.

Associate Editor Chris Albrecht. Our trendy, always-looking-to-the-future guy isn't wasting a lot of brain share on Y2K. He's already talking about what's next, what bugs are on the horizon, how we're going to put the date change behind us and move on.

Now I promise: That's the last you'll hear from me about Y2K. At least this millennium. Now it's your turn. Use the TalkBack button to tell me if you are more -- or less -- worried about Y2K problems the closer we get to Jan. 1. You can also talk it over with other readers in my Berst Alerts forum.  

donwillmott.gif (3103 bytes) According to Don Willmott, Executive Editor,  PC Magazine Online, (May 21, 1998 - pictured at left), "It will certainly be exciting to arrive at 2001, but we have to pass through 2000 to get there. And no one is truly certain about just how damaging the “Year 2000 Crisis” is going to be." Click here to obtain article.
U.S. GOV'T WARNING: SMALL BUSINESSES AT BIG RISK FROM Y2K
If you run a small business -- that is, with revenue under $50 million a year -- the U.S. Small Business Administration is worried about you.  According to the San Francisco Chronicle, the agency was prompted to issue a special warning after a recent Gallup Poll survey indicated 82% of small businesses are at risk from the so-called Year 2000, or millennium, bug.  Worse, 75% of small-business owners have taken no steps to make sure their computers won't mistake the year 2000 for the year 1900.   The agency warns that 330,000 of the estimated 23 million small businesses are at risk of closing down as a result of Y2K, and another 370,000 could be temporarily or permanently hobbled.  All this is expected to lead to service shutdowns, shipment problems and job losses.  To avoid becoming an unpleasant statistic, get your shop in order now. ZDNet's Y2K resource is a smart place to start.
Gary North Y2K Opinions from Gary North.  Click here.

What is this year 2000 issue? On January 1, 2000, many of the world's computers, most of which were programmed to read years as two-digit numbers, will suddenly be confounded by a figure, 00, that could mean either 2000 or 1900.  Companies all over the world are spending billions trying to solve the problem.  According to a recent article, Chase Manhattan Bank is expected to spend up to $250 million to address the problem; the federal government will reportedly shell out $3.8 billion.

CTI Compliance

In the case of CTI's 3780 protocol product, Version 3.5 (Release 02218 and later) has been tested and meets Y2K compliance.   Further, it has been tested and approved by one of the largest financial software houses in the U.S. who uses our product in the market.

In the case of CTI's TCP/IP based Electronic Hub Mailbox Systems, we have tested, up-dated and approved both the TCP/IP System (through the CTI-VAN serving a number of companies) and the 3780 based Mailbox System (at one key OEM site having over 100 users)

For CTI's Corporate Statement of Y2K Compliance -> Click here.

YEAR 2000 FREQUENTLY ASKED QUESTIONS

Can PC-based applications have problems when we reach the year 2000? Answers to this and the other  frequently asked questions:

 


Feds set up Y2K hot line
WASHINGTON - Consumers fretting about how they will fly come January 2000 or whether their Social Security checks will arrive on time now have a new resource for addressing their millennium woes. The President's Council on Year 2000 on Thursday announced the creation of the toll-free hot line to answer Y2K questions. By dialing 1-888-USA-4-Y2K, consumers can access prerecorded messages seven days a week, 24 hours a day on how personal computers, telephones and other products or services will be affected.

Sterling Software (Dallas, TX) is now shipping a new Y2K product fix called "Vision Phaseshift" that is supposed to fix the Y2K problems on MVS applications.  Vision Phaseshift runs as a utility between the application itself and the operating system.  

Pricing starts at only $275,000 


3Com Provides a Networking Hotline for Y2K

Many computer and telecommunications products have some kind of time or date oriented mechanism within their architecture.  This mechanism may be designed as part of the product’s hardware or internal software.   Sometimes the year portion of the date is represented only by the last two digits instead of the entire four digits.  Consequently, when January 1, 2000 arrives, some products - though not all - may see this change as a move backwards in time to the year 1900 instead of forward in time to the year 2000, and various problems may unfold as a result.  This situation has become known as the "Year 2000 Problem" or the "Millennium Problem." 3 Com has developed a Web Site for the Year 2000 situation.  There are six different links for information regarding the following:   Product Status Listing; Warranty Statement; Testing Statement; Look up by 3C number; FAQ; and Palm Computing.


The Issue according to the ITAA (Information Technology Association of America):   In order to save space and speed processing, most computer systems have been set up to identify calendar dates with only the last two digits of the year. Without software conversion, the vast majority of computer systems will not be able to recognize "00" as the Year 2000. When these systems are unable to recognize this two-digit year field correctly - programs will fail, or, at the very least, will fail to operate properly.

The dimensions of Year 2000 Software Conversion are enormous, and should be of substantial concern to executives in both business and government. This situation will affect computations which calculate age, sort by date, compare dates, or perform other specialized tasks. At $450 to $600 per affected computer program, the Gartner Group has estimated that a medium-sized company will spend between $3.6-$4.2 million to convert its software. The cost-per-line-of-code has been estimated between $1.00-$1.50. Viasoft estimates cost-per-impacted-program between $572-$1,204. This is a problem that exists for mainframe, midrange and PC computers alike. The two-digit-year-field can be found in microcode, operating systems, software compilers, applications, queries, procedures, screens, data bases, and data.

Estimates place correcting the problem for businesses and the public sector in the United States alone between $100-$200 billion. If you accept the premise that the total information technology services marketplace in America approaches $150 billion annually; that means Year 2000 Software Conversion could represent anywhere from 33%-50% of dollars spent for information systems in one year. Some ITAA Year 2000 Task Group members report estimates placing the worldwide total to correct the problem between $300 and $600 billion.


Y2K RTC (Real-Time Clock) Cycle Test
  1. Make a full system backup.  Disconnect the PC from all other systems and networks.
  2. Modify the system date to December 31, 1999.
  3. Modify the system time to 11:58 P.M.
  4. Display the system date and time to make sure they are set correctly.
  5. Turn the computer off.
  6. Wait 3 minutes to 5 minutes so the RTC can cycle into January 1, 2000.
  7. Turn the computer back on.
  8. Check the system date and time.  They should read a few minutes after midnight, January 1, 2000.  If they don't, make note of the date and time displayed - these are valuable clues to the kind of date problem you have.
  9. Reset the system to the current date and time before rebooting.
Y2K RTC (Real-Time Clock) Set Test
  1. Make a full system backup.  Disconnect the PC from all other systems and networks.
  2. Modify the system date to January 1, 2000.
  3. Display the system date to be sure it is set correctly.
  4. Turn the computer off.
  5. Wait 1 minute so the RTC can cycle.
  6. Turn the computer back on.
  7. Check the system date and time.  They should read a few minutes after midnight, January 1, 2000.  If they don't, make note of the date and time displayed - these are valuable clues to the kind of date problem you have.
  8. Reset the system to the current date before you reboot.

Up-grade Costs

Click here for an Order Form for your up-grade.