TMSS10LogStatsExtractDB [-C customer map file] [-H bill for daily highwater] [-R date range] [-c customer filter] [-h database home directory] [-m bill for multiple locations in one day] [-o output directory] [p seconds between progress markers] [-v verbose output]
TMSS10LogStatsExtractDB creates an Extract file for each Customer from the Journal database.
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.
| 2017-01-30 | Fixed bug where extract would lockup database |
| 2016-12-21 | Enhanced argument parser to allow arguments in format *FI:filename that allows loading of arguments from a file |
| 2015-08-24 | Changed hascontents to contentcount and change contentcount to a filter rather than bool |
| 2015-08-24 | Added iscontainer and hascontents to the config file filter logic |
| 2015-05-16 | Added environmental varialbe TMSSCANFILEUNQUALIFIED which will load and check volumes without Customer-ID and Media-ID qualifiers |
| 2015-05-16 | Added environmental varialbe TMSSSCANFILENOPARSE which will presume scanfile items are only Volumes and not parse them, saving time |
| 2015-05-16 | When loading scanfile from import definition, added CUSTOMER and MEDIA keywords to set defaults |
| 2015-05-16 | When loading scanfile from import definition, changed keyword from VOLUME to BARCODE |
| 2015-05-16 | Added TMSSUNQUALIFIEDVOLUME environmental variable which forces all barcodes to be printed without Customer-ID and Media-ID |
| 2015-05-04 | Added support for AD passwords to all command line programs (check for environmental variable TMSSNOMD5) |
| 2015-04-07 | Reverted database from 6.1.19 to 5.3.28 please contact support before upgrading |
| 2014-11-19 | Changed server argument parser to allow colon in password to support z/OS DD name files |
| 2014-10-26 | Upgraded development environment from Visual Studio 2012 to Visual Studio 2013 |
| 2014-08-14 | Upgrade database from 6.0.20 to 6.1.19 |