The 3494 docs clearly state that it is the responsibility of the "host
software" to enforce category limits.  I thought that the library
performed this function and still think it should, but it isn't so.

Orville L. Lantto
Datatrend Technologies, Inc.  (http://www.datatrend.com)
121 Cheshire Lane #700
Minnetonka, MN 55305
Email: Orville.Lantto AT dtrend DOT com





Bill Boyer <bill.boyer AT VERIZON DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/18/02 02:40 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: 3494 Volume Stealing


How exactly did you 'steal' it from server A to B? I always thought it was
the responsibility of the library manager component in the 3494 to handle
who owns what. Maybe you should be looking at the code level in the 3494
library manager?? You might want to check out the library manager logs for
around the time when you 'steal' this volume.

Whenever I share a 3494 between multiple TSM servers, I use different
volume
numbering schemes and the CHECKIN command for each server is defined in a
server script with the appropriate VOLRANGE= specified. This is then
scheduled to run daily with an admin command schedule. Then I educate the
client that they should only checkin volumes using the RUN command for the
script I created, or better yet just let the schedule command do it for
them.

Bill Boyer
DSS, Inc.