System Programmer Reference › Customizing CA VM:Backup › Reconfiguring CA VM:Backup

Reconfiguring CA VM:Backup

As part of initialization, CA VM:Backup reads the VMBACKUP CONFIG file, which resides on the CA VM:Backup 191 minidisk. This file contains records that specify configuration options for CA VM:Backup. These options do the following:

• Define tape handling options, such as whether operators can override tape expiration dates
• Specify how long CA VM:Backup should wait for a response to a message and how frequently CA VM:Backup should issue a reminder message
• Define job processing controls, such as the number of jobs CA VM:Backup can run concurrently and whether CA VM:Backup should process user restore requests immediately or hold them for execution later
• Define CA VM:Backup user authorizations
• Create, update, and delete resource pools
• Identify SFS file pools to CA VM:Backup
• Enable or disable the interfaces to other CA products
• Activate the Surrogate facility
• Add a DASDtape minidisk
• Configure the AUTOCAT record
• Specify the virtual address of any of the system minidisks
• Specify character case (upper or lower) for messages, reports, or screens

You can manually edit VMBACKUP CONFIG to change any of these configuration options. To do so, you must first bring down the CA VM:Backup system, then use an editor such as XEDIT to edit the VMBACKUP CONFIG records, then reinitialize CA VM:Backup to have the changes take effect. Configuration File Records describes each configuration file record in detail.

You can also use system administrator screens to change the first six configuration options listed above. When you change configuration options through these screens, CA VM:Backup dynamically updates the appropriate configuration file records and the changes take effect immediately; you do not have to reinitialize CA VM:Backup.

During initialization, if CA VM:Backup finds that a configuration file record is in error, it displays a diagnostic message on the CA VM:Backup system console and does not initialize.