System Programmer Reference › Starting, Ending, and Restarting CA VM:Backup › Starting CA VM:Backup

Starting CA VM:Backup

When you log on to the CA VM:Backup service virtual machine or when the system is autologged, the PROFILE EXEC invokes a startup EXEC file called PROFRUN. For more information about this EXEC, see the CA Mainframe VM Product Manager Reference Guide.

The VMBSYS command performs a routine CA VM:Backup initialization, during which CA VM:Backup does the following:

• Reads the VMBACKUP CONFIG file.
• Verifies that all required system minidisks are linked and formatted.
• Checks the structure of the non-index catalog files and ensures that each catalog file is valid; if catalog index files do not already exist, builds them.
• Verifies that all resource pools are properly defined.
• Checks for devices defined in the virtual address ranges used by CA VM:Backup.
• If CA VM:Backup finds devices that were not detached when CA VM:Backup last ended (because of an abnormal end while a job was running), the devices are detached. For other devices in these ranges, CA VM:Backup marks the addresses in use so that they will not be used.
• Checks the restart recovery minidisk to find out whether any previously running jobs were interrupted and need to be restarted.
• Checks whether any outstanding jobs are waiting to be processed

There are several other ways to initialize CA VM:Backup; this section explains how to do so.