If you are using VMTBUILD to build the TMC and the Audit files, protect against data loss from DASD failures by putting the TMC and Audit files on separate real DASD volumes.
Be sure that CA VM:Tape is not running before you run VMTBUILD from the CA VM:Tape user ID.
Important! If the TMC you are building is shared, shut down all CA VM:Tape systems that share the TMC before you run VMTBUILD. The system from which you run VMTBUILD should be shut down last or you will need to reaccess the TMC minidisk before you run VMTBUILD.
If input to VMTBUILD is a CA VM:Tape backup of a TMC or Audit file, FILEDEF commands must use the same label type that was used when the file was backed up.
Note: For more information about example of using the utility, see Recovering the TMC.
Be sure the specified or default configuration file resides on an accessed minidisk because VMTBUILD uses it to obtain the SERIES records and filenames and filetypes of the output files.
Be sure the TMC and Audit output files specified in the configuration file do not exist or have been renamed before executing VMTBUILD. Make a backup copy of the current TMC and Audit files before running VMTBUILD.
Important! If you do not provide the current TMC as input to the VMTBUILD utility, all current TMC information will be lost. This could result in data loss, because saved tapes will no longer be protected; they will be in scratch or deleted status and available to be used again.
|
Copyright © 2013 CA.
All rights reserved.
|
|