Re: it was 20 years ago today ....

[Seymour J Metz]

I don't agree that COVID-19 is more far reaching; if, e.g., the financial 
institutions, railroads, did not ultimately address their Y2K issues, it would 
have been grim. Likewise manufacturing relying on JIT inventory. But I was 
never concerned with, e.g., power generation, heavy manufacturing.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Jesse 1 Robinson [jesse1.robin...@sce.com]
Sent: Saturday, May 2, 2020 2:57 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

(Old post) I don't have any citations, but some of the most notorious doomsters 
recanted their gloomy predictions well BEFORE January 2000. They presumably 
sold a lot of $19.99 books in the meantime. I doubt that Tom received an offer 
of refund. So how did we dodge the Y2K asteroid? I can testify from personal 
witness that we worked our *sses off and coincidentally spent tons of money. 
Catastrophe did not just happen to miss us. We took heroic evasive maneuvers.

Fast forward to today. We're currently mired in a crisis even farther-reaching 
than Y2K. The question is increasingly asked: what will the 'new normal' look 
like once we're back to whatever? No predictions from me, but we can observe 
some changes in pre-2000 IT. A lot of the aforementioned Y2K spend was directed 
at and justified by replacing old hardware and software. I joined SCE in 1994. 
By early in the new century, not a single piece of mainframe hardware on the 
floor in the md-90s remained in use. All replaced by more modern gear or in 
some cases by changes in the way we did business. These changes were 
accomplished not so much by futuristic strategic planning as by the looming 
threat of jail time for corporate executives who failed to board the boat. 
Coercion at its sweetest.

.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Tom 
Brennan
Sent: Thursday, January 2, 2020 6:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: it was 20 years ago today 

 > In the 90s Stewart Alsop famously predicted the end of the world.

I just checked my old book collection and found "Time Bomb 2000" by Edward and 
Jennifer Yourdon.  On the back it has questions like, Will your car run?, Will 
there be food?, Will your PC work? ...  Yep, I fell for it.  Marked $19.99 - I 
hope I got a really good discount.

On 1/2/2020 4:18 PM, Jesse 1 Robinson wrote:
> I heard a 'Y2K person' interviewed on NPR recently. Her point was that if the 
> IT industry had done nothing in advance to remediate, we would have had utter 
> chaos on 1/1/2000. But we did prepare. We undoubtedly overprepared, but by 
> how much will forever remain a mystery.
>
> In the 90s Stewart Alsop famously predicted the end of the world. He 
> retreated well before the event itself. We all buy insurance that we're 
> thrilled not to utilize. That doesn't make it a waste.
>
> .
> .
> 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
> robin...@sce.com


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Jesse 1 Robinson]

(Old post) I don't have any citations, but some of the most notorious doomsters 
recanted their gloomy predictions well BEFORE January 2000. They presumably 
sold a lot of $19.99 books in the meantime. I doubt that Tom received an offer 
of refund. So how did we dodge the Y2K asteroid? I can testify from personal 
witness that we worked our *sses off and coincidentally spent tons of money. 
Catastrophe did not just happen to miss us. We took heroic evasive maneuvers.  

Fast forward to today. We're currently mired in a crisis even farther-reaching 
than Y2K. The question is increasingly asked: what will the 'new normal' look 
like once we're back to whatever? No predictions from me, but we can observe 
some changes in pre-2000 IT. A lot of the aforementioned Y2K spend was directed 
at and justified by replacing old hardware and software. I joined SCE in 1994. 
By early in the new century, not a single piece of mainframe hardware on the 
floor in the md-90s remained in use. All replaced by more modern gear or in 
some cases by changes in the way we did business. These changes were 
accomplished not so much by futuristic strategic planning as by the looming 
threat of jail time for corporate executives who failed to board the boat. 
Coercion at its sweetest. 

.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Tom 
Brennan
Sent: Thursday, January 2, 2020 6:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: it was 20 years ago today 

 > In the 90s Stewart Alsop famously predicted the end of the world.

I just checked my old book collection and found "Time Bomb 2000" by Edward and 
Jennifer Yourdon.  On the back it has questions like, Will your car run?, Will 
there be food?, Will your PC work? ...  Yep, I fell for it.  Marked $19.99 - I 
hope I got a really good discount.

On 1/2/2020 4:18 PM, Jesse 1 Robinson wrote:
> I heard a 'Y2K person' interviewed on NPR recently. Her point was that if the 
> IT industry had done nothing in advance to remediate, we would have had utter 
> chaos on 1/1/2000. But we did prepare. We undoubtedly overprepared, but by 
> how much will forever remain a mystery.
> 
> In the 90s Stewart Alsop famously predicted the end of the world. He 
> retreated well before the event itself. We all buy insurance that we're 
> thrilled not to utilize. That doesn't make it a waste.
> 
> .
> .
> 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
> robin...@sce.com


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Jeremy Nicoll]

On Thu, 9 Jan 2020, at 17:04, Charles Mills wrote:
> I am not an applications guy, and I didn't do any applications Y2K 
> remediation, so I am not an expert, but it would seem to me that if I 
> had used windowing I would have based the window on the current date -- 
> today minus 80 years or something like that -- so that it would never 
> fail (in this way -- of course, software has many ways to fail). It 
> would work as well in 2040 as it did in 2000.

You're oversimplifying though.  In a particular application there may be 
many dates - eg a customer's birth date, marriage date, retiral date and 
- say - the future date on which some contractual thing will mature.

Thye'd likely all have different windows.

-- 
Jeremy Nicoll - my opinions are my own.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Joel C. Ewing]

It all depends on where you use the windowing.   If for terseness on  
data entry for internal conversion to 4-digit years and retention as 
4-digit years, then a floating window relative in some way to current 
year is the obvious and only rational choice.


If you elected to retain the date as a 2-digit year in external files or 
data-base records and must be able to continue to read the data, then a 
floating window is not an option for externally saved dates:  the 
windowing base-year choice is implicitly fixed by assumptions at 
creation once you store a date in 2-digit year format.


If you made your applications smart enough to associate or "compute" 
(based on a 4-digit year stored somewhere) a 4-digit base year to use 
for windowing with each data set or data base record containing 2-digit 
years, I guess you could make make historical 2-digit year dates work 
indefinitely with both new and  historical data; but that sounds like 
something that would be much more difficult to maintain without error 
and more costly in the long run than just changing external data formats 
and storing 4-digit years. Otherwise, virtually every time you needed 
to  process a two-digit year in historic data, you would first need to 
pre-process the date field to determine the appropriate window base-year 
and to expand to a 4-digit year.


z/OS  applications should be basing time-related decisions using 
time/date formats with 4-digit years, and not relying on internal binary 
clock formats.  At least at our installation during Y2K mitigation there 
was no application programmer code dependency on the hardware TOD clock 
for date determination, and I would think that would be more the rule 
than an exception.   I wouldn't expect much of a ripple from the z/OS 
hardware clock wrap, because for the most part only z/OS itself and some 
IBM subsystems need to be able to deal with it -- not an issue unless 
you plan to be running on a severely back-level unsupported version of 
z/OS at the time of the wrap.   I can't speak for Unix/Linux application 
conventions.

    JC Ewing

On 1/9/20 11:04 AM, Charles Mills wrote:

I am not an applications guy, and I didn't do any applications Y2K remediation, 
so I am not an expert, but it would seem to me that if I had used windowing I 
would have based the window on the current date -- today minus 80 years or 
something like that -- so that it would never fail (in this way -- of course, 
software has many ways to fail). It would work as well in 2040 as it did in 
2000.

Don't forget we've got another one of these coming up in 2042, and for people 
using UNIX times, one in 2038. 2042 does not seem so far away as it once did.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Joel C. Ewing
Sent: Thursday, January 9, 2020 8:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

I always preferred to describe a 100-year windowed two-digit year
representation by its lowest or "base" year, in this case 1920 -- just
easier for me to visualize the 100 continguous years of validity on a
timeline..

One would hope those who chose the fixed-windowing temporary solution to
Y2K described in this article were honest enough to call 2020 the
"Failure Year" and not some nice euphemism like "Pivot Year" that would
sound less threatening to management with marginal tech skills.
  JC Ewing

On 1/9/20 9:14 AM, Charles Mills wrote:

https://www.zdnet.com/article/the-y2k-bug-is-back-causing-headaches-for-developers-again/?ftag=TRE-03-10aaa6b=21203266192019599533914397741980

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
Joel C. Ewing

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Charles Mills]

I am not an applications guy, and I didn't do any applications Y2K remediation, 
so I am not an expert, but it would seem to me that if I had used windowing I 
would have based the window on the current date -- today minus 80 years or 
something like that -- so that it would never fail (in this way -- of course, 
software has many ways to fail). It would work as well in 2040 as it did in 
2000.

Don't forget we've got another one of these coming up in 2042, and for people 
using UNIX times, one in 2038. 2042 does not seem so far away as it once did.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Joel C. Ewing
Sent: Thursday, January 9, 2020 8:37 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

I always preferred to describe a 100-year windowed two-digit year 
representation by its lowest or "base" year, in this case 1920 -- just 
easier for me to visualize the 100 continguous years of validity on a  
timeline..

One would hope those who chose the fixed-windowing temporary solution to 
Y2K described in this article were honest enough to call 2020 the 
"Failure Year" and not some nice euphemism like "Pivot Year" that would 
sound less threatening to management with marginal tech skills.
 JC Ewing

On 1/9/20 9:14 AM, Charles Mills wrote:
> https://www.zdnet.com/article/the-y2k-bug-is-back-causing-headaches-for-developers-again/?ftag=TRE-03-10aaa6b=21203266192019599533914397741980

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Joel C. Ewing]

I always preferred to describe a 100-year windowed two-digit year 
representation by its lowest or "base" year, in this case 1920 -- just 
easier for me to visualize the 100 continguous years of validity on a  
timeline..


One would hope those who chose the fixed-windowing temporary solution to 
Y2K described in this article were honest enough to call 2020 the 
"Failure Year" and not some nice euphemism like "Pivot Year" that would 
sound less threatening to management with marginal tech skills.

    JC Ewing

On 1/9/20 9:14 AM, Charles Mills wrote:

https://www.zdnet.com/article/the-y2k-bug-is-back-causing-headaches-for-developers-again/?ftag=TRE-03-10aaa6b=21203266192019599533914397741980

Charles

...



--
Joel C. Ewing

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Charles Mills]

https://www.zdnet.com/article/the-y2k-bug-is-back-causing-headaches-for-developers-again/?ftag=TRE-03-10aaa6b=21203266192019599533914397741980
 

Charles

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Mark Jacobs]

Re:Mayor,It would have to had been Rudy Giuliani since he was mayor on 9/11.

Mark Jacobs

Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com

‐‐‐ Original Message ‐‐‐
On Wednesday, January 8, 2020 11:52 AM, scott Ford  wrote:

> Guys I was working in NYC at that time consulting for a lot of city
> agencies. I was doing a channel extension Y2K project for a Brokerage House.
> I dont remember who was mayor, but I do remember the panic around what
> hardware and software are effected by Y2K. It was a zoo..lol
>
> Scott
>
> On Fri, Jan 3, 2020 at 4:23 PM Charles Mills charl...@mcn.org wrote:
>
> > Quite seriously, people who lived in NYC during his tenure have more
> > nuanced recollections than either of the below.
> > Charles
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of Savor, Thomas (Alpharetta)
> > Sent: Friday, January 3, 2020 11:53 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: it was 20 years ago today 
> > You mean the Mayor that killed corruption and the Mafia in Nyc...that
> > idiot ??
> > Thanks,
> > Tom Savor
> > -Original Message-
> > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf
> > Of Barkow, Eileen
> > Sent: Friday, January 3, 2020 1:56 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: it was 20 years ago today 
> > ⚠ EXTERNAL MESSAGE – Think Before You Click
> > The current and past idiot Rudolph Guilianni
> >
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
>
> *IDMWORKS *
>
> Scott Ford
>
> z/OS Dev.
>
> “By elevating a friend or Collegue you elevate yourself, by demeaning a
> friend or collegue you demean yourself”
>
> www.idmworks.com
>
> scott.f...@idmworks.com
>
> Blog: www.idmworks.com/blog
>
> The information contained in this email message and any attachment may be
> privileged, confidential, proprietary or otherwise protected from
> disclosure. If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination, distribution, copying or
> use of this message and any attachment is strictly prohibited. If you have
> received this message in error, please notify us immediately by replying to
> the message and permanently delete it from your computer and destroy any
> printout thereof.
> --
>
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[scott Ford]

Guys I was working in NYC at that time consulting for a lot of city
agencies. I was doing a channel extension Y2K project for a Brokerage House.
I dont remember who was mayor, but I do remember the panic around what
hardware and software are effected by Y2K. It was a zoo..lol

Scott

On Fri, Jan 3, 2020 at 4:23 PM Charles Mills  wrote:

