Re: Big fun with Windows 2003 and IBM 3494 libraries

Mark,
 
The IBM Automatied Library Service is a tcp/ip application.
The 3494 won't show up in Windows Device Manager, or the TSM management 
console, because there is no physical cable connection to the 3494 library 
manager; TSM talks to it via IP (usually).
 
The device name you need for TSM is the name you created in the ibmatl.conf 
file.
 
The other thing you have to do is go to the 3494 library maangement console, 
look for the LAN config screen, and put the IP address of the TSM server in 
there.  (Essentially giving the Windows TSM server permission to access the 
3494.)
 
Then look in the driver user's guide for the mtlib utility.
You use mtlib to talk to 3494 libraries, ntutil to talk to the drives.
 
Open a CMD window, type:  mtlib -qL  -l   libname
 
(case sensitive:  -qL is little q big L;  -l libname is little l; libname is 
the name you created in ibmatl.conf)
 
If your connection is working, you'll get back the library info such as # of 
slots, serial#, and a page full of stuff you don't care about.  But it proves 
your connection is working.
 
 
 

________________________________

From: ADSM: Dist Stor Manager on behalf of Mark Stapleton
Sent: Tue 2/13/2007 12:18 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Big fun with Windows 2003 and IBM 3494 libraries



Well, I figured out why the ibmatl install seemed to hang. The ibmatl.readme 
text file comes up during the install, and the install won't finish until you 
close the text file. No documentation on this little gotcha, either.

Sigh.

Now I'm trying to figure out whether the server is talking to the library. (I 
know I'm talking to the tape drives.) I edited the ibmatl.conf file and started 
the IBM Automated Library service. It would appear from the lmcpd.log that the 
connection is successful (also from the 3494a_atl.log), but I'm not seeing the 
device in the Device Manager, or in the Devices Information stanza in the TSM 
management console.

I don't know the ntutil utility very well; does anyone know how to find the 
device name for the library using that?

--
Mark Stapleton (mark.s AT evolvingsol DOT com)
Senior consultant