Previous Topic: Restoring from the BKUP MinidiskNext Topic: Servant Facility


Reconfiguring CA VM:Director

You need to reconfigure CA VM:Director when you change your z/VM system or change the users that use your z/VM system. For instance, adding new directory managers, granting users authority to use new commands, or adding new DASD require that you reconfigure CA VM:Director.

You can reconfigure most aspects of CA VM:Director at almost any time by using the ADMIN command or the CONFIG command.

The ADMIN command changes directory manager information, directory pool definitions, directory profiles, skeleton files, and SFS managers; the CONFIG command changes users’ authorizations to CA VM:Director commands, descriptions of DASD that CA VM:Director is responsible for managing, CA VM:Director processing behavior, and descriptions of SFS if you use it.

Make these configuration changes by editing (or adding or removing) records in various configuration files or by filling in screen fields. The configuration feature you change determines which configuration file you change or which screens you fill in.

Configuration feature

Command that lets you change this feature

Directory manager

ADMIN MANAGERS

Global definitions used during directory processing (for example, default machine mode for any user directory entry that does not contain a MACHINE statement)

ADMIN GLOBALS

POSIX group information

ADMIN POSIX

SFS manager

ADMIN SFSMGRS

Skeleton file

ADMIN SKELETON skelname

Directory pool’s master definition

ADMIN POOL poolname

Directory profile

ADMIN PROFILE profname

User authorizations to use commands

CONFIG AUTHORIZ

Descriptions of DASD that CA VM:Director manages†

CONFIG DASD

Product processing behavior

CONFIG PRODUCT

Security

CONFIG SECURITY

Servant Facility

CONFIG PRODUCT

SFS file pools or user storage groups

CONFIG SFS

† Although allocating minidisks and serializing these allocation requests are configuration changes, they must be done only through the MANAGE command and other CA VM:Director features that are designed to automate DASD management.

You can make most of these configuration changes while CA VM:Director is running. They are applied to CA VM:Director dynamically and take effect as soon as you save them. Others require that you first terminate CA VM:Director. These changes are applied to CA VM:Director when you restart it after making those changes.

Note: For more information about which records can be added with the CONFIG command and which records have to be added manually after CA VM:Director is terminated, see Configuration Files and Records.