Previous Topic: DASD ManagementNext Topic: Authorities


Directory Management

When you create a user ID, a virtual machine definition is added to the CA VM:Director directory database. The definition consists of one or more directory entries which combine to form the virtual machine definition. These directory entries are created based on statements contained in the directory profile and a skeleton file you used to create the user ID.

You can change the contents of directory entries, directly or indirectly, to change the characteristics of a user ID’s workspace. For instance, you can define a user ID’s links to other user IDs’ minidisks through its directory entry or change a user ID’s password or virtual storage size through its directory entry.

CA VM:Director can check the contents of directory entries to verify that security provisions defined by the system administrator are not violated. For example, if you try to change the size of a user ID’s minidisk, CA VM:Director lets you do so only if you are allowed to allocate that much space.

Skeleton Files

Skeleton files are prototype CP directory entries. Control statements in skeleton files specify the components of each user’s virtual machine. They can also contain INCLUDE statements that effectively include the statements from a directory profile in the skeleton file.

When you create a directory entry using a skeleton file, the entry name and password (for USER or IDENTITY entries) placed on the directory entry USER, IDENTITY, or SUBCONFIG record are taken from the command you use to create the directory entry. For example, say there is a skeleton file named PROFUSER SKELETON and its first record is the following:

USER PROFUSER PROFUSER 16M 16M G

If you enter the command vmdirect manage david to create a new user ID named DAVID and specify skeleton PROFUSER when prompted, the first record in DAVID’s directory entry will be:

USER DAVID DAVID 16M 16M G

Skeleton files make it easier to define directory entries with the same characteristics. When you create directory entries by basing them on skeleton files, you are verifying that those entries all have the same characteristics. This is important when you want to standardize user ID capabilities and characteristics.

In contrast to directory profiles, skeleton files are not merely referenced by directory entries; rather, they are copied into the new directory entries for user IDs you create by using skeleton files.

Your CA VM:Director system administrator will let you know the names of any skeleton files you are authorized to use for creating user IDs. Alternatively, your CA VM:Director system administrator may have authorized you to create and use your own skeleton files.

Directory Profiles

In a VM system, you define each user with directory entries in the CP online directory. Control statements in the directory entries specify the user ID, password, and components of each user’s virtual machine.

Directory profiles contain sets of frequently used control statements. Instead of entering the same control statements repeatedly in many directory entries, you can create one directory profile that contains these commonly used control statements. You then add an INCLUDE statement to each directory entry that needs to use the control statements in that directory profile.

Directory profiles offer several advantages over repeating the same control statements in numerous directory entries: