ADSM-L

[ADSM-L] SV: 3584, VIO, TSM, and bad eject behavior...

2009-08-31 04:08:53
Subject: [ADSM-L] SV: 3584, VIO, TSM, and bad eject behavior...
From: Christian Svensson <Christian.Svensson AT CRISTIE DOT SE>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 31 Aug 2009 10:03:22 +0200
Hi Wanda,
I know what you mean... As consultant our minds can get confused some times.
But try to use REMOVE=BULK instead. :)


Best Regards
Christian Svensson

Cell: +46-70-325 1577
E-mail: Christian.Svensson AT cristie DOT se
Skype: cristie.christian.svensson
________________________________________
Från: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] f&#246;r Wanda 
Prather [wprather AT JASI DOT COM]
Skickat: den 31 augusti 2009 03:04
Till: ADSM-L AT VM.MARIST DOT EDU
Ämne: 3584, VIO, TSM, and bad eject behavior...

Well, I"m confused again.
Just set up TSM for a customer with a TS3500 (3584).
Three logical partitions in the library, one for a for VTS, 1 for mainframe,
1 for TSM.
ALMS installed, VIO enabled.
TSM partition has 4 drives, 255 VIO slots.
Have assigned the TSM tape volser range to the TSM partition.

TSM is 6.1 on Windows.
Getting weird behavior when we do a CHECKOUT or a MOVE DRMEDIA with
REMOVE=YES

Sometimes on the CHECKOUT, TSM activity log shows the tapes checked out and
ejected successfully, and the tapes appear in the library I/O door as
expected.

Other times on the CHECKOUT, TSM activity log shows the tapes checked out
and ejected successfully, and the tapes aren't in the I/O door.  But looking
at the  3584 operator panel we see "volume vvvvvv ejected", followed by
"volume vvvvvv inserted".  Looks to me like the 3584 VIO is grabbing the
tapes as they are checked out, and putting them back in....

Has anybody experienced behavior like this?  Seems like a firmware problem
to me, or is there something I'm missing in the partition setup?

W

<Prev in Thread] Current Thread [Next in Thread>