> Quite seriously, people who lived in NYC during his tenure have more
> nuanced recollections than either of the below.
>
> Charles
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Savor, Thomas (Alpharetta)
> Sent: Friday, January 3, 2020 11:53 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today 
>
> You mean the Mayor that killed corruption and the Mafia in Nyc...that
> idiot ??
>
> Thanks,
>
> Tom Savor
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf
> Of Barkow, Eileen
> Sent: Friday, January 3, 2020 1:56 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today 
>
>   ⚠ EXTERNAL MESSAGE – Think Before You Click
>
>
>
> The current and past idiot Rudolph  Guilianni
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 



*IDMWORKS *

Scott Ford

z/OS Dev.




“By elevating a friend or Collegue you elevate yourself, by demeaning a
friend or collegue you demean yourself”



www.idmworks.com

scott.f...@idmworks.com

Blog: www.idmworks.com/blog





*The information contained in this email message and any attachment may be
privileged, confidential, proprietary or otherwise protected from
disclosure. If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination, distribution, copying or
use of this message and any attachment is strictly prohibited. If you have
received this message in error, please notify us immediately by replying to
the message and permanently delete it from your computer and destroy any
printout thereof.*

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Tom Brennan]

LOL
That would certainly do it!  But it's not very fast since I would have 
to get up from my comfy chair.


On 1/5/2020 11:03 AM, Lennie Dymoke-Bradshaw wrote:

I think the most secure answer to the first question is to turn the power off.

Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd
Web:  www.rsmpartners.com
‘Dance like no one is watching. Encrypt like everyone is.’

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: 05 January 2020 18:25
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] it was 20 years ago today

I think we should stick with this list for as long as possible.

1) What is the absolute best way to clear a register?
2) Exactly how many cycles does it take to do an LA instruction?
3) Is EBCDIC really that bad?

4) Funky late-night experiences with data cells, optical readers and long-gone 
software
5) Why IBM's implementation of Posix time zones is flawed
6) Is JCL really that bad?

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Brennan
Sent: Friday, January 3, 2020 12:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

We probably should change the subject.  Some suggestions:


.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Don 
Leahy
Sent: Saturday, January 4, 2020 10:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: it was 20 years ago today

I was working on contract with a major bank during the run up to Y2K.
  The bank was so confident that they had the issue licked that they laid
off all of the contractors in November.   I found another contract
immediately, but my new shop also had things well in hand, so I ended up 
partying that night.  Neither shop had any significant issues during the 
century change.

On Fri, Jan 3, 2020 at 13:23 Gabe Goldberg  wrote:


Just came across:  ‘Here We Go. The Chaos Is Starting’: An Oral
History of Y2K

https://www.popularmechanics.com/technology/security/a30338692/y2k-pan
ic/

I still have about half the Y2K books I bought, figure they'll go with
the next Great Purge. Circa 1995 I thought of doing "The Y2K Handbook"
(like "The REXX Handbook" and two VM/ESA handbooks co-edited with Phil
Smith) but never got around to it. Likely for the best, considering
the tsunami of books published.

--
Gabriel Goldberg, Computers and Publishing, Inc.   g...@gabegold.com
3401 Silver Maple Place, Falls Church, VA 22042
<https://www.google.com/maps/search/3401+Silver+Maple+Place,+Falls+Church,+VA+22042?entry=gmail=g>
  (703) 204-0433
LinkedIn: http://www.linkedin.com/in/gabegoldTwitter: GabeG0



--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Lennie Dymoke-Bradshaw]

I think the most secure answer to the first question is to turn the power off.

Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd  
Web:  www.rsmpartners.com
‘Dance like no one is watching. Encrypt like everyone is.’

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: 05 January 2020 18:25
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] it was 20 years ago today

I think we should stick with this list for as long as possible. 

1) What is the absolute best way to clear a register?  
2) Exactly how many cycles does it take to do an LA instruction?  
3) Is EBCDIC really that bad?  

4) Funky late-night experiences with data cells, optical readers and long-gone 
software
5) Why IBM's implementation of Posix time zones is flawed
6) Is JCL really that bad?  

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Brennan
Sent: Friday, January 3, 2020 12:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

We probably should change the subject.  Some suggestions:


.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Don 
Leahy
Sent: Saturday, January 4, 2020 10:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: it was 20 years ago today

I was working on contract with a major bank during the run up to Y2K.
 The bank was so confident that they had the issue licked that they laid
off all of the contractors in November.   I found another contract
immediately, but my new shop also had things well in hand, so I ended up 
partying that night.  Neither shop had any significant issues during the 
century change.

On Fri, Jan 3, 2020 at 13:23 Gabe Goldberg  wrote:

> Just came across:  ‘Here We Go. The Chaos Is Starting’: An Oral 
> History of Y2K
>
> https://www.popularmechanics.com/technology/security/a30338692/y2k-pan
> ic/
>
> I still have about half the Y2K books I bought, figure they'll go with 
> the next Great Purge. Circa 1995 I thought of doing "The Y2K Handbook"
> (like "The REXX Handbook" and two VM/ESA handbooks co-edited with Phil
> Smith) but never got around to it. Likely for the best, considering 
> the tsunami of books published.
>
> --
> Gabriel Goldberg, Computers and Publishing, Inc.   g...@gabegold.com
> 3401 Silver Maple Place, Falls Church, VA 22042 
> <https://www.google.com/maps/search/3401+Silver+Maple+Place,+Falls+Church,+VA+22042?entry=gmail=g>
>  (703) 204-0433
> LinkedIn: http://www.linkedin.com/in/gabegoldTwitter: GabeG0


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Jesse 1 Robinson]

I think we should stick with this list for as long as possible. 

1) What is the absolute best way to clear a register?  
2) Exactly how many cycles does it take to do an LA instruction?  
3) Is EBCDIC really that bad?  

4) Funky late-night experiences with data cells, optical readers and long-gone 
software  
5) Why IBM's implementation of Posix time zones is flawed  
6) Is JCL really that bad?  

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Brennan
Sent: Friday, January 3, 2020 12:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

We probably should change the subject.  Some suggestions:


.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Don 
Leahy
Sent: Saturday, January 4, 2020 10:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: it was 20 years ago today

I was working on contract with a major bank during the run up to Y2K.
 The bank was so confident that they had the issue licked that they laid
off all of the contractors in November.   I found another contract
immediately, but my new shop also had things well in hand, so I ended up 
partying that night.  Neither shop had any significant issues during the 
century change.

On Fri, Jan 3, 2020 at 13:23 Gabe Goldberg  wrote:

> Just came across:  ‘Here We Go. The Chaos Is Starting’: An Oral 
> History of Y2K
>
> https://www.popularmechanics.com/technology/security/a30338692/y2k-pan
> ic/
>
> I still have about half the Y2K books I bought, figure they'll go with 
> the next Great Purge. Circa 1995 I thought of doing "The Y2K Handbook"
> (like "The REXX Handbook" and two VM/ESA handbooks co-edited with Phil
> Smith) but never got around to it. Likely for the best, considering 
> the tsunami of books published.
>
> --
> Gabriel Goldberg, Computers and Publishing, Inc.   g...@gabegold.com
> 3401 Silver Maple Place, Falls Church, VA 22042 
> <https://www.google.com/maps/search/3401+Silver+Maple+Place,+Falls+Church,+VA+22042?entry=gmail=g>
>  (703) 204-0433
> LinkedIn: http://www.linkedin.com/in/gabegoldTwitter: GabeG0


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Gabe Goldberg]

And this mess:

https://www.nytimes.com/interactive/2019/12/23/style/y2k-bug-millennials.html

On 1/3/2020 1:23 PM, Gabe Goldberg wrote:
Just came across:  ‘Here We Go. The Chaos Is Starting’: An Oral 
History of Y2K


https://www.popularmechanics.com/technology/security/a30338692/y2k-panic/

I still have about half the Y2K books I bought, figure they'll go with 
the next Great Purge. Circa 1995 I thought of doing "The Y2K Handbook" 
(like "The REXX Handbook" and two VM/ESA handbooks co-edited with Phil 
Smith) but never got around to it. Likely for the best, considering 
the tsunami of books published.



--
Gabriel Goldberg, Computers and Publishing, Inc.   g...@gabegold.com
3401 Silver Maple Place, Falls Church, VA 22042   (703) 204-0433
LinkedIn: http://www.linkedin.com/in/gabegoldTwitter: GabeG0

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Don Leahy]

I was working on contract with a major bank during the run up to Y2K.
 The bank was so confident that they had the issue licked that they laid
off all of the contractors in November.   I found another contract
immediately, but my new shop also had things well in hand, so I ended up
partying that night.  Neither shop had any significant issues during the
century change.

On Fri, Jan 3, 2020 at 13:23 Gabe Goldberg  wrote:

> Just came across:  ‘Here We Go. The Chaos Is Starting’: An Oral History
> of Y2K
>
> https://www.popularmechanics.com/technology/security/a30338692/y2k-panic/
>
> I still have about half the Y2K books I bought, figure they'll go with
> the next Great Purge. Circa 1995 I thought of doing "The Y2K Handbook"
> (like "The REXX Handbook" and two VM/ESA handbooks co-edited with Phil
> Smith) but never got around to it. Likely for the best, considering the
> tsunami of books published.
>
> --
> Gabriel Goldberg, Computers and Publishing, Inc.   g...@gabegold.com
> 3401 Silver Maple Place, Falls Church, VA 22042
> 
>  (703) 204-0433
> LinkedIn: http://www.linkedin.com/in/gabegoldTwitter: GabeG0
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Charles Mills]

Quite seriously, people who lived in NYC during his tenure have more nuanced 
recollections than either of the below.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Savor, Thomas (Alpharetta)
Sent: Friday, January 3, 2020 11:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

You mean the Mayor that killed corruption and the Mafia in Nyc...that idiot ?? 

Thanks,

Tom Savor
-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Barkow, Eileen
Sent: Friday, January 3, 2020 1:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

  ⚠ EXTERNAL MESSAGE – Think Before You Click



The current and past idiot Rudolph  Guilianni

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Charles Mills]

4) Funky late-night experiences with data cells, optical readers and long-gone 
software
5) Why IBM's implementation of Posix time zones is flawed
6) Is JCL really that bad?

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Brennan
Sent: Friday, January 3, 2020 12:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

We probably should change the subject.  Some suggestions:

1) What is the absolute best way to clear a register?
2) Exactly how many cycles does it take to do an LA instruction?
3) Is EBCDIC really that bad?

On 1/3/2020 12:04 PM, Mike Schwab wrote:
> Was holding the primary for his replacement on 9/11/2001, that had to
> be postponed.
> 
> On Fri, Jan 3, 2020 at 1:53 PM Savor, Thomas (Alpharetta)
>  wrote:
>>
>> You mean the Mayor that killed corruption and the Mafia in Nyc...that idiot 
>> ??
>>
>> Thanks,
>>
>> Tom Savor
>> -Original Message-
>> From: IBM Mainframe Discussion List  On Behalf Of 
>> Barkow, Eileen
>> Sent: Friday, January 3, 2020 1:56 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: it was 20 years ago today 
>>
>>⚠ EXTERNAL MESSAGE – Think Before You Click
>>
>>
>>
>> The current and past idiot Rudolph  Guilianni
>>
>> -Original Message-
>> From: IBM Mainframe Discussion List  On Behalf Of 
>> Jesse 1 Robinson
>> Sent: Friday, January 3, 2020 1:24 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: it was 20 years ago today 
>>
>> OK, bonus homework question: who was mayor of New York City in Jan 1, 2000?
>>
>> .
>> .
>> 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
>> robin...@sce.com
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> 
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [External] Re: FW: Re: it was 20 years ago today ....

[zMan]

OK, not actually Y2K, just "stupid date handling". I wondered, since 20
years ago meters didn't take cards!

On Fri, Jan 3, 2020 at 11:38 AM Barkow, Eileen 
wrote:

