Re: 3584 date off by 6 years

2010-01-04 Thread Keith Arbogast
Len, The date and time shown in the Operator Panel are correct despite the futuristic Call Home date. All drives and the accessor seem to be working normally. I intend to open a PMR about the date thing this morning. Keith

Re: 3584 date off by 6 years

2010-01-04 Thread adms mailing list
:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 3584 date off by 6 years Len, The date and time shown in the Operator Panel are correct despite the futuristic Call Home date. All drives and the accessor seem to be working normally. I intend to open a PMR about the date thing this morning. Keith

Re: 3584 date off by 6 years

2010-01-04 Thread Oscar Kolsteren
Same here. Got two 3584 libraries showing this futuristic date!!! -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of adms mailing list Sent: 04 January 2010 14:37 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 3584 date off by 6 years Hi Keith

Re: 3584 date off by 6 years

2010-01-04 Thread David Longo
!!! -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of adms mailing list Sent: 04 January 2010 14:37 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 3584 date off by 6 years Hi Keith Both the 3584's at my current site are showing the same date

Re: 3584 date off by 6 years

2010-01-04 Thread Evans, Bill
-Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Oscar Kolsteren Sent: Monday, January 04, 2010 7:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 3584 date off by 6 years Same here. Got two 3584 libraries showing this futuristic date

Re: 3584 date off by 6 years

2010-01-04 Thread Neil Schofield
Keith We've got the same issue on two TS3500 libraries (running code v8870 and v7420). It's funny as we were only reminiscing last week about the fun we'd had 10 years ago fighting the millennium bug. We even joked about having systems today that weren't 'decade compliant', but dismissed the

Re: 3584 date off by 6 years

2010-01-04 Thread Jánský Vítězslav
: Re: [ADSM-L] 3584 date off by 6 years Keith We've got the same issue on two TS3500 libraries (running code v8870 and v7420). It's funny as we were only reminiscing last week about the fun we'd had 10 years ago fighting the millennium bug. We even joked about having systems today that weren't

Re: 3584 date off by 6 years

2010-01-04 Thread Harvey, Bruce T
- | From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of | Jánský Vítezslav | Sent: Monday, January 04, 2010 12:13 PM | To: ADSM-L@VM.MARIST.EDU | Subject: Re: [ADSM-L] 3584 date off by 6 years | | Well its simple ... | | 0x9 in binary = 9 in decimal | 0x10 in binary = 16 in decimal

Re: 3584 date off by 6 years

2010-01-04 Thread Howard Coles
...@vm.marist.edu] On Behalf Of Jánský Vítezslav Sent: Monday, January 04, 2010 11:13 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 3584 date off by 6 years Well its simple ... 0x9 in binary = 9 in decimal 0x10 in binary = 16 in decimal y2k bug strikes back. V.J. -Original Message- From

Re: 3584 date off by 6 years

2010-01-04 Thread Harry Redl
Hi, yes - seems like Binary Coded Decimal problem - not only IBM libraries are affected. Harry From: Fred Johanson f...@uchicago.edu To: ADSM-L@VM.MARIST.EDU Sent: Mon, January 4, 2010 8:48:37 PM Subject: Re: [ADSM-L] 3584 date off by 6 years We'll just

Re: 3584 date off by 6 years

2010-01-04 Thread Fred Johanson
: [ADSM-L] 3584 date off by 6 years Hi, yes - seems like Binary Coded Decimal problem - not only IBM libraries are affected. Harry From: Fred Johanson f...@uchicago.edu To: ADSM-L@VM.MARIST.EDU Sent: Mon, January 4, 2010 8:48:37 PM Subject: Re: [ADSM-L] 3584

Re: 3584 date off by 6 years

2010-01-04 Thread Harmeet Sian
: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Fred Johanson Sent: Tuesday, 5 January 2010 9:11 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 3584 date off by 6 years Do you mean libraries from other makers, or other IBM hardware? Our mainframe guys have their eyes open

Re: 3584 date off by 6 years

2010-01-04 Thread Richard Sims
Windows Mobile also has what is now being called The Year 2016 Bug (search on Google).

Re: 3584 date off by 6 years

2010-01-03 Thread Keith Arbogast
Len: I saw into the future using the Web Specialist interface, rather than the Operator Panel. I would be interested to know if you have seen differences between Library Error logs displayed by the two. Best wishes, Keith Arbogast Indiana University

Re: 3584 date off by 6 years

2010-01-03 Thread Len Boyle
: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Keith Arbogast Sent: Sunday, January 03, 2010 7:04 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 3584 date off by 6 years Len: I saw into the future using the Web Specialist interface, rather than the Operator Panel. I would

3584 date off by 6 years

2010-01-02 Thread Keith Arbogast
The first Call Home of the new year for our 3584 had a 2016/01/01 date stamp on it. It is on firmware level 9590. I don't know the resolution for this yet. When I do I'll post again. Keith Arbogast Indiana University

Re: 3584 date off by 6 years

2010-01-02 Thread Nick Laflamme
On Jan 2, 2010, at 3:57 PM, Keith Arbogast wrote: The first Call Home of the new year for our 3584 had a 2016/01/01 date stamp on it. That's what I call pro-active service! rimshot Nick

Re: 3584 date off by 6 years

2010-01-02 Thread Len Boyle
@VM.MARIST.EDU Subject: [ADSM-L] 3584 date off by 6 years The first Call Home of the new year for our 3584 had a 2016/01/01 date stamp on it. It is on firmware level 9590. I don't know the resolution for this yet. When I do I'll post again. Keith Arbogast Indiana University