Re: checkin command

2003-02-24 Thread Bob Booth - UIUC
I do it every day. I think you need to have the 'devt=3590' option for the 3494. checkin libv libname volname status=scratch devt=3590 checkl=no or checkin libv libname search=yes status=scratch devt=3590 checkl=no bob On Mon, Feb 24, 2003 at 04:01:21PM -0600, Tommy Templeton wrote: Does

Re: checkin command

2003-02-24 Thread Fred Johanson
You need DEV=tape or whatever. At 04:01 PM 2/24/2003 -0600, you wrote: Does this command work in a 3494 environment? Does there have to be any conditions to use it. The last time I tried to run it, I didn't have very good success. I could have been doing something wrong. checkin libvol 3494vts

Re: checkin command

2003-02-24 Thread Kason Leung
It looks like you're trying to check in a single volume. In that case, you'll need to specify the devtype parameter in your checkin command. This is what we do to checkin a single tape: checkin libvol 3494A vol # devtype=3590 status=scratch I'm assuming your 3494 has 3590 drives in it. Kason

Re: checkin command

2003-02-24 Thread Tommy Templeton
: Monday, February 24, 2003 4:15 PM Subject: Re: checkin command It looks like you're trying to check in a single volume. In that case, you'll need to specify the devtype parameter in your checkin command. This is what we do to checkin a single tape: checkin libvol 3494A vol # devtype=3590

Re: checkin command

2003-02-24 Thread Tommy Templeton
, February 24, 2003 4:42 PM Subject: Re: checkin command We have 3590e tapes and I'm trying to incorporate this command into those server command scripts on the TSM server. I'm trying to put together an offsite backup process. We've been doing our offsite process all wrong and I'm trying