> Would you believe that there is still fallout from Y2K. NYC parking meters
> could not accept credit cards because of it.
>
>
>
>
> https://www.ny1.com/nyc/all-boroughs/news/2020/01/03/software-glitch-knocks-out-credit-card-payments-at-nyc-parking-meter
>
>
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf
> Of Seymour J Metz
> Sent: Friday, January 3, 2020 11:26 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [External] Re: FW: Re: it was 20 years ago today 
>
>
>
> There were date dependencies in a lot of unexpected places, although some
> of them were of minor importance. There was no more reason to believe that
> everything was under control than there was to believe in the inevitability
> of disaster. Hidden among the hype were some plausible concerns. Frankly,
> we lucked out.
>
>
>
>
>
> --
>
> Shmuel (Seymour J.) Metz
>
>
> https://gcc02.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.gmu.edu%2F~smetz3data=02%7C01%7Cebarkow%40doitt.nyc.gov%7C668247219a474d4f929208d79069ad4c%7C73d61799c28440228d4154cc4f1929ef%7C0%7C0%7C637136655989197748sdata=fffL9bJBCNMoJYgF%2F2NSwhyJc29Tajp370CzvdEm%2Bmk%3Dreserved=0
>
>
>
>
>
> 
>
> From: IBM Mainframe Discussion List  IBM-MAIN@LISTSERV.UA.EDU>> on behalf of Pommier, Rex <
> rpomm...@sfgmembers.com<mailto:rpomm...@sfgmembers.com>>
>
> Sent: Friday, January 3, 2020 11:06 AM
>
> To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
>
> Subject: Re: [External] Re: FW: Re: it was 20 years ago today 
>
>
>
> 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  IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Joel C. Ewing
>
> Sent: Thursday, January 2, 2020 9:54 PM
>
> To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
>
> 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 +, "Schuffenhauer, Mark" <
> mschu...@tcfbank.com<mailto:mschu...@tcfbank.com>> 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: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>
>
> > 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 th

Re: it was 20 years ago today ....

[Tom Brennan]

We probably should change the subject.  Some suggestions:

1) What is the absolute best way to clear a register?
2) Exactly how many cycles does it take to do an LA instruction?
3) Is EBCDIC really that bad?

On 1/3/2020 12:04 PM, Mike Schwab wrote:

Was holding the primary for his replacement on 9/11/2001, that had to
be postponed.

On Fri, Jan 3, 2020 at 1:53 PM Savor, Thomas (Alpharetta)
 wrote:


You mean the Mayor that killed corruption and the Mafia in Nyc...that idiot ??

Thanks,

Tom Savor
-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Barkow, Eileen
Sent: Friday, January 3, 2020 1:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

   ⚠ EXTERNAL MESSAGE – Think Before You Click



The current and past idiot Rudolph  Guilianni

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: Friday, January 3, 2020 1:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

OK, bonus homework question: who was mayor of New York City in Jan 1, 2000?

.
.
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
robin...@sce.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN






--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Mike Schwab]

Was holding the primary for his replacement on 9/11/2001, that had to
be postponed.

On Fri, Jan 3, 2020 at 1:53 PM Savor, Thomas (Alpharetta)
 wrote:
>
> You mean the Mayor that killed corruption and the Mafia in Nyc...that idiot ??
>
> Thanks,
>
> Tom Savor
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Barkow, Eileen
> Sent: Friday, January 3, 2020 1:56 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today 
>
>   ⚠ EXTERNAL MESSAGE – Think Before You Click
>
>
>
> The current and past idiot Rudolph  Guilianni
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Jesse 1 Robinson
> Sent: Friday, January 3, 2020 1:24 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today 
>
> OK, bonus homework question: who was mayor of New York City in Jan 1, 2000?
>
> .
> .
> 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
> robin...@sce.com
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Jon Bathmaker]

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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Matt Hogstrom
Sent: Friday, January 3, 2020 9:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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  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  On
Behalf Of Joel C. Ewing
Sent: Thursday, January 2, 2020 9:54 PM
To: IBM-MAIN@LISTSERV.UA.EDU
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 +, "Schuffenhauer, Mark"  
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: IBM-MAIN@LISTSERV.UA.EDU
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: ibm-m...@bama.ua.edu
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

Re: it was 20 years ago today ....

[Savor, Thomas (Alpharetta)]

You mean the Mayor that killed corruption and the Mafia in Nyc...that idiot ?? 

Thanks,

Tom Savor
-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Barkow, Eileen
Sent: Friday, January 3, 2020 1:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

  ⚠ EXTERNAL MESSAGE – Think Before You Click



The current and past idiot Rudolph  Guilianni

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: Friday, January 3, 2020 1:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

OK, bonus homework question: who was mayor of New York City in Jan 1, 2000?

.
.
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
robin...@sce.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Barkow, Eileen]

The current and past idiot Rudolph  Guilianni

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: Friday, January 3, 2020 1:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

OK, bonus homework question: who was mayor of New York City in Jan 1, 2000?

.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Barkow, Eileen
Sent: Friday, January 3, 2020 8:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: [External] Re: FW: Re: it was 20 years ago today 

Would you believe that there is still fallout from Y2K. NYC parking meters 
could not accept credit cards because of it.



https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ny1.com%2Fnyc%2Fall-boroughs%2Fnews%2F2020%2F01%2F03%2Fsoftware-glitch-knocks-out-credit-card-payments-at-nyc-parking-meterdata=02%7C01%7Cebarkow%40doitt.nyc.gov%7C2f66622ef0ef4b14c32908d7907a3a7c%7C73d61799c28440228d4154cc4f1929ef%7C0%7C0%7C637136726982065700sdata=44W9ZI7xw9PDPq0nYOeCp108hZmsr80yNNpJJ52QSP4%3Dreserved=0



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Friday, January 3, 2020 11:26 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: FW: Re: it was 20 years ago today 



There were date dependencies in a lot of unexpected places, although some of 
them were of minor importance. There was no more reason to believe that 
everything was under control than there was to believe in the inevitability of 
disaster. Hidden among the hype were some plausible concerns. Frankly, we 
lucked out.





--

Shmuel (Seymour J.) Metz

https://gcc02.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.gmu.edu%2F~smetz3data=02%7C01%7Cebarkow%40doitt.nyc.gov%7C2f66622ef0ef4b14c32908d7907a3a7c%7C73d61799c28440228d4154cc4f1929ef%7C0%7C0%7C637136726982065700sdata=po0ExUffQ3uIV7rqwqa7bTuFXXgRFulja2k%2F3Ymhfj4%3Dreserved=0







From: IBM Mainframe Discussion List 
mailto:IBM-MAIN@LISTSERV.UA.EDU>> on behalf of 
Pommier, Rex mailto:rpomm...@sfgmembers.com>>

Sent: Friday, January 3, 2020 11:06 AM

To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>

Subject: Re: [External] Re: FW: Re: it was 20 years ago today 



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 
mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Joel 
C. Ewing

Sent: Thursday, January 2, 2020 9:54 PM

To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>

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 +, "Schuffenhauer, Mark" 
> mailto:mschu...@tcfbank.com>> 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: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>

> Subject: Re: FW: Re: it was 20 years ago today 

>

> External Email

>

> I was consulting at Arlington County, Virginia County Government. My whole 
> family 

Re: it was 20 years ago today ....

[Jesse 1 Robinson]

OK, bonus homework question: who was mayor of New York City in Jan 1, 2000? 

.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Barkow, Eileen
Sent: Friday, January 3, 2020 8:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: [External] Re: FW: Re: it was 20 years ago today 

Would you believe that there is still fallout from Y2K. NYC parking meters 
could not accept credit cards because of it.



https://www.ny1.com/nyc/all-boroughs/news/2020/01/03/software-glitch-knocks-out-credit-card-payments-at-nyc-parking-meter



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Friday, January 3, 2020 11:26 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: FW: Re: it was 20 years ago today 



There were date dependencies in a lot of unexpected places, although some of 
them were of minor importance. There was no more reason to believe that 
everything was under control than there was to believe in the inevitability of 
disaster. Hidden among the hype were some plausible concerns. Frankly, we 
lucked out.





--

Shmuel (Seymour J.) Metz

https://gcc02.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.gmu.edu%2F~smetz3data=02%7C01%7Cebarkow%40doitt.nyc.gov%7C668247219a474d4f929208d79069ad4c%7C73d61799c28440228d4154cc4f1929ef%7C0%7C0%7C637136655989197748sdata=fffL9bJBCNMoJYgF%2F2NSwhyJc29Tajp370CzvdEm%2Bmk%3Dreserved=0







From: IBM Mainframe Discussion List 
mailto:IBM-MAIN@LISTSERV.UA.EDU>> on behalf of 
Pommier, Rex mailto:rpomm...@sfgmembers.com>>

Sent: Friday, January 3, 2020 11:06 AM

To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>

Subject: Re: [External] Re: FW: Re: it was 20 years ago today 



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 
mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Joel 
C. Ewing

Sent: Thursday, January 2, 2020 9:54 PM

To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>

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 +, "Schuffenhauer, Mark" 
> mailto:mschu...@tcfbank.com>> 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: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>

> 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 

Re: it was 20 years ago today

[Gabe Goldberg]

Just came across:  ‘Here We Go. The Chaos Is Starting’: An Oral History 
of Y2K


https://www.popularmechanics.com/technology/security/a30338692/y2k-panic/

I still have about half the Y2K books I bought, figure they'll go with 
the next Great Purge. Circa 1995 I thought of doing "The Y2K Handbook" 
(like "The REXX Handbook" and two VM/ESA handbooks co-edited with Phil 
Smith) but never got around to it. Likely for the best, considering the 
tsunami of books published.


--
Gabriel Goldberg, Computers and Publishing, Inc.   g...@gabegold.com
3401 Silver Maple Place, Falls Church, VA 22042   (703) 204-0433
LinkedIn: http://www.linkedin.com/in/gabegoldTwitter: GabeG0

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Jesse 1 Robinson]

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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Matt Hogstrom
Sent: Friday, January 3, 2020 9:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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  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  On 
> Behalf Of Joel C. Ewing
> Sent: Thursday, January 2, 2020 9:54 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 +, "Schuffenhauer, Mark" 
>>  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: IBM-MAIN@LISTSERV.UA.EDU
>> 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 
>> exten

Re: [External] Re: FW: Re: it was 20 years ago today ....

[Seymour J Metz]

If a company was so shortsighted as to not deal with it decades earlier, then 
what's wrong with charging all that the market will bear? The companies that 
planned ahead didn't have to spend nearly as much.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Matt Hogstrom 
Sent: Friday, January 3, 2020 12:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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  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  On Behalf Of 
> Joel C. Ewing
> Sent: Thursday, January 2, 2020 9:54 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 +, "Schuffenhauer, Mark" 
>>  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: IBM-MAIN@LISTSERV.UA.EDU
>> 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: ibm-m...@bama.ua.edu
>>> Subject: Re: it was 20 

Re: [External] Re: FW: Re: it was 20 years ago today ....

[Matt Hogstrom]

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  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  On Behalf Of 
> Joel C. Ewing
> Sent: Thursday, January 2, 2020 9:54 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 +, "Schuffenhauer, Mark" 
>>  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: IBM-MAIN@LISTSERV.UA.EDU
>> 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: ibm-m...@bama.ua.edu
>>> 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). 

Re: FW: Re: it was 20 years ago today ....

[Seymour J Metz]

One wonders how reliable their judgement was as to what was needed. The cost of 
doing unnecessary remediation was a lot lower than the cost of finding out too 
late that it was necessary.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Schuffenhauer, Mark 
Sent: Thursday, January 2, 2020 7:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: FW: Re: it was 20 years ago today 

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: IBM-MAIN@LISTSERV.UA.EDU
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: ibm-m...@bama.ua.edu
> 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.
>
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DISCLAIMER: This email and any attachments may contain confidential information 
that is intended solely for use by the intended recipient(s). If you are not 
the intended recipient, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the communication. If 
you received this email in error, please contact the sender by reply email and 
immediately delete the communication.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Seymour J Metz]

There were sound reasons to worry about economic chaos, but a total 
infrastructure collapse, while conceivable, didn't seem likely. I don't recall 
exactly what Alsop predicted.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Jesse 1 Robinson 
Sent: Thursday, January 2, 2020 7:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

I heard a 'Y2K person' interviewed on NPR recently. Her point was that if the 
IT industry had done nothing in advance to remediate, we would have had utter 
chaos on 1/1/2000. But we did prepare. We undoubtedly overprepared, but by how 
much will forever remain a mystery.

In the 90s Stewart Alsop famously predicted the end of the world. He retreated 
well before the event itself. We all buy insurance that we're thrilled not to 
utilize. That doesn't make it a waste.

.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Schuffenhauer, Mark
Sent: Thursday, January 2, 2020 4:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: FW: Re: it was 20 years ago today 

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: IBM-MAIN@LISTSERV.UA.EDU
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: ibm-m...@bama.ua.edu
> 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.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Seymour J Metz]

"01YY" was certainly a hack, as were rolling windows. Lilian was a much sounder 
way to go, where it was feasible. 


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Joel C. Ewing 
Sent: Thursday, January 2, 2020 7:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

Around 1990 it became clear that our installation needed some
alternative to a universally-used, in-house date subroutine -- one which
supported all sorts of date calculations, conversion between several
different formats, offsets from dates, day of week adjustments, etc.  It
had been extended and modified many times, and depending on the type of
request the same field in a complex structured parameter block might be
used as  input, output, or just ignored.   In other words, it was next
to impossible to be sure there weren't some unintended behaviors that
someone had learned to exploit, and it was equally certain there was no
way to verify the unstructured code was even 100% accurate for pre-2000
dates.  Since it used two-digit years and base-1900  windowing, the old
date routine would clearly fail for dates or date calculations crossing
the year 2000 boundary.

