Re: 3583 Meltdown

2005-04-02 Thread Jurjen Oskam
On Fri, Apr 01, 2005 at 01:57:56PM -0600, Bill Kelly wrote: I heard, both Jurjen and I have problems open with IBM hardware support (personally, I suspect a firmware problem, but obviously that's just an uneducated guess). I'm now running on 4AP0, a non-released version. The 'silly'

Re: 3583 Meltdown

2005-04-02 Thread Jurjen Oskam
On Fri, Apr 01, 2005 at 02:10:45PM -0600, Rushforth, Tim wrote: [3584 TapeAlerts] But we too were getting too many of these useless errors so we decided to turn tape alert off and only use if we suspect a problem. (Perhaps we should leave tape alert on but not report on any of the

3583 Meltdown

2005-04-01 Thread Curtis Stewart
Hi everyone, Here's an interesting little piece of activity log from one of my remote TSM servers Gotta like TapeAlert. Other than being an amusing way to start my day, everything checks out OK and I can't believe it. 1. The 6AM job is a copy stgpool operation. 2. Despite the TapeAlert

Re: 3583 Meltdown

2005-04-01 Thread Bill Kelly
On Fri, 1 Apr 2005, Curtis Stewart wrote: Here's an interesting little piece of activity log from one of my remote TSM servers Gotta like TapeAlert. Other than being an amusing way to start my day, everything checks out OK and I can't believe it. [...lots of bogus TapeAlerts omitted...]

Re: 3583 Meltdown

2005-04-01 Thread Stapleton, Mark
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Stewart Here's an interesting little piece of activity log from one of my remote TSM servers Gotta like TapeAlert. Other than being an amusing way to start my day, everything checks out OK and I can't believe it.

Re: 3583 Meltdown

2005-04-01 Thread Rushforth, Tim
on but not report on any of the errors ...) We are on TSM 5.2.2.4 on Windows with SCSI LTO1 and LTO2 in 3584's. Tim Rushforth City of Winnipeg -Original Message- From: Bill Kelly [mailto:[EMAIL PROTECTED] Sent: Friday, April 01, 2005 1:58 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: 3583 Meltdown