Be sure the VM user ID that issues the VMTBKP command is authorized as a CA VM:Tape operator, because VMTBKP issues a VMTAPE SUSPEND command.
Be sure the VMTAPE CONFIG file resides on an accessed minidisk, because VMTBKP uses it to obtain the filenames and filetypes of the TMC and Audit files.
You must issue three CMS FILEDEF commands before executing VMTBKP:
The ddname TMCBKP1 is the primary TMC backup file. The device type specified must be tape or disk. The output can be blocked, but the blocking factor must be a multiple of 340.
The ddname TMCBKP2 is the alternate TMC backup file. The device type specified must be tape, disk, or dummy. If the output is blocked, the blocking factor must be a multiple of 340.
The ddname AUDITBKP is the Audit file backup file. The device type specified must be tape, disk, or dummy. The output can be blocked, and the blocking factor must be a multiple of 370.
If any of the output backup files go to tape and you use CA VM:Tape to do the mounts, you must mount the tape before you issue the VMTBKP command. This is because VMTBKP suspends CA VM:Tape operations during the backup process.
The Audit minidisk must be linked MW, because VMTBKP must write to the minidisk to save the primary backup file information and to reinitialize the Audit file. The TMC minidisk can be linked read-only, because VMTBKP does not write to the TMC. Both the TMC and the Audit minidisks must be accessed before you issue the VMTBKP command. During VMTBKP operation, the TMC and Audit minidisks are reaccessed after VMTBKP suspends CA VM:Tape to guarantee that the latest versions of the TMC and Audit file are backed up.
If you intend to use the VMTBACK EXEC to run VMTBKP, be sure the VMTLIBR 1B0 work disk is accessed read/write. To do this, add a LINK and an ACCESS statement to your VMTBACK EXEC. If you do not have a VMTLIBR 1B0 work disk, ask your directory maintenance personnel to create one for you.