Before 1990, I had encountered the B.G. Ohms article "Computer
Processing of Dates Outside the Twentieth Century" in the IBM Systems
Journal,  (Vol 25, No 2, 1986, pp 244), which suggested use of what the
author called "Lilian date format" (days from Oct 15, 1582) to simplify
date computations.  I used that as the base internal date format for a
new structured date routine, which handled all sorts of date format
conversions, date calculations, relative and absolute date windowing to
convert two-digit to four-digit years, etc. and we started phasing out
use of the old date routine to eliminate the most obvious common point
of failure.

 From 1997-1999 various tools and significant person-hours were used to
locate two-digit year date usage in over 10,000 in-house application
programs, which were then remediated with four-digit years and tested on
a test system running with future dates.  There were some cases, mostly
involving data entry, where it made sense to allow
relative-to-current-year windowing to convert two-digit years to four
digits, but absolute windowing was strongly discouraged and dates
retained in external files were converted to four-digit years.

As others have noted, solving the immediate Y2K problem by merely
changing two-digit years to use a different absolute-base windowing
scheme was a questionable temporary solution, creating yet another,
potentially more-costly problem in the future.

Our Y2K remediation efforts found and fixed many potential problems that
would otherwise have made the first several months of 2000 chaotic.  As
a result, the transition from 1999 to 2000 was uneventful with no
significant problems.

There were no "hacks" of which I was aware from IBM to ease the
transition, unless you count changing the definition of year values in
SMF records from "00YY" to "01YY" for dates past 1999.   There were of
course various PTFs to fix any issues with four-digit years in MVS and
in IBM applications. I recall one notable PTF to fix an erroneous
leap-year determination in ISPF that even turned up pre-Y2K in the early
1990's -- a good example of why date calculation code should avoid
clever efficiency over obvious and verifiable algorithms.   There were
some offerings from 3rd party vendors.  There were also a steady stream
of "crackpot" easy-fix suggestions on newsgroups in the late 1990's from
people not understanding the issues, and in 1999 from alarmists
predicting failures of computer-based control devices that that had no
logical reason to be using dates in any significant way.

The problem for us was not "how" to fix a single instance of the
problem, but finding "where" to fix an unknown number of instances of
the problem in 1000's of lines of in-house code and in associated data sets.
 JC Ewing

On 1/2/20 3:06 PM, Pommier, Rex wrote:
> Hi Ron,
>
> I think the rolling century was implemented at a lot of places.  IIRC, didn't 
> DFSort have something like that as well as SAS?  The company I was at over 
> Y2K went through and converted everything to 4 digit years.  I believe the 
> one I'm with now did the same thing.
>
> Rex
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> McCabe, Ron
> Sent: Thursday, January 2, 2020 2:50 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [External] Re: it was 20 years ago today
>
> Question about how the year 2000 was handled as we just got hit by a major 
> date problem.  I remember that one way to handle the date comparisons was to 
> have all the years from 00-19 (or something greater than 19) have a high 
>

Re: [External] Re: FW: Re: it was 20 years ago today ....

[Barkow, Eileen]

Would you believe that there is still fallout from Y2K. NYC parking meters 
could not accept credit cards because of it.



https://www.ny1.com/nyc/all-boroughs/news/2020/01/03/software-glitch-knocks-out-credit-card-payments-at-nyc-parking-meter



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Friday, January 3, 2020 11:26 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: FW: Re: it was 20 years ago today 



There were date dependencies in a lot of unexpected places, although some of 
them were of minor importance. There was no more reason to believe that 
everything was under control than there was to believe in the inevitability of 
disaster. Hidden among the hype were some plausible concerns. Frankly, we 
lucked out.





--

Shmuel (Seymour J.) Metz

https://gcc02.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.gmu.edu%2F~smetz3data=02%7C01%7Cebarkow%40doitt.nyc.gov%7C668247219a474d4f929208d79069ad4c%7C73d61799c28440228d4154cc4f1929ef%7C0%7C0%7C637136655989197748sdata=fffL9bJBCNMoJYgF%2F2NSwhyJc29Tajp370CzvdEm%2Bmk%3Dreserved=0







From: IBM Mainframe Discussion List 
mailto:IBM-MAIN@LISTSERV.UA.EDU>> on behalf of 
Pommier, Rex mailto:rpomm...@sfgmembers.com>>

Sent: Friday, January 3, 2020 11:06 AM

To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>

Subject: Re: [External] Re: FW: Re: it was 20 years ago today 



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 
mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Joel 
C. Ewing

Sent: Thursday, January 2, 2020 9:54 PM

To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>

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 +, "Schuffenhauer, Mark" 
> mailto:mschu...@tcfbank.com>> 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: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>

> 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

Re: [External] Re: FW: Re: it was 20 years ago today ....

[Seymour J Metz]

There were date dependencies in a lot of unexpected places, although some of 
them were of minor importance. There was no more reason to believe that 
everything was under control than there was to believe in the inevitability of 
disaster. Hidden among the hype were some plausible concerns. Frankly, we 
lucked out.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Pommier, Rex 
Sent: Friday, January 3, 2020 11:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [External] Re: FW: Re: it was 20 years ago today 

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  On Behalf Of 
Joel C. Ewing
Sent: Thursday, January 2, 2020 9:54 PM
To: IBM-MAIN@LISTSERV.UA.EDU
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 +, "Schuffenhauer, Mark" 
>  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: IBM-MAIN@LISTSERV.UA.EDU
> 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: ibm-m...@bama.ua.edu
>> 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 / ar

Re: it was 20 years ago today

[Jesse 1 Robinson]

It has long been a hallmark of our profession to over-achieve. We prepared for 
Y2K so well that predicted chaos was averted. Even entertaining chaos was rare. 


I was personally convinced that we would be 'OK', but I made one particular 
concession to the doomsday crowd. I collected a few hundred dollars' worth of 
$5 bills on the grounds that ATMs might be the only source of cash. Didn't want 
to have to pay $20 each for every little thing. I eventually spent them all at 
leisure.  

.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Vernooij, Kees (ITOP NM) - KLM
Sent: Friday, January 3, 2020 6:43 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: it was 20 years ago today

Correct. 
And then I see yesterday on a local news site an article with a suggestive 
title like: a lot of fuzz, but hardly any problems really occurred.

The article itself has a little more nuance, but it is still nice food for 
title hunters (useful if your business model exists of getting as much people 
as possible to generate advertisement hits).

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jeremy Nicoll
Sent: 03 January 2020 15:24
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

On Fri, 3 Jan 2020, at 00:49, Joel C. Ewing wrote:

> The problem for us was not "how" to fix a single instance of the 
> problem, but finding "where" to fix an unknown number of instances of 
> the problem in 1000's of lines of in-house code and in associated data sets.

I think how complex this was depended a lot on how old a site's applications 
were.  It also depended on how long the 'tail' or archived data was.

Suppose you identified all the instances of a single date data column in a 
single current file that might be read and rewritten by umpteen programs.  If 
you changed all the programs you'd also need either to change the data in all 
the archived files as well, or make the program able to decide whether it was 
running in pre-change or post-change mode.

But you'd also need to change all the other programs that also read those old 
archive files.  And that might have knpck-on effects on other files that they 
manipulated.

While doing this, you also had to make sure that - if your change failed - you 
could back it out and create/recreate all the related files.

It's rapidly obvious that you can't change all old files in sync with a series 
of program changes and still allow all your old, or not-yet-changed programs to 
process the old files (because you changed those).

That's why the date-window approach got  used.  The as-yet-unchanged programs 
could contine to read all the archived data, while the updated programs could 
handle the old-format data more intelligently.

If I remember correctly, one of the changes that happened (to customer
TS) was that we no longer supported customers aged > 100.  I have no idea 
what they were meant to do with their money.

Where I worked (a UK bank), Y2K was a big deal.  A colossal amount of work was 
done in the two or so years beforehand, and on the night the computer centre 
was heavily staffed - not quite as many of us as on a normal day, but 
nevertheless lots.

We had by then run simulated workloads back and forth across the date change 
many times, as well as checking things like how end-of-financial/ tax 
year/calendendar year processing could be expected to go (at eg end of March 
2000, 5/6 April 2000, 31 Dec 2000) and I expect beyond that as eg programmes 
doing 2-year, 5-year etc historical reports and those doing forecasting that 
might not run until some months later also needed to be thought to be ok.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [External] Re: FW: Re: it was 20 years ago today ....

[Pommier, Rex]

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  On Behalf Of 
Joel C. Ewing
Sent: Thursday, January 2, 2020 9:54 PM
To: IBM-MAIN@LISTSERV.UA.EDU
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 +, "Schuffenhauer, Mark" 
>  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: IBM-MAIN@LISTSERV.UA.EDU
> 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: ibm-m...@bama.ua.edu
>> 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 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Vernooij, Kees (ITOP NM) - KLM]

Correct. 
And then I see yesterday on a local news site an article with a suggestive 
title like: a lot of fuzz, but hardly any problems really occurred.

The article itself has a little more nuance, but it is still nice food for 
title hunters (useful if your business model exists of getting as much people 
as possible to generate advertisement hits).

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jeremy Nicoll
Sent: 03 January 2020 15:24
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

On Fri, 3 Jan 2020, at 00:49, Joel C. Ewing wrote:

> The problem for us was not "how" to fix a single instance of the 
> problem, but finding "where" to fix an unknown number of instances of 
> the problem in 1000's of lines of in-house code and in associated data sets.

I think how complex this was depended a lot on how old a site's applications
were.  It also depended on how long the 'tail' or archived data was.

Suppose you identified all the instances of a single date data column in a 
single 
current file that might be read and rewritten by umpteen programs.  If you 
changed all the programs you'd also need either to change the data in all
the archived files as well, or make the program able to decide whether it 
was running in pre-change or post-change mode.

But you'd also need to change all the other programs that also read those
old archive files.  And that might have knpck-on effects on other files that
they manipulated.

While doing this, you also had to make sure that - if your change failed - 
you could back it out and create/recreate all the related files.

It's rapidly obvious that you can't change all old files in sync with a series
of program changes and still allow all your old, or not-yet-changed
programs to process the old files (because you changed those).

That's why the date-window approach got  used.  The as-yet-unchanged 
programs could contine to read all the archived data, while the updated
programs could handle the old-format data more intelligently.

If I remember correctly, one of the changes that happened (to customer 
TS) was that we no longer supported customers aged > 100.  I have
no idea what they were meant to do with their money.

Where I worked (a UK bank), Y2K was a big deal.  A colossal amount of work
was done in the two or so years beforehand, and on the night the computer
centre was heavily staffed - not quite as many of us as on a normal day, but 
nevertheless lots.

We had by then run simulated workloads back and forth across the date
change many times, as well as checking things like how end-of-financial/
tax year/calendendar year processing could be expected to go (at eg end
of March 2000, 5/6 April 2000, 31 Dec 2000) and I expect beyond that as 
eg programmes doing 2-year, 5-year etc historical reports and those doing
forecasting that might not run until some months later also needed to be 
thought to be ok.

-- 
Jeremy Nicoll - my opinions are my own.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Jeremy Nicoll]

On Fri, 3 Jan 2020, at 00:49, Joel C. Ewing wrote:

> The problem for us was not "how" to fix a single instance of the 
> problem, but finding "where" to fix an unknown number of instances of 
> the problem in 1000's of lines of in-house code and in associated data sets.

I think how complex this was depended a lot on how old a site's applications
were.  It also depended on how long the 'tail' or archived data was.

Suppose you identified all the instances of a single date data column in a 
single 
current file that might be read and rewritten by umpteen programs.  If you 
changed all the programs you'd also need either to change the data in all
the archived files as well, or make the program able to decide whether it 
was running in pre-change or post-change mode.

But you'd also need to change all the other programs that also read those
old archive files.  And that might have knpck-on effects on other files that
they manipulated.

While doing this, you also had to make sure that - if your change failed - 
you could back it out and create/recreate all the related files.

It's rapidly obvious that you can't change all old files in sync with a series
of program changes and still allow all your old, or not-yet-changed
programs to process the old files (because you changed those).

That's why the date-window approach got  used.  The as-yet-unchanged 
programs could contine to read all the archived data, while the updated
programs could handle the old-format data more intelligently.

If I remember correctly, one of the changes that happened (to customer 
TS) was that we no longer supported customers aged > 100.  I have
no idea what they were meant to do with their money.

Where I worked (a UK bank), Y2K was a big deal.  A colossal amount of work
was done in the two or so years beforehand, and on the night the computer
centre was heavily staffed - not quite as many of us as on a normal day, but 
nevertheless lots.

We had by then run simulated workloads back and forth across the date
change many times, as well as checking things like how end-of-financial/
tax year/calendendar year processing could be expected to go (at eg end
of March 2000, 5/6 April 2000, 31 Dec 2000) and I expect beyond that as 
eg programmes doing 2-year, 5-year etc historical reports and those doing
forecasting that might not run until some months later also needed to be 
thought to be ok.

