Y2K (Year 2000) Stocks: An Investment Discussion Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Y2K (Year 2000) Stocks: An Investment Discussion

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: David Eddy who wrote (6244)	9/15/1997 9:30:00 PM
From: Jeff Redman	of 13949

Most of our code is custom, COBOL, MVS. Our stores and distribution facilities run R/6000 AIX. IMR helped with the initial assessment, we found out that the fix was not as bad as we thought, about 10% of our code. Compuware came in later and increased the amount to 20%. Many of our new systems are in client/server, all new projects since the late 80's have been using DB2 with a date format of mm/dd/yyyy, our client/server data bases are Sybase. We looked at all our data base tables for 2 digit years, then temp & perm sequential files. Around 86 we changed our date subroutine to add a 4 digit year option. Many of our programs call this common module so the fix is in one place and we go into the programs that call this subroutine and change the arguments. Also, many of the programs with dates are report programs that put a date of mm/dd/yy in the header, these don't need to be changed. We have put 1999 and 2000 date test data into our data bases and then we are running our procs against the data to check the results. Our 2000 team is using "hourglass"? in the proc to make the job think it's 2000 when running the test.

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next