Congratulations, I know somewhat where you are.  Life changed greatly when we
added the 12slot door to our 3583 nine months ago.
My checkin script (written in kornshell for AIX) does some different thing than
you have listed.

For the most part when I changed my script to "search=bulk", I was not prepared
for the system "request"ing me to load the bulk i/o door.  With some kornshell
magic, I was able to query the requests and issue a "reply" that would allow the
checkin process to complete without my help.

My script does the following functions: (with the help of DRM)

1)  unmount any idle tapes that have not timed out.
2)  "label" any new tapes that have not been previously used.  Previously used
tapes would result in a warning message.
3) checkin all tapes attempting to scratch them.  Any copy pool tapes that are
not in onsite retrieve status will result in a warning message
4) checkin all remaining tapes in the bulk loader with status private
(search=yes)
5) checkin all tapes that exist in the library to the status of private.
(search-yes)  This is just in case some tape was placed manually or somehow
checked out erroneously)
6) This step is tricky, so I will list the select.  The step selects any tape in
the library that is in a courierretreive or vaultretrieve status and stores them
in a variable.
"SELECT LIBVOLUMES.VOLUME_NAME FROM DRMEDIA DRMEDIA, LIBVOLUMES LIBVOLUMES \
WHERE DRMEDIA.VOLUME_NAME = LIBVOLUMES.VOLUME_NAME AND \
((DRMEDIA.STATE='COURIERRETRIEVE') OR (DRMEDIA.STATE='VAULTRETRIEVE'))"
7) Issue move drmedia to the selected volumes changing them to onsiteretrieve.
This will scratch them since they are checked in.
8) Next I select any tape that is in the library as private with "last.use"
empty.  These are usually old backupsets or db backups
9) issue an update volume to the tapes from the previous step changing them to
scratch status.

This process takes care of 99% of the tapes I place in the library.  I review
the library daily to confirm that all volumes are in the correct status.
Occasionally, someone will insert a tape before it expires, so I just check them
back out manually.

The checkout process is much easier.  I just added "remove=bulk" and the process
works great.

PS.  If you require the AIX checkout script, place $10 with your request in an
email to me at jpenderg AT watsonpharm DOT com (just kidding about the $10).  
Please
send your request personally (not in a reply), because I am sure everyone does
not want to see messages saying "send it to me too"





"Coats, Jack" <Jack.Coats AT BANKSTERLING DOT COM> on 11/05/2002 05:12:24 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Joseph Pendergast/Corona/Watson)

Subject:  Fun with a bulk door on a tape library



Whoopee!  Just got an upgrade to my tape library (IBM 3583).  Put in some
more slots, tape drives and a bulk loader door.  The door now has 12 slots
in it, up from 1.

I have tried some things, but I know there are come command shortcuts for
using the bulk loader door efficiently.
What I need to do is to be able to:

1. Checking copypool and old database backup tapes back into the library.

2. Checkout copypool and database backup tapes to be sent offsite.

Currently I use
   checkin libv <library> <volume> stat=scr
      or checkin libv <library> <volume> stat=pri
   checkout libv <library> <volume>

And I assume that all I need to do is put
   checkin libv <library> stat=scr search=bulk
      or checkin libv <library> <volume> stat=pri search=bulk
   checkout libv <library> <volume> rec=bulk

The one for checking in with stat=pri seems wrong somehow.
Hints or suggestions on 'proper' use of a bulk door?

Other than just getting the syntax down and working my objective is to:
1. In the morning, have my database backup tape and all copypool tapes in
   my library to be put into the bulk door.
2. Load the bulk door with the incoming database backup tape and returning
   copypool tapes (ready for reuse), and have everything update and put away
   properly.

My environment is WinNT 4.0 with TSM 4.1.3 in the process of moving to
(upgrading)
Win2K Server with TSM 4.2 (can't go further because I still have Novell
4.1.1 clients).

TIA ... Jack