-- 
Jeremy Nicoll - my opinions are my own.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Vernooij, Kees (ITOP NM) - KLM]

*That* seems like a lifetime ago...

Kees


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Rupert Reynolds
Sent: 03 January 2020 13:17
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

. . . "Sgt Pepper taught the band to play" :-)

On Tue, 31 Dec 2019, 18:26 Chris Hoelscher,  wrote:

> Has it been 20 years since Y2K?? sometimes it seems like last year, other
> times seems like another lifetime .
>
> Thank You,
> Chris Hoelscher| Lead Database Administrator | IBM Global Technical
> Services| T 502.476.2538  or 502.407.7266
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Rupert Reynolds]

. . . "Sgt Pepper taught the band to play" :-)

On Tue, 31 Dec 2019, 18:26 Chris Hoelscher,  wrote:

> Has it been 20 years since Y2K?? sometimes it seems like last year, other
> times seems like another lifetime .
>
> Thank You,
> Chris Hoelscher| Lead Database Administrator | IBM Global Technical
> Services| T 502.476.2538  or 502.407.7266
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Wayne Bickerdike]

known number of instances of
> the problem in 1000's of lines of in-house code and in associated data
> sets.
>  JC Ewing
>
> On 1/2/20 3:06 PM, Pommier, Rex wrote:
> > Hi Ron,
> >
> > I think the rolling century was implemented at a lot of places.  IIRC,
> didn't DFSort have something like that as well as SAS?  The company I was
> at over Y2K went through and converted everything to 4 digit years.  I
> believe the one I'm with now did the same thing.
> >
> > Rex
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List  On
> Behalf Of McCabe, Ron
> > Sent: Thursday, January 2, 2020 2:50 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: [External] Re: it was 20 years ago today
> >
> > Question about how the year 2000 was handled as we just got hit by a
> major date problem.  I remember that one way to handle the date comparisons
> was to have all the years from 00-19 (or something greater than 19) have a
> high value so it would be greater than the 1990's.  Does anyone remember
> that?  Was it something IBM did although I don't recall putting on any
> patches for something like that so I'm thinking it was something we did.
> >
> > Thanks,
> > Ron McCabe
> > Manager of Mainframe/Midrange Systems
> > Mutual of Enumclaw
> >
> ...
>
> --
> Joel C. Ewing
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
Wayne V. Bickerdike

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FW: Re: it was 20 years ago today ....

[Joel C. Ewing]

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 +, "Schuffenhauer, Mark"  
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: IBM-MAIN@LISTSERV.UA.EDU
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: ibm-m...@bama.ua.edu
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FW: Re: it was 20 years ago today ....

[Bill Dodge]

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 +, "Schuffenhauer, Mark"  
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: IBM-MAIN@LISTSERV.UA.EDU
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: ibm-m...@bama.ua.edu
> 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.
>
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DISCLAIMER: This email and any attachments may contain confidential information 
that is intended solely for use by the intended recipient(s). If you are not 
the intended recipient, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the communication. If 
you received this email in error, please contact the sender by reply email and 
immediately delete the communication.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Tom Brennan]

> In the 90s Stewart Alsop famously predicted the end of the world.

I just checked my old book collection and found "Time Bomb 2000" by 
Edward and Jennifer Yourdon.  On the back it has questions like, Will 
your car run?, Will there be food?, Will your PC work? ...  Yep, I fell 
for it.  Marked $19.99 - I hope I got a really good discount.


On 1/2/2020 4:18 PM, Jesse 1 Robinson wrote:

I heard a 'Y2K person' interviewed on NPR recently. Her point was that if the 
IT industry had done nothing in advance to remediate, we would have had utter 
chaos on 1/1/2000. But we did prepare. We undoubtedly overprepared, but by how 
much will forever remain a mystery.

In the 90s Stewart Alsop famously predicted the end of the world. He retreated 
well before the event itself. We all buy insurance that we're thrilled not to 
utilize. That doesn't make it a waste.

.
.
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
robin...@sce.com


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Schuffenhauer, Mark]

I don't think it was a complete waste, code was changed that did not need to be.

With code changes came tools we paid for that were never used again.

The number of high severity issues due to bad code changes was punitive,  as 
was the cost of missing SLA's.  The cost of physical resources to cover all the 
really slow statically linked programs to manage date stuff, whether it was 
needed or not.

No plan for managing all the data and inventory created so it could be 
leveraged on future projects.

It started out as a Shriek joke many years ago, but computer systems are like 
onions, if you don't peel through the layers and be concerned about all the 
layers, something will bite you in the face.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: Thursday, January 2, 2020 6:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today 

External Email

I heard a 'Y2K person' interviewed on NPR recently. Her point was that if the 
IT industry had done nothing in advance to remediate, we would have had utter 
chaos on 1/1/2000. But we did prepare. We undoubtedly overprepared, but by how 
much will forever remain a mystery.

In the 90s Stewart Alsop famously predicted the end of the world. He retreated 
well before the event itself. We all buy insurance that we're thrilled not to 
utilize. That doesn't make it a waste.

.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Schuffenhauer, Mark
Sent: Thursday, January 2, 2020 4:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: FW: Re: it was 20 years ago today 

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: IBM-MAIN@LISTSERV.UA.EDU
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: ibm-m...@bama.ua.edu
> 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.


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DISCLAIMER: This email and any attachments may contain confidential information 
that is intended solely for use by the intended recipient(s). If you are not 
the intended recipient, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the communication. If 
you received this email in error, please contact the sender by reply email and 
immediately delete the communication.

--

Re: FW: Re: it was 20 years ago today ....

[Mike Schwab]

We had people come in on the 1st to test everything.  Nothing happen.
A few websites didn't add 1900 to the year, they put a 19 in front of
the  year, resulting in 19100.

On Thu, Jan 2, 2020 at 5:20 PM 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: ibm-m...@bama.ua.edu <mailto:ibm-m...@bama.ua.edu>
> > 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.
> >
> >
> >
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> >
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Joel C. Ewing]

Around 1990 it became clear that our installation needed some 
alternative to a universally-used, in-house date subroutine -- one which 
supported all sorts of date calculations, conversion between several 
different formats, offsets from dates, day of week adjustments, etc.  It 
had been extended and modified many times, and depending on the type of 
request the same field in a complex structured parameter block might be 
used as  input, output, or just ignored.   In other words, it was next 
to impossible to be sure there weren't some unintended behaviors that 
someone had learned to exploit, and it was equally certain there was no 
way to verify the unstructured code was even 100% accurate for pre-2000 
dates.  Since it used two-digit years and base-1900  windowing, the old 
date routine would clearly fail for dates or date calculations crossing 
the year 2000 boundary.


Before 1990, I had encountered the B.G. Ohms article "Computer 
Processing of Dates Outside the Twentieth Century" in the IBM Systems 
Journal,  (Vol 25, No 2, 1986, pp 244), which suggested use of what the 
author called "Lilian date format" (days from Oct 15, 1582) to simplify 
date computations.  I used that as the base internal date format for a 
new structured date routine, which handled all sorts of date format 
conversions, date calculations, relative and absolute date windowing to 
convert two-digit to four-digit years, etc. and we started phasing out 
use of the old date routine to eliminate the most obvious common point 
of failure.


From 1997-1999 various tools and significant person-hours were used to 
locate two-digit year date usage in over 10,000 in-house application 
programs, which were then remediated with four-digit years and tested on 
a test system running with future dates.  There were some cases, mostly 
involving data entry, where it made sense to allow 
relative-to-current-year windowing to convert two-digit years to four 
digits, but absolute windowing was strongly discouraged and dates 
retained in external files were converted to four-digit years.


As others have noted, solving the immediate Y2K problem by merely 
changing two-digit years to use a different absolute-base windowing 
scheme was a questionable temporary solution, creating yet another, 
potentially more-costly problem in the future.


Our Y2K remediation efforts found and fixed many potential problems that 
would otherwise have made the first several months of 2000 chaotic.  As 
a result, the transition from 1999 to 2000 was uneventful with no 
significant problems.


There were no "hacks" of which I was aware from IBM to ease the 
transition, unless you count changing the definition of year values in 
SMF records from "00YY" to "01YY" for dates past 1999.   There were of 
course various PTFs to fix any issues with four-digit years in MVS and 
in IBM applications. I recall one notable PTF to fix an erroneous 
leap-year determination in ISPF that even turned up pre-Y2K in the early 
1990's -- a good example of why date calculation code should avoid 
clever efficiency over obvious and verifiable algorithms.   There were 
some offerings from 3rd party vendors.  There were also a steady stream 
of "crackpot" easy-fix suggestions on newsgroups in the late 1990's from 
people not understanding the issues, and in 1999 from alarmists 
predicting failures of computer-based control devices that that had no 
logical reason to be using dates in any significant way.


The problem for us was not "how" to fix a single instance of the 
problem, but finding "where" to fix an unknown number of instances of 
the problem in 1000's of lines of in-house code and in associated data sets.

    JC Ewing

On 1/2/20 3:06 PM, Pommier, Rex wrote:

Hi Ron,

I think the rolling century was implemented at a lot of places.  IIRC, didn't 
DFSort have something like that as well as SAS?  The company I was at over Y2K 
went through and converted everything to 4 digit years.  I believe the one I'm 
with now did the same thing.

Rex

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
McCabe, Ron
Sent: Thursday, January 2, 2020 2:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: it was 20 years ago today

Question about how the year 2000 was handled as we just got hit by a major date 
problem.  I remember that one way to handle the date comparisons was to have 
all the years from 00-19 (or something greater than 19) have a high value so it 
would be greater than the 1990's.  Does anyone remember that?  Was it something 
IBM did although I don't recall putting on any patches for something like that 
so I'm thinking it was something we did.

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


...

--
Joel C. Ewing

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Jesse 1 Robinson]

I heard a 'Y2K person' interviewed on NPR recently. Her point was that if the 
IT industry had done nothing in advance to remediate, we would have had utter 
chaos on 1/1/2000. But we did prepare. We undoubtedly overprepared, but by how 
much will forever remain a mystery. 

In the 90s Stewart Alsop famously predicted the end of the world. He retreated 
well before the event itself. We all buy insurance that we're thrilled not to 
utilize. That doesn't make it a waste. 

.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Schuffenhauer, Mark
Sent: Thursday, January 2, 2020 4:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: FW: Re: it was 20 years ago today 

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: IBM-MAIN@LISTSERV.UA.EDU
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: ibm-m...@bama.ua.edu
> 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.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FW: Re: it was 20 years ago today ....

[Schuffenhauer, Mark]

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: IBM-MAIN@LISTSERV.UA.EDU
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: ibm-m...@bama.ua.edu
> 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.
>
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DISCLAIMER: This email and any attachments may contain confidential information 
that is intended solely for use by the intended recipient(s). If you are not 
the intended recipient, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the communication. If 
you received this email in error, please contact the sender by reply email and 
immediately delete the communication.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FW: Re: it was 20 years ago today ....

[Bill Dodge]

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: ibm-m...@bama.ua.edu
> 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.
>
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: FW: Re: it was 20 years ago today ....

[Tom Brennan]

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: ibm-m...@bama.ua.edu <mailto:ibm-m...@bama.ua.edu>
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.

  



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Jesse 1 Robinson]

I would say that windowing was the nearly universal remediation for Y2K. How 
that window was defined and implemented varied by shop. But yes, the problem of 
handling windowing in the future is real. I think that most shops 'decided' 
somewhere up the line that windowing was a temporary workaround pending a 
permanent fix. Temporary workarounds live forever, especially this one because 
Y2K funding has long since disappeared from everyone's budget.  But the window 
has to get moved along from time to time. 

Two things.

1. Creating and maintaining windowing is almost entirely an application issue. 
I never heard of a single system-level windowing fix. Each shop had to decide 
for itself on the appropriate window boundaries and how to handle in-window and 
out-window cases.

2. Until a permanent fix is implemented--changing all dates to fully 
qualified--it's incumbent on the survivors to document the windowing process 
remaining in place. I honestly don't know what our apps folx did, but we do 
have an ancient universal date routine that most apps call for any date-related 
issue. That may have been used.  

.
.
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
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
McCabe, Ron
Sent: Thursday, January 2, 2020 1:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: it was 20 years ago today

From what I'm finding in our shop the date century window was 20 and it just 
got bumped up to 30...so in ten years we will have to go through this again and 
no will remember about it.

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Chris Hoelscher
Sent: Thursday, January 2, 2020 1:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

In our shop it was 69 for date century windowing .

Thank You,
Chris Hoelscher| Lead Database Administrator | IBM Global Technical Services| T 
502.476.2538  or 502.407.7266

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
McCabe, Ron
Sent: Thursday, January 2, 2020 3:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] it was 20 years ago today

