You want tldtest for that. The only caveat is taht you require the /dev
device name. I am trying to figure out how to convert from user defined name
to this. T he 's i' command in tldtest will list the contents of the CAP.
You can use echo, wc, and pipes to count the number of slots used or free:

example to count the number of free CAP slots: echo "s i"|tldtest -r
/dev/sg/c4t0l0|grep 'full = 0'|wc -l

'full = 0' indicates that the CAP slot if empty. 'full = 1' indicates it is
full.

Remember that if the CAP needs to be scanned, this command can take several
seconds to complete (hardware dependent I'm sure)

Jason

> -----Original Message-----
> From: scott.kendall AT abbott DOT com [mailto:scott.kendall AT abbott DOT com]
> Sent: July 11, 2001 12:39
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] tape eject
> 
> 
> 
> I know there have been many posts on tape eject and there is a script
> available on www.xbpadm-commands.com.
> 
> There was also a solution posted to the "press <RETURN> to 
> continue" message
> seen with vmchange -res -e and NetBackup 3.4.
> 
> My question is this..  how is everyone handling the tape 
> limits for the CAP?
> 
> I would guess that a lot of people are using a while loop 
> within their eject
> script to count the number of ejects and then pause & send a 
> message that the
> CAP is full or are breaking up the list of tapes that is 
> passed to the eject
> script into sizes that their CAP can handle.
> 
> I have multiple robots all with different size CAPs.  I would 
> like a way for
> the script to either check to see if there is an available 
> slot in the CAP
> before ejecting each media or watch for an error and then 
> continue when the
> CAP is emptied.  Is anyone doing anything like this?
> 
> 
> Thanks,
> 
> Scott