Joni,

I have two ideas that might work for you. The first is to just add
another checkin command with the new volrange to the script. I've not
tried it but I *believe* the second checkin will wait for the first
to complete. The reason I believe this is because I've accidently
issued 2 checkin commands before and the second one seemed to wait on
the first to complete. My other idea is to create another script
containing only the checkin command with the new volrange and have
your operations staff run both.

Good luck,
Rick

At 12:33 PM 2/17/2012, you wrote:

Hi Everyone,

I have a script that I run to return tapes to scratch and pull them
from my IE door which is below, but now I have 2 different ranges of
tapes, so how can I address this?  My new range of tapes is
MN*****.  Any thoughts on how I can get around this or add to the
script so that the operations staff can still run the vault_return
script without issues?

Just let me know.  Thanks in advance!

tsm: CHLN102>q script vault_return f=d
                          Name: VAULT_RETURN
                   Line Number: 5
                       Command: move drm * wherest=vaultr tostate=onsiter
Last Update by (administrator): LIDZR8V
         Last Update Date/Time: 11/30/2011 09:49:54

                          Name: VAULT_RETURN
                   Line Number: 10
                       Command: checkin libvol quantumenc search=bulk
                                 stat=scratch checkl=barcode
                                 volrange=M00000,M00599 waitt=0
Last Update by (administrator): LIDZR8V
         Last Update Date/Time: 02/17/2012 13:30:24

________________________________

This e-mail and any attachments to it are confidential and are
intended solely for use of the individual or entity to whom they are
addressed. If you have received this e-mail in error, please notify
the sender immediately and then delete it. If you are not the
intended recipient, you must not keep, use, disclose, copy or
distribute this e-mail without the author's prior permission. The
views expressed in this e-mail message do not necessarily represent
the views of Highmark Inc., its subsidiaries, or affiliates.