Modifying configuration file

An example of the TMVERIFY.CONFIG file is included in the sample files that are installed with Tape Manager. An example of the configuration file is shown below.

* This is the parameter file for the TMVERIFY EXEC, which provides              
* a database verification function for IBM Tape Manager for               
* z/VM (5697-J08).                                                              
*                                                                               
* Caution: the database verification is intended as a diagnostic tool,          
* to be run only when problems with the tape database integrity are             
* suspected, and with the Tape Manager main server shut down. For large         
* inventories, the process may be lengthy, and the userid running TMVERIFY      
* may require large amounts of virtual storage (100M or more). This is          
* because the entire tape inventory is read, verified, and indexed in           
* storage.                                                                      
*                                                                               
* On start up, it will read a configuration file (this file), to obtain          
* the parameters for the run.                                                   
*        
*                
*                                                                               
* (list of configuration parameters follows) 

The parameters in the sample TMVERIFY.CONFIG file are listed in the table below. The values are specified using this format:

PARAMETER_NAME = VALUE

To specify a null value for a parameter, use this format:

PARAMETER_NAME = 
Table 1. Parameters in TMVERIFY.CONFIG
Parameter Description Example
Errors_to Provides a list of users to which any error messages generated by the TMVERIFY utility will be sent. User IDs are typed after the equal sign (=) and are separated by one or more blanks. The line may be continued as necessary. If this parameter is omitted or set to null, error messages will be sent to the console. Errors_to = SAMARAK
Error_action Determines whether TMVERIFY will stop if an error is encountered or, if possible, skip the tape in question and continue. The value for Error_Action can be one of the following:
  • STOP
  • CONTINUE
The default is CONTINUE.
Error_action = CONTINUE
Verbosity Determines how much informational output will be produced. Note that all warning output is always produced unless those warnings have been suppressed by an IGNORE for the section in which they occur.

Verbosity may be one of the following:

  • HIGH
  • MEDIUM (default)
  • LOW
Note: Using HIGH adds at least one line of output for every tape in the inventory. Be cautious about using HIGH if you have a large tape inventory.
Verbosity = Medium
TM_Userid (Required) Identifies the user ID that owns the disks to which TMVERIFY will link in order to access and verify the Tape Manager database. Normally this is the Tape Manager main server user ID. TM_userid = XMTMM
Database_disk_1 (Required) Identifies the virtual address of the TM_Userid to which TMVERIFY will link to access the Tape Manager database files. Usually this address is 200. Database_disk_1 = 200
Database_disk_2 (Required) Identifies the virtual address of the TM_Userid to which TMVERIFY will link to access the Tape Manager database files. Usually this address is 210. Database_disk_2 = 210
Config_disk (Optional, but recommended) Identifies the virtual address of the TM_Userid to which TMVERIFY will link to access the Tape Manager SYS CONFIG file. Usually this address is 198.

If this address is not provided, TMVERIFY will continue, but will not validate media types found in the tape or pool inventory files against those defined to Tape Manager in the SYS CONFIG file.

Config_disk = 198

The next several parameters specify the action to take when an error in a database record is found. Unless otherwise noted, the options are:

  • IGNORE. Do nothing.
  • WARN. Send a message to the console and to any user IDs listed in the "Error_to" parameter in the TMVERIFY.CONFIG file.
  • CORRECT. Send the same message as WARN but, where possible, also attempt to correct the error.

Many errors are not correctable, and there may be implications to correcting those that are. For example, invalid date fields can be corrected to a default value, but that may potentially invalidate reporting by date. CORRECT should only be used in consultation with IBM® Technical Support.

Table 2. More parameters in TMVERIFY.CONFIG
Parameter Description
Invalid_tape_inventory_records Specifies the action to take when an error is found in a record in the SYS TAPE file: IGNORE, WARN, or CORRECT.

Example:

Invalid_tape_ inventory_records = WARN
Invalid_pool_volume_records Specifies the action to take when an error is found in a pool file: IGNORE, WARN, or CORRECT. Using CORRECT generally results in rebuilding this file from the SYS TAPE data.

Example:

Invalid_pool_volume_records = WARN