What a concept . . . holding senior management accountable!
Best regards,
*Jon Bathmaker,*
Senior z/OS Systems Programmer,
SYS1 Consulting Inc.
519-577-9661
On 1/3/2020 12:44 PM, Jesse 1 Robinson wrote:
On balance, we benefitted from the exercise. A lot of old--still
serviceable--hardware and software got upgraded just cuz. We could never have
budgeted this massive modernization drive just on principle. What gave the
industry impetus was the dark insinuation that if a company fell flat on its
face, the top level management could be held personally liable for malfeasance
and prosecuted. That was a major incentive for any company that might have
otherwise been inclined to coast through the millennial curtain with hands in
the air.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
[email protected]
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Matt Hogstrom
Sent: Friday, January 3, 2020 9:06 AM
To: [email protected]
Subject: (External):Re: [External] Re: FW: Re: it was 20 years ago today ....
I was changing jobs during that time and my previous employer paid me extra to
be on-site during the Y2K evening. Ended in a yawner.
However, there was a heck of a lot of money made in the tech industry upgrading
everything. Never let a good crisis go to waste seemed to be the reigning
philosophy.
Matt Hogstrom
PGP key 0F143BC1
On Jan 3, 2020, at 11:06, Pommier, Rex <[email protected]> wrote:
Yeah, there was a lot of hype and panic among the uninitiated/unaware. I
won't mention the place, but the company I was working for leading up to Y2K
required us to test coax-to-parallel protocol convertors that were running our
printers off 3174 controllers.
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On
Behalf Of Joel C. Ewing
Sent: Thursday, January 2, 2020 9:54 PM
To: [email protected]
Subject: [External] Re: FW: Re: it was 20 years ago today ....
Y2K concerns for a 3174 make no sense to anyone who has ever customized one.
There is no place while configuring a 3174 where you tell it local date-time
and no hardware support to sync it with any external time source. So if it
does have any kind of internal time awareness, there is zero reason to expect
it to be synced with anything related to actual date-time and no reason it
would choose to fail at a real world
1999/2000 year boundary it can't possibly know is happening.
Joel C Ewing
On 1/2/20 8:16 PM, Bill Dodge wrote:
We had users who were dependent on a 3174's connectivity that wanted us to verify that it
was Y2K compatibe. Totally in panic mode so several of us assembled around the 3174s
and shouted "Happy New Year". They never blinked.
---
Bill Dodge
On Fri, 3 Jan 2020 00:07:18 +0000, "Schuffenhauer, Mark" <[email protected]>
wrote:
I remember all the hype, it really freaked people out. I know people who quit
work, liquidated everything and went off grid. Many non-technical people were
very concerned it was the end. Minor non-y2k issues during the first few days
were blown out of proportion. Probably because of the scare tactics and
uncertainty the contracting companies used to get y2k work.
One wonders how much companies paid for y2k work that wasn't needed.
-----Original Message-----
From: IBM Mainframe Discussion List On Behalf Of Bill Dodge
Sent: Thursday, January 2, 2020 5:55 PM
To: [email protected]
Subject: Re: FW: Re: it was 20 years ago today ....
External Email
I was consulting at Arlington County, Virginia County Government. My whole
family was at a friend's house as was our tradition but I had to report to the
IT Department by 11:30 PM even though I had been running a virtual machine
whose date had been set to cross the threshold at least 10 times. We were gone
by 12:15.
---
Bill Dodge
On Thu, 2 Jan 2020 15:19:52 -0800, Tom Brennan wrote:
My oldest was just hitting 5 and couldn't reach the breaker box. But I was at work
anyway. I'm pretty sure everybody showed up, including the IT dept head. There was
basically nothing to do. Maybe about 15 minutes after midnight I was looking at a console
with a couple of managers behind me and I said "Uh oh", and wow... they were
all over me looking for any kind of problem, probably just to have something to report. I
think it was a date formatted wrong in a WTO or similar - nothing more. That might have
been the extent of the Y2K problems I remember seeing.
On 1/2/2020 2:52 PM, Phil Smith III wrote:
Hmm. I sent the post below, doesn't appear to have ever showed up, so retrying!
From: Phil Smith III
Sent: Tuesday, December 31, 2019 9:27 PM
To: [email protected]
Subject: Re: it was 20 years ago today ....
Has it been 20 years since Y2K?? sometimes it seems like last year, other times
seems like another lifetime .....
How many of us had smartass kids hanging out in the basement who, at 12:00:01,
threw the main breaker? I know I did!
Like many of you, I was on call that night, took the 2AM-10AM shift (at
Sterling Software). Around 5AM when it was clear nothing was happening, we got
sent home. I did get a nice sweatshirt out of it.
...
--
Joel C. Ewing
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
