We were unsuccessful over the weekend in the attempt to test a DR
senario where an alternate TSM assumes responsibility for restoring
data. The problem seems to be related to TSM losing information when
some devconfig info for the 3494 tape libraries are deleted and
recreated in order to adjust the information to correct it for how it
appears on the DR server.

Our production environment has 1 TSM server on AIX, and 2 3494 tape
libraries in alternate sites. TSM accesses the drives via fibre and
switches.
Production:
Library Name     Drive Name       Device Type     On-Line
------------     ------------     -----------     -------------------
IBM3494A         3590RMT0         3590            Yes local
IBM3494A         3590RMT1         3590            Yes local
IBM3494B         3590RMT2         3590            Yes alternate site
IBM3494B         3590RMT3         3590            Yes alternate site
IBM3494B         3590RMT4         3590            Yes alternate site
IBM3494B         3590RMT5         3590            Yes alternate site

lmcp0 Available          LAN/TTY Library Management Control Point
lmcp1 Available          LAN/TTY Library Management Control Point
rmt0  Available 1H-08-01 IBM 3590 Tape Drive and Medium Changer (FCP)
rmt1  Available 1H-08-01 IBM 3590 Tape Drive and Medium Changer (FCP)
rmt2  Available 1Z-08-01 IBM 3590 Tape Drive and Medium Changer (FCP)
rmt3  Available 1Z-08-01 IBM 3590 Tape Drive and Medium Changer (FCP)
rmt4  Available 1Z-08-01 IBM 3590 Tape Drive and Medium Changer (FCP)
rmt5  Available 1Z-08-01 IBM 3590 Tape Drive and Medium Changer (FCP)
rmt6  Defined   1Z-08-01 IBM 3590 Tape Drive and Medium Changer (FCP)
/* Device Configuration */
DEFINE DEVCLASS 3494ATAPE DEVTYPE=3590 FORMAT=DRIVE
ESTCAPACITY=41943040K MOUNTL
IMIT=2 MOUNTWAIT=60 MOUNTRETENTION=5 PREFIX=ADSMVOL LIBRARY=IBM3494A
DEFINE DEVCLASS 3494BTAPE DEVTYPE=3590 FORMAT=DRIVE
ESTCAPACITY=41943040K MOUNTL
IMIT=DRIVES MOUNTWAIT=60 MOUNTRETENTION=5 PREFIX=ADSMVOL
LIBRARY=IBM3494B
DEFINE DEVCLASS ADSMDBBK DEVTYPE=FILE FORMAT=DRIVE
MAXCAPACITY=9437184K
MOUNTLIM
IT=1 DIRECTORY=/var/tsmdbbk SHARED=NO
SET SERVERNAME BACKUP
DEFINE LIBRARY IBM3494A LIBTYPE=349X PRIVATECATEGORY=300
SCRATCHCATEGORY=302 SHA
RED=NO
DEFINE LIBRARY IBM3494B LIBTYPE=349X PRIVATECATEGORY=300
SCRATCHCATEGORY=302 SHA
RED=NO
DEFINE DRIVE IBM3494A 3590RMT0 ONLINE=Yes WWN="5005076300004DAF"
SERIAL="0000000
23294"
DEFINE DRIVE IBM3494A 3590RMT1 ONLINE=Yes WWN="5005076300004D4A"
SERIAL="0000000
80797"
DEFINE DRIVE IBM3494B 3590RMT2 ONLINE=Yes WWN="5005076300002D9B"
SERIAL="0000000
C0629"
DEFINE DRIVE IBM3494B 3590RMT3 ONLINE=Yes WWN="5005076300003904"
SERIAL="0000000
C0614"
DEFINE DRIVE IBM3494B 3590RMT4 ONLINE=Yes WWN="50050763000055D5"
SERIAL="0000000
F4915"
DEFINE DRIVE IBM3494B 3590RMT5 ONLINE=Yes WWN="5005076300002839"
SERIAL="0000000
F4908"
DEFINE PATH BACKUP IBM3494A SRCTYPE=SERVER DESTTYPE=LIBRARY
DEVICE=/dev/lmcp0 ON
LINE=YES
DEFINE PATH BACKUP 3590RMT0 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=IBM3494A DEVIC
E=/dev/rmt0 ONLINE=YES
DEFINE PATH BACKUP 3590RMT1 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=IBM3494A DEVIC
E=/dev/rmt1 ONLINE=YES
DEFINE PATH BACKUP IBM3494B SRCTYPE=SERVER DESTTYPE=LIBRARY
DEVICE=/dev/lmcp1 ON
LINE=YES
DEFINE PATH BACKUP 3590RMT2 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=IBM3494B DEVIC
E=/dev/rmt2 ONLINE=YES
DEFINE PATH BACKUP 3590RMT3 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=IBM3494B DEVIC
E=/dev/rmt3 ONLINE=YES
DEFINE PATH BACKUP 3590RMT4 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=IBM3494B DEVIC
E=/dev/rmt4 ONLINE=YES
DEFINE PATH BACKUP 3590RMT5 SRCTYPE=SERVER DESTTYPE=DRIVE
LIBRARY=IBM3494B DEVIC
E=/dev/rmt5 ONLINE=YES
*----------------------------------------------------------------------------------------------------------------
The emergency DR TSM was expected to restore data from the tape
library
housing the primary storage pools.
DR site and the device have different rmt0 from the production server.
So dev info for the drives and libraries had to be deleted and
redefined.

lmcp1 Available          LAN/TTY Library Management Control Point
rmt0  Available 1Z-08-02 IBM 3590 Tape Drive and Medium Changer (FCP)
rmt1  Available 1Z-08-02 IBM 3590 Tape Drive and Medium Changer (FCP)
rmt2  Available 1Z-08-02 IBM 3590 Tape Drive and Medium Changer (FCP)
rmt3  Available 1Z-08-02 IBM 3590 Tape Drive and Medium Changer (FCP)

The consequence is that although the library showed on TSM, the info
about where the vols resides was lost. a
- q vol   returned info about a volume
- a q content <vol> returned info about a volume
but:
- q libvol showed empty rows for the library.

Anyone have insight, experience, or suggestions related to this
problem?

I am going to try changing the logical names on the devices so they
match the production server and should not require and deletions and
redefginitions of devices.

Larry Clark