[ADSM-L] 3584, VIO, TSM, and bad eject behavior...
2009-08-30 21:05:37
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>
|
- [ADSM-L] 3584, VIO, TSM, and bad eject behavior...,
Wanda Prather <=
|
Previous by Date: |
Re: [ADSM-L] Seeking wisdom on dedupe..filepool file size client compression and reclaims, Bill Boyer |
Next by Date: |
[ADSM-L] SV: 3584, VIO, TSM, and bad eject behavior..., Christian Svensson |
Previous by Thread: |
Re: [ADSM-L] Seeking wisdom on dedupe..filepool file size client compression and reclaims, John D. Schneider |
Next by Thread: |
[ADSM-L] SV: 3584, VIO, TSM, and bad eject behavior..., Christian Svensson |
Indexes: |
[Date]
[Thread]
[Top]
[All Lists] |
|
|