TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


cli:tmss10logstatsprocess
 
 

TMSS10LogStatsProcess

TMSS10LogStatsProcess processes a TapeTrack Statistics file, apply calculations and produce a report in XML format.

Synopsis

TMSS10LogStatsProcess [-M customer map file] [-N no xml preamble] [-P package map] [-X xml stylesheet] [-c config file] [-i input ttstats file] [-l list stats definition language syntax]

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.

Options

  • -M Customer Description Map File
  • -N No XML preamble (default = false)
  • -P Package Map File
  • -X XML Style Sheet (default = tapetrack.xslt)
  • -c Config File (default = default.ttsdef)
  • -i Input TTSTATS file
  • -l List Stats Definition Laguage syntax (default = false)

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

Example

Command line syntax

TMSS10LogStatsProcess -i 0001.ttstats -M customer.txt  -P package.txt > Billing_0002.xml 

Output

<?xml version="1.0" encoding="ISO8859-1" ?>
<?xml-stylesheet type="text/xsl" href="tapetrack.xslt"?>
<tapetrack_data>
	<item>
		<customer>0001</customer>
		<itemcode>Los Angeles STORAGE_OFFSITE</itemcode>
		<description>CONT Vault Storage Charge</description>
		<count>60</count>
		<cost>0.01</cost>
		<total>0.60</total>
	</item>
	<item>
		<customer>0002</customer>
		<itemcode>Los Angeles STORAGE_OFFSITE</itemcode>
		<description>LTO Vault Storage Charge</description>
		<count>160</count>
		<cost>0.01</cost>
		<total>1.60</total>
	</item>
	<item>
		<customer>0002</customer>
		<itemcode>Los Angeles MOVE_ONSITE</itemcode>
		<description>LTO Deliver to Customer </description>
		<count>4</count>
		<cost>10.90</cost>
		<total>10.90</total>
	</item>
</tapetrack_data>
Changelog
2015-08-24Changed hascontents to contentcount and change contentcount to a filter rather than bool
2015-08-24Added iscontainer and hascontents to the config file filter logic
2015-05-16Added environmental varialbe TMSSCANFILEUNQUALIFIED which will load and check volumes without Customer-ID and Media-ID qualifiers
2015-05-16Added environmental varialbe TMSSSCANFILENOPARSE which will presume scanfile items are only Volumes and not parse them, saving time
2015-05-16When loading scanfile from import definition, added CUSTOMER and MEDIA keywords to set defaults
2015-05-16When loading scanfile from import definition, changed keyword from VOLUME to BARCODE
2015-05-16Added TMSSUNQUALIFIEDVOLUME environmental variable which forces all barcodes to be printed without Customer-ID and Media-ID
2015-05-04Added support for AD passwords to all command line programs (check for environmental variable TMSSNOMD5)
2015-03-16Increased all filter lengths to a maximum of 1024
2014-11-19Changed server argument parser to allow colon in password to support z/OS DD name files
2014-10-26Upgraded development environment from Visual Studio 2012 to Visual Studio 2013
cli/tmss10logstatsprocess.txt · Last modified: 2022/05/31 03:17 by scunliffe