Table of Contents
TMSS10LibraryManager
TMSS10LibraryManager manages Scratch Volume levels within the Target Repository.
Metrics used to monitor Volume levels include Repository capacity, Volumes moving in and out of the Repository, minimum Scratch Volumes required, Repository Scratch levels, available Scratch Volumes from other Repositories and free slot requirements.
Synopsis
TMSS10LibraryManager [-C Customer-ID] [-M Media-ID] [-R Repository-ID] [-S logon string] [-T target repository] [-V volume filter] [-c configuration file] [-e ejection filter] [-f minimum free slots] [-r repository scratch order] [-s minimum scratch volumes]
Options
-CCustomer-ID-MMedia-ID-SThe Logon string argument sets the Server Logon Information-TTarget Repository for Volumes if ejection is required to make room for minimum Scratch quantity. If not specified, no Volumes will be ejected.-VVolume Filter which can be used to filter the traversal of Customer, Media, Volume, Repository and Flag values.-cThe config file argument specifies the path to the Batch Configuration File. The Batch Configuration File allows you to perform advanced traversal of Customer, Media and Volumes, perform advanced Barcode pre and post processing and route program output to syslogd. Configuration File capabilities vary from program to program but the syntax remains the same. In the event that logic is not supported it will simply be ignored.-eVolume ejection exclusion filter-rRepository Scratch Order override. syntax -r “RAC1=0;RAC2=30;RAC3=20” sets Scratch Rack priority to RAC2, then RAC3, excluding RAC1.
If an argument value starts with the value FI:, the value for that attribute will be read from the file name specified immediately after it. For example, if a file named ACME_volumes has the content ACME_*.*, specifying FI:/etc/ACME_volumes will have the same effect as -V ACME.*.*. Using FI: to refer to a file for an attribute value works for all attributes.
If the pattern being matched starts with *LIST: then rather than matching the literal value, each record in the file specified as *LIST:filename will be tested. If one matches the match will succeed.
Technical Support
The TapeTrack Software is commercially supported by a full time help desk staff.
If you are experiencing problems or want some advice on how to configure or use the product please see the Accessing Technical Support page.
Exit Statuses
- zero Program has ended successfully.
- non-zero Program has not ended successfully.
Environment
Files
stdout: Output Reports.
stderr: Diagnostic messages.
stdin: Program input.
Example
Command line syntax
TMSS10LibraryManager -S user:-password@server -C US02 -M LTO -R LIBR
Output
The output of the TapeTrack Library Manager program is described in detail on the page Library Management Report
See Also
Implementing TMSS10LibraryManager
- Changelog
- Cannot load rss feed.