The only way I found to reliably get back the tape drives after the
Linux TSM server guest was ipl'ed under zVM was to
delete/define the drives in TSM. From what I understand san discovery
using Linux/390 under zVM does not work.
The following is the script I use:
DELETE PATH SERVER1 DRIVE1 SRCT=SERVER DESTT=DRIVE LIBRARY=LIBR1
DELETE DRIVE LIBR1 DRIVE1
DELETE PATH SERVER1 DRIVE2 SRCT=SERVER DESTT=DRIVE LIBRARY=LIBR1
DELETE DRIVE LIBR1 DRIVE2
DELETE PATH SERVER1 DRIVE3 SRCT=SERVER DESTT=DRIVE LIBRARY=LIBR1
DELETE DRIVE LIBR1 DRIVE3
DELETE PATH SERVER1 DRIVE4 SRCT=SERVER DESTT=DRIVE LIBRARY=LIBR1
DELETE DRIVE LIBR1 DRIVE4
def drive libr1 drive1
def path server1 drive1 srct=server destt=drive libr=libr1 devi=/dev/IBMtape0
def drive libr1 drive2
def path server1 drive2 srct=server destt=drive libr=libr1 devi=/dev/IBMtape1
def drive libr1 drive3
def path server1 drive3 srct=server destt=drive libr=libr1 devi=/dev/IBMtape2
def drive libr1 drive4
def path server1 drive4 srct=server destt=drive libr=libr1 devi=/dev/IBMtape3


On Mon, Jan 11, 2010 at 2:40 PM, Lee, Gary D. <GLEE AT bsu DOT edu> wrote:
> Yesterday, we appear to have lost one of our fiber attached ts1120 drives.
>
> TSM on sles9 running as a guest in zvm
> Server v5.4.4.
> Tapes are in a 3494 library.
>
> The problem is that lin_tape assigns devices /dev/IBMtape0 /dev/IBMtape1 etc. 
> in order of attachment to tapes.
> If any one but the last in the list does not attach, this screws up the tsm 
> path definitions, and all subsequent drives will not function.
>
> How do I get around this in the future if possible?
>
> Gary Lee
> Senior System Programmer
> Ball State University
> phone: 765-285-1310
>
>