Step 2. Tailor the Product Deployment

Installation Guide › Deploying the Product › Deploying the Product for the First Time › Step 2. Tailor the Product Deployment

Step 2. Tailor the Product Deployment

The VMDEFINE command creates the entry and then enters a NAMES panel for you to view or modify the definitions. You may tailor the characteristics of the CA VM:Backup product server machine on the VMSERVER NAMES panel. Name panel usage is described in the IBM NAMES command documentation and HELP file. To change entries just overtype the values and press PF6 to change the entry. Press PF3 to exit the panel.

Required Tags

The tag names in this section are required. Although changing the device numbers is permitted, CA strongly suggests that you use the standard device numbers. Do not remove any of the following tags:

RUNTIME
PUBLIC
LOCAL
CATDISK
POOLDISK
CHECKDISK
SYSDISK
RPTDISK

Removable Tags

The tag names in this section define values for the minidisks. The process allocates the minidisks by default to hold an alternate and a previous version of the product materials. Having three sets of product code makes it easy to switch between product releases or between fix levels. If you do not want to define this disk space, insert a leading asterisk in the values for the following tags:

ALTRUNTIME
ALTPUBLIC
PREVRUNTIME
PREVPUBLIC

Commenting the values prevents the definition of the minidisks during the deployment.

Step 3. Allocate Resources for Production Use

The product materials installation process creates the ppfname PLANINFO file. The file contains the directory entries for user IDs created for each product deployment and a list of the disk space that is needed.

You defined the name of the product server virtual machine when you issued the VMDEFINE command in Step 1. You can alter the definition to add optional product server disks. In this step, combine the following components:

The definition in the VMSERVER NAMES file
The product user ID configuration and disk size information from the PLANINFO file

This action creates the defined server machine and allocates the disk space for the product deployment.

For more information about how the VMALLOC command is configured and used, see the Allocating User ID Entries and Disk Space appendix. Issue the command as the appendix instructs.

To create the user ID and allocate the disk space, enter the following command:

VMALLOC SERVER name

name: Specifies the user ID of the product server machine to deploy.

You can perform extra steps to finish the allocation task using DIRECTXA or a Directory Manager product. This action depends on the description of the configuration in Allocating User ID Entries and Disk Space appendix.

Step 4. Deploy the Product Materials

The steps in this section create a usable product instance. Copy the installed product build materials to the disk areas you allocated in the previous step.

Step 4.1. Copy Product Materials to Runtime Areas

To collect the configuration information from your VM system and create a set of status files, enter the VMRMDS command. These files are used to create an initial exclusion file. Enter the command as follows:

VMRMDS

To verify the product server disks, create default configuration files, and copy product materials to the runtime disk space, enter the VMDEPLOY command.

VMDEPLOY name INIT

name: Specifies the user ID of the product server machine being deployed.
INIT: Specifies that a new server is being deployed. The process places a set of default configuration files and a startup PROFILE EXEC file on the disk. The LOCAL tag in the VMSERVER NAMES file entry defines the disk for the files. The disks that are defined on the DEPLOY tag are populated with product materials.

Note: For more information about deploying optional Product Materials, such as the HELP files, see the CA Mainframe VM Product Manager Reference Guide.

Step 4.2. Enter LMP Statements

To define the LMP (License Management Program) key for this product, follow the procedure in the CA Mainframe VM Product Manager Reference Guide.

Step 4.3 Establish Required Authorizations

If an External Security Manager product is used at your installation, establish the required authorizations for the deployed user IDs. The following table shows the authorizations that the default user IDs for this product need.

Deployed User ID	Required Authorizations
VMBACKUP	Read access to VMANAGER 0195 minidisk. Read access to VMANAGER 01FF minidisk.

Deployed User ID

Required Authorizations

VMBACKUP

Read access to VMANAGER 0195 minidisk.

Read access to VMANAGER 01FF minidisk.

Step 5. Start CA VM:Backup

The following procedures assume that the CA VM:Backup interface for CA VM:Tape is not implemented. The VMBACKUP CONFIG file does not contain a PRODUCT VMTAPE record.

To start CA VM:Backup, use the following procedure:

Log on to VMBACKUP and respond NO to the message:

VMISTA259R *

Do you want to start VMBACKUP now?

Prepare the checkpoint minidisk. Enter the following commands:

ACCESS 1D1 K

RESERVE CHECK POINT K

Respond YES to the prompt:

DMSRSV603R RESERVE will erase all files on disk K(1D1). Do 
you wish to continue?
Enter 1 (YES) or 0 (NO).

Prepare the sample template and exception files. Enter the following commands:
```
COPYFILE * TEMPDIST D = TEMPLATE A 
COPYFILE * XCEPDIST D = XCEPT A 
```
Start the server by entering:
```
PROFILE
```

Respond YES to the message:

VMISTA259R *

Do you want to start VMBACKUP now?

Disconnect and leave the server running by entering:
```
#CP DISCONN
```
The CA VM:Backup server initializes, and displays this message when the initialization is complete:
```
CA VM:Backup is ready to use: ddmmmyy hh:mm:ss.
```

Step 6. Test CA VM:Backup

The following procedures assume that the CA VM:Backup interface for CA VM:Tape is not implemented. The VMBACKUP CONFIG file does not contain a PRODUCT VMTAPE record.

Step 6.1. Running a Full Backup Job

Note: These procedures can vary depending on the tape management product you are using.

To run a full backup, perform the following procedure:

Log on to VMANAGER.
Ensure that two standard tapes are labeled B00001 and B00002 and are available for your CA VM:Backup test. If not, use the CMS TAPE WVOL1 command to initialize the tapes with standard labels.
You are running a backup job using templates that you prepared while starting CA VM:Backup. If you want to look at these templates, follow these steps:
1. Display the System Administrator Main Menu by entering:
```
VMBACKUP
```
2. Select Manage Job Templates.
3. Next to the DAILY or WEEKLY template name you want to view, enter:
```
UPD
```
4. When you finish reviewing the template, press PF3 three times to return to CMS.
Submit the full backup of the VMANAGER 191 minidisk by entering:
```
VMBACKUP SUBMIT WEEKLY
```
You are prompted for the volser of the tape to use for the backup job. Reply by entering:
```
VMBACKUP REPLY n B00001
```
where:

n

Indicates the request number of the CA VM:Backup prompt.
CA VM:Backup confirms the volser by repeating the request. Reply by entering:
```
VMBACKUP REPLY m B00001
```
where:

m

Indicates the new CA VM:Backup request number.
CA VM:Backup confirms the volser and then sends a tape mount request to the tape operator console:
```
VMBMNT0623I MOUNT CART B00001 AT 310...
```
Mount tape B00001 on a drive.
Attach the tape drive to VMBACKUP as 310 by entering:
```
ATTACH raddr  TO VMBACKUP AS 310
```
where:

raddr

Specifies the real address of the tape device.

310

Denotes the virtual address at which CA VM:Backup has requested the drive.

When CA VM:Backup completes the job, it sends output listings and a NOTE file to the VMANAGER virtual reader. The NOTE file indicates whether any problems were encountered during the backup job.

Step 6.2. Running an Incremental Job

Log on to VMANAGER.
Change the date of the PROFILE EXEC file to the current date, causing it to be backed up in this incremental backup job. Enter the following command:
```
COPYFILE PROFILE EXEC A
```
Generate and submit the incremental backup job by entering:
```
VMBACKUP SUBMIT DAILY
```
You are prompted for the volser of the tape to be used for the backup job. Reply by entering:
```
VMBACKUP REPLY n B00002
```
where:

n

Indicates the request number of the CA VM:Backup prompt.
CA VM:Backup confirms the volser by repeating the request. Reply by entering:
```
VMBACKUP REPLY m  B00002
```
where:

m

Indicates the new CA VM:Backup request number.
CA VM:Backup confirms the volser and sends a tape mount request to the tape operator console:
```
VMBMNT623I MOUNT CART B00002 AT 310...
```
Mount tape B00002 on a drive.
Attach the tape drive to VMBACKUP as 310 by entering:
```
ATTACH raddr  TO VMBACKUP AS 310
```
where:

raddr

Denotes the real address of the tape device.

310

Denotes the virtual address at which CA VM:Backup has requested the drive.

When CA VM:Backup completes the job, it sends output listings and a NOTE file to the VMANAGER virtual reader. The NOTE file indicates whether any problems were encountered during the backup job.

Step 6.3. Restoring a File

Log on to VMANAGER.
To display a list of all files that are backed up from the VMANAGER 191, enter the following command:
```
VMBACKUP RESTORE (ALL
```
Select the files that you want to restore by typing r in the REQ column to the left of the files. Press PF9 to submit the restore request.
On the next screen, indicate that you want the process to return the files to the VMANAGER virtual reader: enter 1 on the command line. When VMBACKUP receives the job, a tape mount request displays at the tape operator console.
Mount the tape on a drive.
Attach the tape drive to VMBACKUP as 310 by entering:
```
ATTACH raddr  TO VMBACKUP AS 310
```
where:

raddr

Indicates the real address of the tape device.

310

Denotes the virtual address at which CA VM:Backup has requested the drive.

Step 6.4. Putting the DAILY and WEEKLY Templates Into Production

This section explains the steps that you must take to incorporate the DAILY and WEEKLY templates into your backup procedures. You used the DAILY and WEEKLY templates, which CA provides, when you verified the installation of CA VM:Backup, previously.

Optionally modify an exclusion file that identifies minidisks you do not want backed up.
Optionally modify the exception file that comes with CA VM:Backup.
To identify what you want backed up, customize the DAILY and WEEKLY templates. Also optionally specify the exclusion and exception files.

Step 6.5. Exclusion File

The exclusion file identifies the minidisks that you do not want backed up during your system backups. You issue the VMIBBE command to create an exclusion file automatically. You can later modify the exclusion file with the Manage Exception/Exclusion Files option of the System Administrator Main Menu.

Identify the exclusion file in your WEEKLY and DAILY backup job templates.

Create an exclusion file named VMBACKUP $XCLUDE. This file includes the following components:

Volumes
User IDs
The virtual addresses of full-pack minidisks and other CP areas on your system

The file contains exclusion records suitable as input for the VMBACKUP IMPORT command.

Logon VMANAGER.
To collect configuration information from your VM system and to create a set of status files, enter the VMRMDS command. These files are used to create the EXCLUDE statements. Enter the command as follows:
```
VMRMDS
```
To create the VMBACKUP $XCLUDE file on the VMANAGER A-disk, enter the following command:
```
VMIBBE
```
Enter the following command:
```
VMBACKUP IMPORT VMBACKUP $XCLUDE
```

Note: For information about the IMPORT command and the format of exclusion files, see the CA VM:Backup System Programmer Reference Guide.

Step 6.6. Exception File

This section presents one of the things you can do with the exception file.

Note: For more information about the exception file, see the CA VM:Backup System Administration Guide.

Deployment loads a default CA VM:Backup exception file to the CA VM:Backup runtime minidisk. As one of the Start CA VM:Backup steps, you copied the file to the CA VM:Backup local minidisk. This file is VMBACKUP XCEPT. The exception file quiesces other CA components to back them up. You can modify the exception file with the Manage Exception/Exclusion Files option of the System Administrator Main Menu.

Identify the exception file in your WEEKLY and DAILY backup job templates.

Step 6.7. Customizing the DAILY and WEEKLY Templates

You want to do the following actions:

Change the DAILY and WEEKLY templates you used in the installation verification tests run earlier
Incorporate them into your set of system backup templates

Perform the following procedure:

Display the System Administrator Main Menu by entering:
```
VMBACKUP
```
Select Manage Job Templates.
To the left of the DAILY or WEEKLY template you want to view, enter:
```
UPD
```
The system presents you with the first of a series of template management screens.
(Optional) Go to the Select Guidelines portion of the template management screens. In the Exclusion File field type the name of the exclusion file. If you identify an exclusion file in either the DAILY or WEEKLY template, identify that same exclusion file in the other template.
(Optional) Go to the Select Guidelines portion of the template management screens. In the Exception File field type the name of the exception file. If you identify an exception file in either the DAILY or WEEKLY template, identify that same exception file in the other template.
Go to the Input Guidelines portion of the template management screens. In the Restricted to Records area, change the value USERID VMANAGER 0191 to one of the following formats:
- Change to the following format:
```
userid * *
```
  where userid is a literal. The first asterisk means all user IDs, and the second asterisk means all minidisks. CA VM:Backup back up all minidisks for all users on your system except the minidisks you identified in the exclusion file.
- Change to one or more instances of the following format:
```
userid user-id vaddr
```
  where userid is a literal. User-id is a user ID to be backed up, and vaddr is the virtual address of one of the minidisks of that user ID.
  
  You can use pattern matching for user IDs and virtual addresses.

Step 7. Make the Product Available

After you install and test the product, make it available to your users. For more information about making the product available, see the "Releasing Products to Users" section in the CA Mainframe VM Product Manager Reference Guide.