Question about how the year 2000 was handled as we just got hit by a major date 
problem.  I remember that one way to handle the date comparisons was to have 
all the years from 00-19 (or something greater than 19) have a high value so it 
would be greater than the 1990's.  Does anyone remember that?  Was it something 
IBM did although I don't recall putting on any patches for something like that 
so I'm thinking it was something we did.

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Wayne Bickerdike
Sent: Thursday, January 2, 2020 11:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

The tale has many variations. Unlikely to have been Bessie Braddock. WC died in 
1965 and was out of politics. It was reputed to be Lady Astor.

On Fri, Jan 3, 2020, 05:03 Seymour J Metz  wrote:

> To put it in context, WC called her ugly *before* she called him drunk.
>
>
> 
> From: IBM Mainframe Discussion List  on 
> behalf of Nightwatch RenBand 
> Sent: Thursday, January 2, 2020 11:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today
>
> Hey, Rupert!
> Winston Churchill and the British politician Bessie Braddock.
> Braddock encountered an intoxicated Churchill and said “Sir, you are 
> drunk.”
> He replied:And you, Bessie, are ugly. But I shall be sober in the 
> morning, and you will still be ugly.
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

FW: Re: it was 20 years ago today ....

[Phil Smith III]

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: ibm-m...@bama.ua.edu <mailto:ibm-m...@bama.ua.edu> 
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.

 


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Seymour J Metz]

IBM provided PTFs for IBM's code, not for customer-written applications. Of 
course, you could contract with IBM to help, but the updates would not come in 
the form of PTFs.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
McCabe, Ron 
Sent: Thursday, January 2, 2020 4:10 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

Several "hacks"?  Were any of these "hacks" provided by IBM in the form of a 
PTF?

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Thursday, January 2, 2020 1:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

There were several hacks; one was to change the interpretation of a binary  XL1 
or H, or a decimal, PL2 field from "last two digits" to "offset from 1900".


--
Shmuel (Seymour J.) Metz
https://nam03.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.gmu.edu%2F~smetz3data=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Cc50e14882b7540a38c9408d78fc6c604%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1%7C0%7C637135956219215589sdata=2IKGguhb6ElhN9ofIVvZrpYfwFhQXzQyLRZ3sCVTVMg%3Dreserved=0



From: IBM Mainframe Discussion List  on behalf of 
McCabe, Ron 
Sent: Thursday, January 2, 2020 3:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

Question about how the year 2000 was handled as we just got hit by a major date 
problem.  I remember that one way to handle the date comparisons was to have 
all the years from 00-19 (or something greater than 19) have a high value so it 
would be greater than the 1990's.  Does anyone remember that?  Was it something 
IBM did although I don't recall putting on any patches for something like that 
so I'm thinking it was something we did.

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Wayne Bickerdike
Sent: Thursday, January 2, 2020 11:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

The tale has many variations. Unlikely to have been Bessie Braddock. WC died in 
1965 and was out of politics. It was reputed to be Lady Astor.

On Fri, Jan 3, 2020, 05:03 Seymour J Metz  wrote:

> To put it in context, WC called her ugly *before* she called him drunk.
>
>
> --
> Shmuel (Seymour J.) Metz
> https://nam03.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.g
> mu.edu%2F~smetz3data=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca
> 5aa0fd43f984a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1
> %7C0%7C637135892512149457sdata=XQ0p8EtwOY8eQKAZZ5mVHuyWkk0PVQOAYC
> nk55KHbWA%3Dreserved=0
>
>
> 
> From: IBM Mainframe Discussion List  on
> behalf of Nightwatch RenBand 
> Sent: Thursday, January 2, 2020 11:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today
>
> Hey, Rupert!
> Winston Churchill and the British politician Bessie Braddock.
> Braddock encountered an intoxicated Churchill and said "Sir, you are
> drunk."
> He replied:And you, Bessie, are ugly. But I shall be sober in the
> morning, and you will still be ugly.
>
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecu
> re-web.cisco.com%2F1OFrGwpGH70rWFs-EMrAUGN6jEySb0De7a6s2QRo2CooV41jBvU
> wt2DA-wvlsUv6Vkl8hQLFeQp838B2YxYNm3bXQYrUEDUbqL6uv0OdtAPbTmK3ntDdPqErj
> -pFyEwMc2ikZQl6Ec00T3S33_smVePsYfwcTRaZY7iKJQBPR83YKqmrpH11xvZ0VdPiqzb
> 3aKAvwkdBC8VF9tCr_ZuzEqFowOpI4HBGUkOfwka_WOra-l-jpRsX-4P_wDQHNN-kLvdk0
> 9SuCPE8frNDO6BQ3sW0IbNQsCgfD2pbyw8VT0Mc5Y8qSciQg7vVLkK0XeqjFG8PIL9f9yu
> gazObaPkSXhjVMJOP75CzEZ9UaneUrfag2vOvmBVI6JVU9ITlkvA3V%2Fhttps%253A%25
> 2F%252Fquoteinvestigator.com%252F2011%252F08%252F17%252Fsober-tomorrow
> %252Fdata=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca5aa0fd43f98
> 4a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1%7C0%7C6371
> 35892512149457sdata=w0kMpv2c7bqfh1LXpaS30lU9BQMTS%2B69tIbENs1tA9U
> %3Dreserved=0
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INF

Re: it was 20 years ago today

[Schuffenhauer, Mark]

For my y2k night, we were expected to be onsite, at the place I worked then.  
We had made lists, checked everything twice.  Lot's of hours to prepare, it 
felt like a marathon with the finish line in sight.

That morning, I started to feel tired and run down, I took a nap in the 
afternoon and woke up super sick, running a fever and other assorted unpleasant 
things.  I dragged myself to work,   Very little happened, had to look at one 
unrelated thing and test a few things out.   Mostly I slept.

We had a program that was called to handle dates. most dates were 3 or 4 char, 
so it didn't matter, but the program was called any way.  Our pivot year was 
further out, but I was told:  "it didn't matter because the mainframe was going 
away."  It's still going.

The program pivot year could have been changed.  The problem was solved over 
time and the date fields were expanded, or the work went to something newer.  
It was nice it was an opportunity to get things off OS/VS COBOL and COBOL II.

Mark

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Paul Gilmartin
Sent: Thursday, January 2, 2020 3:28 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

External Email

On Thu, 2 Jan 2020 21:14:23 +, McCabe, Ron wrote:

>From what I'm finding in our shop the date century window was 20 and it just 
>got bumped up to 30...so in ten years we will have to go through this again 
>and no will remember about it.
>
Dumbness is expanding: in 1965 there was a 30-year window.  In 1999 designers 
settled for 20.

Some places had the foresight to implement a sliding window,
e.g.: (Today-69,Today+30).  There were probably problems when archival data 
unexpectedly slid off the left end.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DISCLAIMER: This email and any attachments may contain confidential information 
that is intended solely for use by the intended recipient(s). If you are not 
the intended recipient, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the communication. If 
you received this email in error, please contact the sender by reply email and 
immediately delete the communication.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Paul Gilmartin]

On Thu, 2 Jan 2020 21:14:23 +, McCabe, Ron wrote:

>From what I'm finding in our shop the date century window was 20 and it just 
>got bumped up to 30...so in ten years we will have to go through this again 
>and no will remember about it.
>
Dumbness is expanding: in 1965 there was a 30-year window.  In 1999
designers settled for 20.

Some places had the foresight to implement a sliding window,
e.g.: (Today-69,Today+30).  There were probably problems
when archival data unexpectedly slid off the left end.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[McCabe, Ron]

From what I'm finding in our shop the date century window was 20 and it just 
got bumped up to 30...so in ten years we will have to go through this again and 
no will remember about it.

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Chris Hoelscher
Sent: Thursday, January 2, 2020 1:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

In our shop it was 69 for date century windowing .

Thank You,
Chris Hoelscher| Lead Database Administrator | IBM Global Technical Services| T 
502.476.2538  or 502.407.7266

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
McCabe, Ron
Sent: Thursday, January 2, 2020 3:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] it was 20 years ago today

Question about how the year 2000 was handled as we just got hit by a major date 
problem.  I remember that one way to handle the date comparisons was to have 
all the years from 00-19 (or something greater than 19) have a high value so it 
would be greater than the 1990's.  Does anyone remember that?  Was it something 
IBM did although I don't recall putting on any patches for something like that 
so I'm thinking it was something we did.

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Wayne Bickerdike
Sent: Thursday, January 2, 2020 11:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

The tale has many variations. Unlikely to have been Bessie Braddock. WC died in 
1965 and was out of politics. It was reputed to be Lady Astor.

On Fri, Jan 3, 2020, 05:03 Seymour J Metz  wrote:

> To put it in context, WC called her ugly *before* she called him drunk.
>
>
> --
> Shmuel (Seymour J.) Metz
> https://nam03.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.g
> mu.edu%2F~smetz3data=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca
> 5aa0fd43f984a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1
> %7C0%7C637135892512149457sdata=XQ0p8EtwOY8eQKAZZ5mVHuyWkk0PVQOAYC
> nk55KHbWA%3Dreserved=0
>
>
> 
> From: IBM Mainframe Discussion List  on
> behalf of Nightwatch RenBand 
> Sent: Thursday, January 2, 2020 11:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today
>
> Hey, Rupert!
> Winston Churchill and the British politician Bessie Braddock.
> Braddock encountered an intoxicated Churchill and said “Sir, you are
> drunk.”
> He replied:And you, Bessie, are ugly. But I shall be sober in the
> morning, and you will still be ugly.
>
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecu
> re-web.cisco.com%2F1OFrGwpGH70rWFs-EMrAUGN6jEySb0De7a6s2QRo2CooV41jBvU
> wt2DA-wvlsUv6Vkl8hQLFeQp838B2YxYNm3bXQYrUEDUbqL6uv0OdtAPbTmK3ntDdPqErj
> -pFyEwMc2ikZQl6Ec00T3S33_smVePsYfwcTRaZY7iKJQBPR83YKqmrpH11xvZ0VdPiqzb
> 3aKAvwkdBC8VF9tCr_ZuzEqFowOpI4HBGUkOfwka_WOra-l-jpRsX-4P_wDQHNN-kLvdk0
> 9SuCPE8frNDO6BQ3sW0IbNQsCgfD2pbyw8VT0Mc5Y8qSciQg7vVLkK0XeqjFG8PIL9f9yu
> gazObaPkSXhjVMJOP75CzEZ9UaneUrfag2vOvmBVI6JVU9ITlkvA3V%2Fhttps%253A%25
> 2F%252Fquoteinvestigator.com%252F2011%252F08%252F17%252Fsober-tomorrow
> %252Fdata=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca5aa0fd43f98
> 4a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1%7C0%7C6371
> 35892512149457sdata=w0kMpv2c7bqfh1LXpaS30lU9BQMTS%2B69tIbENs1tA9U
> %3Dreserved=0
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN Confidentiality 
Notice: This e- mail and all attachments may contain CONFIDENTIAL information 
and are meant solely for the intended recipient. It may contain controlled, 
privileged, or proprietary information that is protected under applicable law 
and shall not be disclosed to any unauthorized third party. If you are not the 
intended recipient, you are hereby notified that any unauthorized review, 
action, disclosure, distribution, or reproduction of any information contained 
in this e- mail and any attachments is strictly PROHIBITED. If you received 
this e- mail in error, please reply to the sender immediately stating that this 
transmission was misdirected, and delete or destro

Re: it was 20 years ago today

[McCabe, Ron]

Several "hacks"?  Were any of these "hacks" provided by IBM in the form of a 
PTF?

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Thursday, January 2, 2020 1:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

There were several hacks; one was to change the interpretation of a binary  XL1 
or H, or a decimal, PL2 field from "last two digits" to "offset from 1900".


--
Shmuel (Seymour J.) Metz
https://nam03.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.gmu.edu%2F~smetz3data=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Cc50e14882b7540a38c9408d78fc6c604%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1%7C0%7C637135956219215589sdata=2IKGguhb6ElhN9ofIVvZrpYfwFhQXzQyLRZ3sCVTVMg%3Dreserved=0



From: IBM Mainframe Discussion List  on behalf of 
McCabe, Ron 
Sent: Thursday, January 2, 2020 3:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

Question about how the year 2000 was handled as we just got hit by a major date 
problem.  I remember that one way to handle the date comparisons was to have 
all the years from 00-19 (or something greater than 19) have a high value so it 
would be greater than the 1990's.  Does anyone remember that?  Was it something 
IBM did although I don't recall putting on any patches for something like that 
so I'm thinking it was something we did.

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Wayne Bickerdike
Sent: Thursday, January 2, 2020 11:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

The tale has many variations. Unlikely to have been Bessie Braddock. WC died in 
1965 and was out of politics. It was reputed to be Lady Astor.

