Silicon Investor (SI) -- The First Internet Community

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 : Discuss Year 2000 Issues -- Ignore unavailable to you. Want to Upgrade?

To: David Eddy who wrote (8566)	9/8/1999 10:22:00 AM
From: Cheeky Kid	Read Replies (1) \| Respond to of 9818

This about sums up my stance on Y too Kay: zdnet.com Great article. What business am I in, I keep that confidential.

To: David Eddy who wrote (8566)	9/8/1999 8:58:00 PM
From: flatsville	Read Replies (1) \| Respond to of 9818

David--I thought you might appreciate this courtesy of csy2k. (Sorry no deja.com url yet.) ------------------------------------------------------- On Wed, 8 Sep 1999 19:20:41, mjs@BCPO.NET (Mike Slaska) wrote: > Background: We have a test VSE machine that has had its date set forward, > currently it is set to 2/3/2000. When my programmers compile with > Intertest, the message, "CAIN8002 WARNING - Symbolic file date/time not > equal to load module date/time" > I am relatively sure that this problem is caused by the fact that my VSE and > VM have different system dates/times. What I need to know is if anyone else > has run into this problem, and, if so, how was it worked around? Waaait a minute. I thought everything was done, DONE, and we're all kicked back, playing Quake. Here's another guy who's unable to start testing. Lemme see, IBM is issuing a whole buncha PTFs on PUT 9906, PTFs labeled YR2000 and HIPER, the PUT comes out in August 1999. Suddenly in August 1999, the mainframe newsgroup comes alive with frantic cries for HALP! (You pointed out that, hey, mainframers seem cool and detached about Y2K but that was in June maybe.) We got Ken reporting that there haven't been a lot of COBOL job REQs posted. Help me out people, we got another mystery on our hands. System date bugs surface in July/August/September 1999 but everyone was done testing last year. Frantic cries for help start in August/September 1999 but everyone was done testing last year. Banks are done, right? They encountered all these generic Date problems a year or two ago. But why are the fixes showing up now? Why wasn't the newsgroup filled with cries for help last year or the year before? Why now? They're all done, aren't they? How does this work? Ooh-ooh, I know, I know, it's all a trick. Oh, and I still haven't found a report on the web about the SEC's August 31, 1999 requirement that all brokerages report 100% Y2K compliance. Come on people, let's find the "Great News." Maybe financial organizations don't "Get It" after all. <SNIP> cory hamasaki kiyoinc.com