cli:tmss10sync
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cli:tmss10sync [2017/06/17 20:06] – [Description] Gerard Nicol | cli:tmss10sync [2025/07/04 04:53] (current) – [Examples] Scott Cunliffe | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== TMSS10Sync ====== | ====== TMSS10Sync ====== | ||
| Synchronize an input file or ODBC connection data with a TapeTrack Framework Server. | Synchronize an input file or ODBC connection data with a TapeTrack Framework Server. | ||
| + | |||
| + | <note tip>For further details including requirements, | ||
| ===== Synopsis ===== | ===== Synopsis ===== | ||
| '' | '' | ||
| configfile] [-d deffile] [-l] [-p] [-s] [-t]'' | configfile] [-d deffile] [-l] [-p] [-s] [-t]'' | ||
| ===== Description ===== | ===== Description ===== | ||
| - | '' | + | '' |
| between text files, CSV files and ODBC connections to update commonly used TapeTrack database fields. | between text files, CSV files and ODBC connections to update commonly used TapeTrack database fields. | ||
| In addition to being able to synchronize data, the program can also perform complex date calculation and | In addition to being able to synchronize data, the program can also perform complex date calculation and | ||
| - | string | + | String |
| The program relies on three separate software engines that are built one on top of the other. | The program relies on three separate software engines that are built one on top of the other. | ||
| - | - **INI Parse Engine** This component is responsible for reading the Definition File, parsing the processing directives, resolving variables and including any embedded Definition File sections. | + | - **INI Parse Engine** This component is responsible for reading the Definition File, parsing the processing directives, resolving variables, and including any embedded Definition File sections. |
| - | - **Import Engine** This component is responsible for reading data from the import file or ODBC connection, extracting data into respective fields and performing any data manipulation. | + | - **Import Engine** This component is responsible for reading data from the import file or ODBC connection, extracting data into respective fields, and performing any data manipulation. |
| - **Sync Engine** This component responsible for updating the TapeTrack Server with any fields which have been specified to be updated. | - **Sync Engine** This component responsible for updating the TapeTrack Server with any fields which have been specified to be updated. | ||
| ===== Options ===== | ===== Options ===== | ||
| - | The options which apply to the TMSS10Sync command are: | + | The options which apply to the TMSS10Sync command are: |
| - | -S The logonstring | + | |
| - | user: | + | * '' |
| - | In the event that this argument is not passed the default will be batch: | + | * '' |
| - | By default the password value will be treated as the path to a file which contains a single record | + | * '' |
| - | representing the password, rather than the password itself. | + | * '' |
| - | If you wish the password value to be the literal password (rather than a file) the password should be | + | * '' |
| - | prepended with a dash (fred: | + | * '' |
| - | You can also have the program read the password as the first record of stdin by prepending the | + | * '' |
| - | password with a plus symbol (fred: | + | * '' |
| - | In the event that the password is all upper case and 32 characters in length, the password will be | + | * '' |
| - | considered an MD5 hash of the password and passed to the server without subsequent MD5 hashing. | + | * '' |
| - | -c The configfile | + | * '' |
| - | 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 | + | <note tip> |
| - | the event that logic is not supported it will simply be ignored. | + | |
| - | TMSS10Sync | + | |
| - | 2 | + | |
| - | The following example will set the default Customer-ID and Media-ID for all scanned barcodes: | + | |
| - | barcodes = | + | |
| - | { | + | |
| - | defaults={ customer-id=" | + | |
| - | }; | + | |
| - | -A This argument sets the attribute | + | |
| - | of attributeindex | + | |
| - | inbuilt Description field. Values of 1 through 200 represent user-defined Extended Attribute values. | + | |
| - | -F This argument instructs | + | |
| - | formatted report on STDOUT | + | |
| - | establishing the offset and length of the fields that are being synchronized from a text file. No other | + | |
| - | processing will be preformed. | + | |
| - | -M This argument instructs | + | |
| - | synchronization as it would in the regular update mode but instead of performing any updates the | + | |
| - | program will write a list of proposed update fields for each record to the STDIN. | + | |
| - | Special Note | + | |
| When running in Dump Mode the program will only run the INI Parse Engine and the Import | When running in Dump Mode the program will only run the INI Parse Engine and the Import | ||
| Engine. It will not run the Sync Engine. As a result, any functionality that relies on the Sync | Engine. It will not run the Sync Engine. As a result, any functionality that relies on the Sync | ||
| Engine, such as the Barcode Parse Option will not be invoked. Further, functions that relate | Engine, such as the Barcode Parse Option will not be invoked. Further, functions that relate | ||
| to data interpretation such as date parsing will also not be run. | to data interpretation such as date parsing will also not be run. | ||
| - | -T This argument instructs the program to set the Do Not Slot flag for each updated Volume. | + | |
| - | -a This argument instructs the program to add any new Volumes to the TapeTrack database. In the event | + | To run data through |
| - | that this argument is not specified and newly encountered Volumes will be skipped and added to | + | </ |
| - | the Not-Added Count. | + | |
| - | -d This argument sets the path to the Import Definition File. The Import Definition file is responsible | + | |
| - | for instructing the program on how to interpret the input file or ODBC connection. This argument is | + | |
| - | required and defaults to the file default.ttidef. | + | |
| - | -l This argument instructs the program to list all of the supported processing directives, which will be | + | |
| - | written to STDOUT. A list of valid ODBC Drivers and DSNs will also be listed. No further processing | + | |
| - | is performed. | + | |
| - | -p This argument instructs to Sync Engine to pass the value in the the VOLUME field to TapeTrack' | + | |
| - | Barcode Parsing Engine, where it will be split into the CUSTOMER, MEDIA and VOLUME fields. | + | |
| - | Barcode Parsing can also be further managed using the barcode section of the Configuration File. | + | |
| - | -s This argument instructs the program to automatically set the SLOT field to the relative record number | + | |
| - | of the record being processed. | + | |
| - | -t This argument instructs the program to run in Test Mode. In Test Mode all three engines will be | + | |
| - | invoked, but no updates will be performed. Test Mode differs from Dump Mode in that Dump Mode | + | |
| - | will not run the Sync Engine while Test Mode will, but without performing updates. | + | |
| ===== Exit Status ===== | ===== Exit Status ===== | ||
| - | zero Program has ended successfully. | + | * **zero** Program has ended successfully. |
| - | TMSS10Sync | + | * **non-zero** Program has not ended successfully. |
| - | 3 | + | |
| - | non-zero Program has not ended successfully. | + | |
| ===== Environment ===== | ===== Environment ===== | ||
| - | TMSSSERVERPROXY If defined the program will route all TapeTrack TCP/IP traffic through | + | |
| - | a HTTPS proxy. The value of the variable should be in the format | + | |
| - | user: | + | |
| - | TMSSAPILOGDIR. | + | |
| - | TMSSAPILOGDIR If defined the program will write out a trace file to this directory. | + | |
| - | TMSSPWPATH When no password value is passed in the logon string the program will look for | + | |
| - | the password in file \etc\tapetrack\user, | + | |
| - | passed in the logonstring. If you wish to change this default path, you can | + | |
| - | set the path in TMSSPWPATH. | + | |
| - | TMSSNOMD5 If defined the program will not MD5 hash passwords before sending them to the | + | |
| - | TapeTrack Server. This is required when relying on Windows Active Directory | + | |
| - | authentication. It should be noted that although the password is not being hashed, | + | |
| - | it is still being encrypted during transmission. | + | |
| ===== Files ===== | ===== Files ===== | ||
| - | stdout Formatted output, Record Dump output or Scan File Output. | + | * '' |
| - | stderr Diagnostic messages. | + | * '' |
| - | stdin Sync input file. | + | * '' |
| ===== Examples ===== | ===== Examples ===== | ||
| - | Example 1. TMSS10Sync: | + | List supported Processing Directives. |
| - | [gnicol@z1090 ~]$ TMSS10Sync -l < syntax.txt | + | <code plain;> |
| - | Example 2. TMSS10Sync: | + | [jsmith@z1090 ~]$ TMSS10Sync -l < syntax.txt |
| - | [gnicol@z1090 ~]$ TMSS10Sync -M < input.txt | + | </ |
| - | Example 3. TMSS10Sync: | + | Run program in Dump Mode. |
| - | [gnicol@z1090 ~]$ TMSS10Sync -F 10 < input.txt > output.txt | + | <code plain;> |
| + | [jsmith@z1090 ~]$ TMSS10Sync -M < input.txt | ||
| + | </ | ||
| + | Produce a formatted listing with a ruler every 10 records. | ||
| + | <code plain;> | ||
| + | [jsmith@z1090 ~]$ TMSS10Sync -F 10 < input.txt > output.txt | ||
| + | </ | ||
| + | |||
| + | ===== See Also===== | ||
| + | |||
| + | [[technote/ | ||
| + | --> Changelog | ||
| + | [filterrss http:// | ||
| + | <-- | ||
cli/tmss10sync.1497729978.txt.gz · Last modified: 2025/01/21 22:07 (external edit)
