| Parameter | Description | Required | Default |
|---|---|---|---|
| -u <User Name> | Specifies the User Name that the utility uses to connect to the TARA Server. Currently the user names allowed are administrator and user. The user just has the read-only privilege. Example TARAJobRM -u administrator |
Yes | Not Applicable |
| -p <password> | Specifies the password for the user name the utility uses to connect to the TARA Server. Example TARAJobRM -u administrator -p xjmT94Rs |
Yes | Not Applicable |
| -P <port> | Specifies the port number that the TARA server is running on. The default port is 54323. If the TARA Server port is changed to a different number, this option has to be specified with the correct TARA Server port number. Example TaraJobRM -u administrator -p xflu7pqr -j MyBackupJob -P 55555 |
No | 54323 |
| -e <path to encoded password file> | Specifies the path to the file that contains the encoded password to the User Name. Example TARAJobRM -u administrator -e C:\Teradata\tara.pwd The file containing the encoded password is created during the post-install of the TARA Server, and is located in the TARA server bin directory: \Teradata\TARA\server\bin). The name of the file is tara.pwd. If the utility is running on a machine different from the TARA server, tara.pwd can be copied to the machine, and the path to the file containing the encoded password can be specified. If you need to recreate a file with the encoded password, run the TARALogonGen executable located in the TARA server bin directory: \Teradata\TARA\server\bin. Enter the password and the tool creates a tara.pwd. This file contains the encoded password. |
Yes | Not Applicable |
| -S <script_name> | Specifies a script name, or the name of a file that has a list of script names to delete. If specifying a single file, the name of the file must immediately follow -S. If specifying a file that has a list of script names, precede the file name with -f (see the -f <input_filename> parameter). In the file containing the list:
|
This parameter, or the -J <jobfile_name> parameter, is required. | |
| -f <input_filename> | Specifies the name of a file that has a list of script or job names to delete. | No | |
| -J <jobfile_name> | Specifies a job name, or the name of a file that has a list of jobfile names to delete. If specifying a single file, the name of the file must immediately follow -J. If specifying a file that has a list of jobfile names, precede the file name with -f (see the -f <input_filename> parameter). In the file containing the list:
To obtain a list of all jobs in the TARA server repository, use tarajobquery -L. Then, copy those jobfiles to be deleted into a file for TARAJobRM.
|
This parameter, or the -S <script_name> parameter, is required. | |
| -s <TARAServer_name> | This option is not required if the TARA server resides on the same BAR server where this utility is launched. Otherwise, the TARAServer_name value is the name of the BAR server running TARAServer. | No | |
| -v | Specifies the verbosity of the utility after parameter validation. The range is 0 to 3. | No | 1 |
| -F | For a TARA JobFile only. Forces removal of the JobFile even if there is a valid image in the Tivoli image catalog. | No |
When a single job or script is deleted, the deletion occurs after parameter validation, without verification of the file to be deleted. In contrast, when multiple scripts or jobs are deleted, the user is prompted by the following line:
X files will be deleted. Is this correct? (y,n)