On Fri, Jan 3, 2020, 05:03 Seymour J Metz  wrote:

> To put it in context, WC called her ugly *before* she called him drunk.
>
>
> --
> Shmuel (Seymour J.) Metz
> https://nam03.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.g
> mu.edu%2F~smetz3data=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca
> 5aa0fd43f984a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1
> %7C0%7C637135892512149457sdata=XQ0p8EtwOY8eQKAZZ5mVHuyWkk0PVQOAYC
> nk55KHbWA%3Dreserved=0
>
>
> 
> From: IBM Mainframe Discussion List  on
> behalf of Nightwatch RenBand 
> Sent: Thursday, January 2, 2020 11:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today
>
> Hey, Rupert!
> Winston Churchill and the British politician Bessie Braddock.
> Braddock encountered an intoxicated Churchill and said "Sir, you are
> drunk."
> He replied:And you, Bessie, are ugly. But I shall be sober in the
> morning, and you will still be ugly.
>
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecu
> re-web.cisco.com%2F1OFrGwpGH70rWFs-EMrAUGN6jEySb0De7a6s2QRo2CooV41jBvU
> wt2DA-wvlsUv6Vkl8hQLFeQp838B2YxYNm3bXQYrUEDUbqL6uv0OdtAPbTmK3ntDdPqErj
> -pFyEwMc2ikZQl6Ec00T3S33_smVePsYfwcTRaZY7iKJQBPR83YKqmrpH11xvZ0VdPiqzb
> 3aKAvwkdBC8VF9tCr_ZuzEqFowOpI4HBGUkOfwka_WOra-l-jpRsX-4P_wDQHNN-kLvdk0
> 9SuCPE8frNDO6BQ3sW0IbNQsCgfD2pbyw8VT0Mc5Y8qSciQg7vVLkK0XeqjFG8PIL9f9yu
> gazObaPkSXhjVMJOP75CzEZ9UaneUrfag2vOvmBVI6JVU9ITlkvA3V%2Fhttps%253A%25
> 2F%252Fquoteinvestigator.com%252F2011%252F08%252F17%252Fsober-tomorrow
> %252Fdata=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca5aa0fd43f98
> 4a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1%7C0%7C6371
> 35892512149457sdata=w0kMpv2c7bqfh1LXpaS30lU9BQMTS%2B69tIbENs1tA9U
> %3Dreserved=0
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN Confidentiality 
Notice: This e- mail and all attachments may contain CONFIDENTIAL information 
and are meant solely for the intended recipient. It may contain controlled, 
privileged, or proprietary information that is protected under applicable law 
and shall not be disclosed to any unauthorized third party. If you are not the 
intended recipient, you are hereby notified that any unauthorized review, 
action, disclosure, distribution

Re: it was 20 years ago today

[Pommier, Rex]

Hi Ron,

I think the rolling century was implemented at a lot of places.  IIRC, didn't 
DFSort have something like that as well as SAS?  The company I was at over Y2K 
went through and converted everything to 4 digit years.  I believe the one I'm 
with now did the same thing.

Rex

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
McCabe, Ron
Sent: Thursday, January 2, 2020 2:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: it was 20 years ago today

Question about how the year 2000 was handled as we just got hit by a major date 
problem.  I remember that one way to handle the date comparisons was to have 
all the years from 00-19 (or something greater than 19) have a high value so it 
would be greater than the 1990's.  Does anyone remember that?  Was it something 
IBM did although I don't recall putting on any patches for something like that 
so I'm thinking it was something we did.

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Wayne Bickerdike
Sent: Thursday, January 2, 2020 11:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

The tale has many variations. Unlikely to have been Bessie Braddock. WC died in 
1965 and was out of politics. It was reputed to be Lady Astor.

On Fri, Jan 3, 2020, 05:03 Seymour J Metz  wrote:

> To put it in context, WC called her ugly *before* she called him drunk.
>
>
> --
> Shmuel (Seymour J.) Metz
> https://nam03.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.g
> mu.edu%2F~smetz3data=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca
> 5aa0fd43f984a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1
> %7C0%7C637135892512149457sdata=XQ0p8EtwOY8eQKAZZ5mVHuyWkk0PVQOAYC
> nk55KHbWA%3Dreserved=0
>
>
> 
> From: IBM Mainframe Discussion List  on 
> behalf of Nightwatch RenBand 
> Sent: Thursday, January 2, 2020 11:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today
>
> Hey, Rupert!
> Winston Churchill and the British politician Bessie Braddock.
> Braddock encountered an intoxicated Churchill and said “Sir, you are 
> drunk.”
> He replied:And you, Bessie, are ugly. But I shall be sober in the 
> morning, and you will still be ugly.
>
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecu
> re-web.cisco.com%2F1OFrGwpGH70rWFs-EMrAUGN6jEySb0De7a6s2QRo2CooV41jBvU
> wt2DA-wvlsUv6Vkl8hQLFeQp838B2YxYNm3bXQYrUEDUbqL6uv0OdtAPbTmK3ntDdPqErj
> -pFyEwMc2ikZQl6Ec00T3S33_smVePsYfwcTRaZY7iKJQBPR83YKqmrpH11xvZ0VdPiqzb
> 3aKAvwkdBC8VF9tCr_ZuzEqFowOpI4HBGUkOfwka_WOra-l-jpRsX-4P_wDQHNN-kLvdk0
> 9SuCPE8frNDO6BQ3sW0IbNQsCgfD2pbyw8VT0Mc5Y8qSciQg7vVLkK0XeqjFG8PIL9f9yu
> gazObaPkSXhjVMJOP75CzEZ9UaneUrfag2vOvmBVI6JVU9ITlkvA3V%2Fhttps%253A%25
> 2F%252Fquoteinvestigator.com%252F2011%252F08%252F17%252Fsober-tomorrow
> %252Fdata=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca5aa0fd43f98
> 4a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1%7C0%7C6371
> 35892512149457sdata=w0kMpv2c7bqfh1LXpaS30lU9BQMTS%2B69tIbENs1tA9U
> %3Dreserved=0
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN Confidentiality 
Notice: This e- mail and all attachments may contain CONFIDENTIAL information 
and are meant solely for the intended recipient. It may contain controlled, 
privileged, or proprietary information that is protected under applicable law 
and shall not be disclosed to any unauthorized third party. If you are not the 
intended recipient, you are hereby notified that any unauthorized review, 
action, disclosure, distribution, or reproduction of any information contained 
in this e- mail and any attachments is strictly PROHIBITED. If you received 
this e- mail in error, please reply to the sender immediately stating that this 
transmission was misdirected, and delete or destroy all electronic and paper 
copies of this e-mail and attachments without disclosing the contents. This e- 
mail does not grant or assign rights of ownership in the proprietary subject 
matter herein, nor shall it be construed as a joint venture, partnership, 
teaming agreement, or any other formal business relationship.

--

Re: it was 20 years ago today

[Chris Hoelscher]

In our shop it was 69 for date century windowing .

Thank You,
Chris Hoelscher| Lead Database Administrator | IBM Global Technical Services| T 
502.476.2538  or 502.407.7266

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
McCabe, Ron
Sent: Thursday, January 2, 2020 3:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] it was 20 years ago today

Question about how the year 2000 was handled as we just got hit by a major date 
problem.  I remember that one way to handle the date comparisons was to have 
all the years from 00-19 (or something greater than 19) have a high value so it 
would be greater than the 1990's.  Does anyone remember that?  Was it something 
IBM did although I don't recall putting on any patches for something like that 
so I'm thinking it was something we did.

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Wayne Bickerdike
Sent: Thursday, January 2, 2020 11:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

The tale has many variations. Unlikely to have been Bessie Braddock. WC died in 
1965 and was out of politics. It was reputed to be Lady Astor.

On Fri, Jan 3, 2020, 05:03 Seymour J Metz  wrote:

> To put it in context, WC called her ugly *before* she called him drunk.
>
>
> --
> Shmuel (Seymour J.) Metz
> https://nam03.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.g
> mu.edu%2F~smetz3data=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca
> 5aa0fd43f984a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1
> %7C0%7C637135892512149457sdata=XQ0p8EtwOY8eQKAZZ5mVHuyWkk0PVQOAYC
> nk55KHbWA%3Dreserved=0
>
>
> 
> From: IBM Mainframe Discussion List  on 
> behalf of Nightwatch RenBand 
> Sent: Thursday, January 2, 2020 11:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today
>
> Hey, Rupert!
> Winston Churchill and the British politician Bessie Braddock.
> Braddock encountered an intoxicated Churchill and said “Sir, you are 
> drunk.”
> He replied:And you, Bessie, are ugly. But I shall be sober in the 
> morning, and you will still be ugly.
>
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecu
> re-web.cisco.com%2F1OFrGwpGH70rWFs-EMrAUGN6jEySb0De7a6s2QRo2CooV41jBvU
> wt2DA-wvlsUv6Vkl8hQLFeQp838B2YxYNm3bXQYrUEDUbqL6uv0OdtAPbTmK3ntDdPqErj
> -pFyEwMc2ikZQl6Ec00T3S33_smVePsYfwcTRaZY7iKJQBPR83YKqmrpH11xvZ0VdPiqzb
> 3aKAvwkdBC8VF9tCr_ZuzEqFowOpI4HBGUkOfwka_WOra-l-jpRsX-4P_wDQHNN-kLvdk0
> 9SuCPE8frNDO6BQ3sW0IbNQsCgfD2pbyw8VT0Mc5Y8qSciQg7vVLkK0XeqjFG8PIL9f9yu
> gazObaPkSXhjVMJOP75CzEZ9UaneUrfag2vOvmBVI6JVU9ITlkvA3V%2Fhttps%253A%25
> 2F%252Fquoteinvestigator.com%252F2011%252F08%252F17%252Fsober-tomorrow
> %252Fdata=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca5aa0fd43f98
> 4a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1%7C0%7C6371
> 35892512149457sdata=w0kMpv2c7bqfh1LXpaS30lU9BQMTS%2B69tIbENs1tA9U
> %3Dreserved=0
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN Confidentiality 
Notice: This e- mail and all attachments may contain CONFIDENTIAL information 
and are meant solely for the intended recipient. It may contain controlled, 
privileged, or proprietary information that is protected under applicable law 
and shall not be disclosed to any unauthorized third party. If you are not the 
intended recipient, you are hereby notified that any unauthorized review, 
action, disclosure, distribution, or reproduction of any information contained 
in this e- mail and any attachments is strictly PROHIBITED. If you received 
this e- mail in error, please reply to the sender immediately stating that this 
transmission was misdirected, and delete or destroy all electronic and paper 
copies of this e-mail and attachments without disclosing the contents. This e- 
mail does not grant or assign rights of ownership in the proprietary subject 
matter herein, nor shall it be construed as a joint venture, partnership, 
teaming agreement, or any other formal business relationship.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send em

Re: it was 20 years ago today

[Seymour J Metz]

There were several hacks; one was to change the interpretation of a binary  XL1 
or H, or a decimal, PL2 field from "last two digits" to "offset from 1900". 


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
McCabe, Ron 
Sent: Thursday, January 2, 2020 3:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

Question about how the year 2000 was handled as we just got hit by a major date 
problem.  I remember that one way to handle the date comparisons was to have 
all the years from 00-19 (or something greater than 19) have a high value so it 
would be greater than the 1990's.  Does anyone remember that?  Was it something 
IBM did although I don't recall putting on any patches for something like that 
so I'm thinking it was something we did.

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Wayne Bickerdike
Sent: Thursday, January 2, 2020 11:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

The tale has many variations. Unlikely to have been Bessie Braddock. WC died in 
1965 and was out of politics. It was reputed to be Lady Astor.

On Fri, Jan 3, 2020, 05:03 Seymour J Metz  wrote:

