TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • tmss10batchloader
cli:tmss10batchloader

Table of Contents

TMSS10BatchLoader

TMSS10BatchLoader creates Customer, Media and Repositories by loading a Configuration file into the TapeTrack Database.

Synopsis

TMSS10BatchLoader [-c configuration file] [-S logonstring]

Options

  • -c The config file argument specifies the path to the Batch Configuration File.
  • -S Logon string argument sets the Server logon information.

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.

Editable Fields

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

  1. zero Program has ended successfully.
  2. non-zero Program has not ended successfully.

Environment

Files

stderr: Diagnostic messages.

Example

Configuration File

Configuration file to create two Customers with Attributes:

Customer 0001

Customer 0002

Download Sample Configuration file. 

  setup=
  {
     customers=
     (
        { 
            id="US01"; description="New York Data Center";
  
            media=
            (
               { 
                   id="LTO"; description="LTO Cartridge";
  
                   repositories=
                 (
                       { id="LIBR"; description="Library"; type=3; next="OFFS"; },
                       { id="OFFS"; description="Iron Mountain"; type=2; next="LIBR"; },
                       { id="DEST"; description="Destroyed"; type=6; },
                       { id="HOLD"; description="Legal hold"; type=4; }
                   )
               },
               { 
                   id="3490"; description="IBM 3490 Cartridge";
  
                   repositories=
                   (
                       { id="LIBR"; description="Library"; type=3; next="OFFS"; },
                       { id="OFFS"; description="Iron Mountain"; type=2; next="LIBR"; }
                   )
               }    
            )
        },
        { 
            id="US02"; description="Los Angeles Data Center";
  
            media=
            (
               { 
                   id="LTO"; description="LTO Cartridge";
  
                   repositories=
                   (
                       { id="LIBR"; description="Library"; type=3; },
                       { id="OFFS"; description="Iron Mountain"; type=2; }
                   )
               },
               { 
                   id="3490"; description="IBM 3490 Cartridge";
  
                   repositories=
                   (
                       { id="LIBR"; description="Library"; type=3; },
                       { id="OFFS"; description="Iron Mountain"; type=2; }
                   )
               }    
            )
        }
     );
  };

Command line syntax

TMSS10BatchLoader -S user:-password@localhost -c master.cfg

Output Results

Configuration Files - Minimising Duplicate Code

When creating multiple Customers with identical Media Types and/or Repositories it is possible to create a configuration file with these Attributes and include it in the master configuration file to save duplication of code blocks.

To create two customers, US01 and US02, with:

A configuration file may “include” the contents of another file using an include directive.

This directive has the effect of in-lining the contents of the named file at the point of inclusion.

An include directive must appear on its own line in the input. It has the form:

@include “filename”

Any backslashes or double quotes in the filename must be escaped as ‘\\’ and ‘\“’, respectively.

Configuration Files

master.cfg

setup= 

{
   customers=
   (
      { 
          id="US01"; description="New York Data Center";
          @include "include.cfg"    
      },
      { 
          id="US02"; description="Los Angeles Data Center";
          @include "include.cfg"  
      }
   );
};
include.cfg
          media=
          (
             { 
                 id="LTO"; description="LTO Cartridge";

                 repositories=
                 (
                     { id="LIBR"; description="Library"; type=3; next="OFFS"; },
                     { id="OFFS"; description="Iron Mountain"; type=2; next="LIBR"; }
                 )
             },
             { 
                 id="3490"; description="IBM 3490 Cartridge";

                 repositories=
                 (
                     { id="LIBR"; description="Library"; type=3; next="OFFS"; },
                     { id="OFFS"; description="Iron Mountain"; type=2; next="LIBR"; }
                 )
             }    
          )

Command line syntax

TMSS10BatchLoader -S user:-password@localhost -c master.cfg

Output Results

Changelog
2021-05-24Fixed bug when using TMSSLEVELNAME and TMSSNOLEVELSLOT variables (#127)
2020-11-24Added support for JSON output
2019-03-30Added support for option_autocontainer setting in media type scope
2019-02-25Added support for HTML output
2019-02-25Added new program
2019-02-25Added support for flag_autocontainer setting in media type scope
2019-02-25Added fast forward code to reduce runtime
2019-02-25Added return code list to end of all command line programs that use the TapeTrack API
2019-02-24Changed server argument parser to allow colon in password to support z/OS DD name files
2019-02-24Added support for Excel output
cli/tmss10batchloader.txt · Last modified: 2022/05/31 00:16 by scunliffe

Page Tools