Step 5. Start CA VM:Director

Installation Guide › Deploying the Product › Deploying the Product for the First Time › Step 4. Deploy the Product Materials › Step 5. Start CA VM:Director

Step 5. Start CA VM:Director

Before a CA VM:Director server can be used, the directory database disk must be initialized. During the first logon of a newly installed CA VM:Director server, the PROFILE EXEC will display messages on how to initialize the database. You will be returned to CMS command mode and be directed to take the steps to initialize the database. Follow this procedure:

Logon to VMDIRECT.
When prompted to start the server, enter No.
Using your knowledge of your system, verify the accuracy of the DASD CONFIG file that VMDEPLOY created on the VMDIRECT 191 disk. Check the VOLUME, EXTENT, and IGNORE records that were added to make sure they reflect the correct state of your system. Update these records if necessary. For more information about the statements in the DASD CONFIG file, see the CA VM:Director Reference Guide.
Obtain a current copy of the CP source directory for this VM system. It is usually a file named USER DIRECT. The source directory file you provide in this step must be accurate and current. If your source directory changes between the time you build the CA VM:Director directory database, and the time you place CA VM:Director into production, you must rerun the VMXGNR utility. Run the VMXGNR utility using the USER DIRECT file in the following steps.
Create a VMXEXIT1 EXEC user exit program to provide the name of a Directory Manager user ID for each user being added to the directory database disk. Place this file on the VMDIRECT server A-disk. For more information about the advanced use of this user exit, see the chapter “User Exit Reference” in the CA VM:Director Reference Guide. The simplest possible VMXEXIT1 program can be made by entering these 3 lines in an editor:
```
/* VMXEXIT1 */
Push ‘VMANAGER’
Exit 0
```
Access the VMDIRECT directory database disk and run the VMXGNR utility by issuing the following commands:
```
ACCESS 1B0 U
VMXGNR dirfn dirft dirfm U VMXEXIT1 EXEC
```
Where:
- dirfn dirft dirfm is the file ID of the USER DIRECT file
- U is file mode letter where the directory database disk is accessed
If you intend to use the CA VM:Director ASSIGN or CHANGE commands and you are using the CA VM:Director SFS user administration feature, make sure the following record is present. Otherwise, skip this step.
```
‘ACCESS 393 filemode’
```
where filemode is an unused filemode.

The ACCESS command, along with the LINK record you verified in Step 3, links CA VM:Director to the MAINT minidisk on which the IBM-supplied FILEPOOL EXEC resides. This is normally the MAINT 193 minidisk. CA VM:Director uses the FILEPOOL EXEC to rename file spaces. Enter file on the XEDIT command line to save your changes to the PROFILE.
Start the CA VM:Director server by issuing the command:
```
PROFILE
```
When the startup sequence completes, and CA VM:Director asks whether you want to start the server, enter the startup option:
```
SOURCE
```
If you receive error messages during startup about minidisk overlaps, you must define additional IGNORE records or take other action, such as relocating or redefining one of the minidisks, before CA VM:Director will start properly.