> To put it in context, WC called her ugly *before* she called him drunk.
>
>
> --
> Shmuel (Seymour J.) Metz
> https://nam03.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.g
> mu.edu%2F~smetz3data=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca
> 5aa0fd43f984a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1
> %7C0%7C637135892512149457sdata=XQ0p8EtwOY8eQKAZZ5mVHuyWkk0PVQOAYC
> nk55KHbWA%3Dreserved=0
>
>
> 
> From: IBM Mainframe Discussion List  on
> behalf of Nightwatch RenBand 
> Sent: Thursday, January 2, 2020 11:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today
>
> Hey, Rupert!
> Winston Churchill and the British politician Bessie Braddock.
> Braddock encountered an intoxicated Churchill and said “Sir, you are
> drunk.”
> He replied:And you, Bessie, are ugly. But I shall be sober in the
> morning, and you will still be ugly.
>
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecu
> re-web.cisco.com%2F1OFrGwpGH70rWFs-EMrAUGN6jEySb0De7a6s2QRo2CooV41jBvU
> wt2DA-wvlsUv6Vkl8hQLFeQp838B2YxYNm3bXQYrUEDUbqL6uv0OdtAPbTmK3ntDdPqErj
> -pFyEwMc2ikZQl6Ec00T3S33_smVePsYfwcTRaZY7iKJQBPR83YKqmrpH11xvZ0VdPiqzb
> 3aKAvwkdBC8VF9tCr_ZuzEqFowOpI4HBGUkOfwka_WOra-l-jpRsX-4P_wDQHNN-kLvdk0
> 9SuCPE8frNDO6BQ3sW0IbNQsCgfD2pbyw8VT0Mc5Y8qSciQg7vVLkK0XeqjFG8PIL9f9yu
> gazObaPkSXhjVMJOP75CzEZ9UaneUrfag2vOvmBVI6JVU9ITlkvA3V%2Fhttps%253A%25
> 2F%252Fquoteinvestigator.com%252F2011%252F08%252F17%252Fsober-tomorrow
> %252Fdata=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca5aa0fd43f98
> 4a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1%7C0%7C6371
> 35892512149457sdata=w0kMpv2c7bqfh1LXpaS30lU9BQMTS%2B69tIbENs1tA9U
> %3Dreserved=0
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Confidentiality Notice: This e- mail and all attachments may contain 
CONFIDENTIAL information and are meant solely for the intended recipient. It 
may contain controlled, privileged, or proprietary information that is 
protected under applicable law and shall not be disclosed to any unauthorized 
third party. If you are not the intended recipient, you are hereby notified 
that any unauthorized review, action, disclosure, distribution, or reproduction 
of any information contained in this e- mail and any attachments is strictly 
PROHIBITED. If you received this e- mail in error, please reply to the sender 
immediately stating that this transmission was misdirected, and delete or 
destroy all electronic and paper copies of this e-mail and attachments without 
disclosing the contents. This e- mail does not grant or assign rights of 
ownership in the proprietary subject matter herein, nor shall it be construed 
as a joint venture, partnership, teaming agreement, or any other formal 
business relationship.

-

Re: it was 20 years ago today

[McCabe, Ron]

Question about how the year 2000 was handled as we just got hit by a major date 
problem.  I remember that one way to handle the date comparisons was to have 
all the years from 00-19 (or something greater than 19) have a high value so it 
would be greater than the 1990's.  Does anyone remember that?  Was it something 
IBM did although I don't recall putting on any patches for something like that 
so I'm thinking it was something we did.

Thanks,
Ron McCabe
Manager of Mainframe/Midrange Systems
Mutual of Enumclaw


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Wayne Bickerdike
Sent: Thursday, January 2, 2020 11:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

The tale has many variations. Unlikely to have been Bessie Braddock. WC died in 
1965 and was out of politics. It was reputed to be Lady Astor.

On Fri, Jan 3, 2020, 05:03 Seymour J Metz  wrote:

> To put it in context, WC called her ugly *before* she called him drunk.
>
>
> --
> Shmuel (Seymour J.) Metz
> https://nam03.safelinks.protection.outlook.com/?url=http:%2F%2Fmason.g
> mu.edu%2F~smetz3data=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca
> 5aa0fd43f984a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1
> %7C0%7C637135892512149457sdata=XQ0p8EtwOY8eQKAZZ5mVHuyWkk0PVQOAYC
> nk55KHbWA%3Dreserved=0
>
>
> 
> From: IBM Mainframe Discussion List  on
> behalf of Nightwatch RenBand 
> Sent: Thursday, January 2, 2020 11:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today
>
> Hey, Rupert!
> Winston Churchill and the British politician Bessie Braddock.
> Braddock encountered an intoxicated Churchill and said “Sir, you are
> drunk.”
> He replied:And you, Bessie, are ugly. But I shall be sober in the
> morning, and you will still be ugly.
>
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecu
> re-web.cisco.com%2F1OFrGwpGH70rWFs-EMrAUGN6jEySb0De7a6s2QRo2CooV41jBvU
> wt2DA-wvlsUv6Vkl8hQLFeQp838B2YxYNm3bXQYrUEDUbqL6uv0OdtAPbTmK3ntDdPqErj
> -pFyEwMc2ikZQl6Ec00T3S33_smVePsYfwcTRaZY7iKJQBPR83YKqmrpH11xvZ0VdPiqzb
> 3aKAvwkdBC8VF9tCr_ZuzEqFowOpI4HBGUkOfwka_WOra-l-jpRsX-4P_wDQHNN-kLvdk0
> 9SuCPE8frNDO6BQ3sW0IbNQsCgfD2pbyw8VT0Mc5Y8qSciQg7vVLkK0XeqjFG8PIL9f9yu
> gazObaPkSXhjVMJOP75CzEZ9UaneUrfag2vOvmBVI6JVU9ITlkvA3V%2Fhttps%253A%25
> 2F%252Fquoteinvestigator.com%252F2011%252F08%252F17%252Fsober-tomorrow
> %252Fdata=02%7C01%7Crmccabe%40MUTUALOFENUMCLAW.COM%7Ca5aa0fd43f98
> 4a353e7908d78fb7f167%7C5a381f7dcc3d4a93b2cbd2fd072e535a%7C1%7C0%7C6371
> 35892512149457sdata=w0kMpv2c7bqfh1LXpaS30lU9BQMTS%2B69tIbENs1tA9U
> %3Dreserved=0
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Confidentiality Notice: This e- mail and all attachments may contain 
CONFIDENTIAL information and are meant solely for the intended recipient. It 
may contain controlled, privileged, or proprietary information that is 
protected under applicable law and shall not be disclosed to any unauthorized 
third party. If you are not the intended recipient, you are hereby notified 
that any unauthorized review, action, disclosure, distribution, or reproduction 
of any information contained in this e- mail and any attachments is strictly 
PROHIBITED. If you received this e- mail in error, please reply to the sender 
immediately stating that this transmission was misdirected, and delete or 
destroy all electronic and paper copies of this e-mail and attachments without 
disclosing the contents. This e- mail does not grant or assign rights of 
ownership in the proprietary subject matter herein, nor shall it be construed 
as a joint venture, partnership, teaming agreement, or any other formal 
business relationship.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Wayne Bickerdike]

The tale has many variations. Unlikely to have been Bessie Braddock. WC
died in 1965 and was out of politics. It was reputed to be Lady Astor.

On Fri, Jan 3, 2020, 05:03 Seymour J Metz  wrote:

> To put it in context, WC called her ugly *before* she called him drunk.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> 
> From: IBM Mainframe Discussion List  on behalf
> of Nightwatch RenBand 
> Sent: Thursday, January 2, 2020 11:06 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: it was 20 years ago today
>
> Hey, Rupert!
> Winston Churchill and the British politician Bessie Braddock.
> Braddock encountered an intoxicated Churchill and said “Sir, you are
> drunk.”
> He replied:And you, Bessie, are ugly. But I shall be sober in the morning,
> and you will still be ugly.
>
> https://secure-web.cisco.com/1OFrGwpGH70rWFs-EMrAUGN6jEySb0De7a6s2QRo2CooV41jBvUwt2DA-wvlsUv6Vkl8hQLFeQp838B2YxYNm3bXQYrUEDUbqL6uv0OdtAPbTmK3ntDdPqErj-pFyEwMc2ikZQl6Ec00T3S33_smVePsYfwcTRaZY7iKJQBPR83YKqmrpH11xvZ0VdPiqzb3aKAvwkdBC8VF9tCr_ZuzEqFowOpI4HBGUkOfwka_WOra-l-jpRsX-4P_wDQHNN-kLvdk09SuCPE8frNDO6BQ3sW0IbNQsCgfD2pbyw8VT0Mc5Y8qSciQg7vVLkK0XeqjFG8PIL9f9yugazObaPkSXhjVMJOP75CzEZ9UaneUrfag2vOvmBVI6JVU9ITlkvA3V/https%3A%2F%2Fquoteinvestigator.com%2F2011%2F08%2F17%2Fsober-tomorrow%2F
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Seymour J Metz]

To put it in context, WC called her ugly *before* she called him drunk.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Nightwatch RenBand 
Sent: Thursday, January 2, 2020 11:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: it was 20 years ago today

Hey, Rupert!
Winston Churchill and the British politician Bessie Braddock.
Braddock encountered an intoxicated Churchill and said “Sir, you are
drunk.”
He replied:And you, Bessie, are ugly. But I shall be sober in the morning,
and you will still be ugly.
https://secure-web.cisco.com/1OFrGwpGH70rWFs-EMrAUGN6jEySb0De7a6s2QRo2CooV41jBvUwt2DA-wvlsUv6Vkl8hQLFeQp838B2YxYNm3bXQYrUEDUbqL6uv0OdtAPbTmK3ntDdPqErj-pFyEwMc2ikZQl6Ec00T3S33_smVePsYfwcTRaZY7iKJQBPR83YKqmrpH11xvZ0VdPiqzb3aKAvwkdBC8VF9tCr_ZuzEqFowOpI4HBGUkOfwka_WOra-l-jpRsX-4P_wDQHNN-kLvdk09SuCPE8frNDO6BQ3sW0IbNQsCgfD2pbyw8VT0Mc5Y8qSciQg7vVLkK0XeqjFG8PIL9f9yugazObaPkSXhjVMJOP75CzEZ9UaneUrfag2vOvmBVI6JVU9ITlkvA3V/https%3A%2F%2Fquoteinvestigator.com%2F2011%2F08%2F17%2Fsober-tomorrow%2F

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today

[Nightwatch RenBand]

Hey, Rupert!
Winston Churchill and the British politician Bessie Braddock.
Braddock encountered an intoxicated Churchill and said “Sir, you are
drunk.”
He replied:And you, Bessie, are ugly. But I shall be sober in the morning,
and you will still be ugly.
https://quoteinvestigator.com/2011/08/17/sober-tomorrow/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Mike Schwab]

W.C. Fields?  https://en.wikipedia.org/wiki/W._C._Fields

On Tue, Dec 31, 2019 at 2:01 PM Rupert Reynolds  wrote:
>
> Ah . . . sigh . . .
> A story I can tell now:
> One night around the new year, at the end of 1999. I was wondering around
> (client) with a bottle of nice sparkling wine, looking for somewhere to
> keep it cool.
>
> It was a special one-off night shift tacked onto the
> ml llend of a contract. I was to stay until various things had finished
> normally overnight, as expected.
>
> "You're drunk!" said the fella. I recognised him from a manager's meeting.
> I'd had a glass of wine, but I defo wasn't drunk!
>
> I couldn't resist it. I stole a line from an American comedian (I can't
> remember his name) and I said his line loud and proud "Why the Hell not?
> I've been drinking all day!"
>
> His face was a picture :-)
>
> And all he could do, being practical, was to sigh and say "Carry on . . ."
> :-)
>
> It was my last day as a contractor, as I was going to spend some years as a
> single parent of 4, so I never asked for a reference. Perhaps it would have
> read "Got the job done. Appears to drink like a fish." :-)
>
> Rupert
>
>
> On Tue, 31 Dec 2019, 18:26 Chris Hoelscher,  wrote:
>
> > Has it been 20 years since Y2K?? sometimes it seems like last year, other
> > times seems like another lifetime .
> >
> > Thank You,
> > Chris Hoelscher| Lead Database Administrator | IBM Global Technical
> > Services| T 502.476.2538  or 502.407.7266
> >
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: it was 20 years ago today ....

[Rupert Reynolds]

Ah . . . sigh . . .
A story I can tell now:
One night around the new year, at the end of 1999. I was wondering around
(client) with a bottle of nice sparkling wine, looking for somewhere to
keep it cool.

It was a special one-off night shift tacked onto the
ml llend of a contract. I was to stay until various things had finished
normally overnight, as expected.

"You're drunk!" said the fella. I recognised him from a manager's meeting.
I'd had a glass of wine, but I defo wasn't drunk!

I couldn't resist it. I stole a line from an American comedian (I can't
remember his name) and I said his line loud and proud "Why the Hell not?
I've been drinking all day!"

His face was a picture :-)

And all he could do, being practical, was to sigh and say "Carry on . . ."
:-)

It was my last day as a contractor, as I was going to spend some years as a
single parent of 4, so I never asked for a reference. Perhaps it would have
read "Got the job done. Appears to drink like a fish." :-)

Rupert


On Tue, 31 Dec 2019, 18:26 Chris Hoelscher,  wrote:

> Has it been 20 years since Y2K?? sometimes it seems like last year, other
> times seems like another lifetime .
>
> Thank You,
> Chris Hoelscher| Lead Database Administrator | IBM Global Technical
> Services| T 502.476.2538  or 502.407.7266
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

it was 20 years ago today ....

[Chris Hoelscher]

Has it been 20 years since Y2K?? sometimes it seems like last year, other times 
seems like another lifetime .

Thank You,
Chris Hoelscher| Lead Database Administrator | IBM Global Technical Services| T 
502.476.2538  or 502.407.7266


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN