Previous Topic: VMDIRECT MANAGERS File ReferenceNext Topic: DEFSIZE Record


VMDIRECT MANAGERS File Record

The following records define the limits of a manager’s authority and the default values that CA VM:Director uses when that directory manager performs directory maintenance functions.

Record

Purpose

Use

DEFSIZE

Specifies a directory manager and the default minidisk size that directory manager will allocate.

Optional

 

DEVTYPE

Specifies a directory manager and the directory manager’s default device type for allocating minidisks.

Optional

IDLIMIT

Specifies a directory manager and maximum number of user IDs that directory manager can manage.

Optional

MANAGER

Specifies a directory manager and its default subpool from which to allocate DASD.

Required

SKELETON

Specifies a directory manager and its default directory skeleton.

Required

A record in the VMDIRECT MANAGERS file consists of a record name followed by parameters. Records having an asterisk as the first non–blank character are comments; except for the *ED= special comment. Records beginning with asterisks are ignored for processing. Blank lines are also ignored.

You can include an edit special comment (*ED=) in the VMDIRECT MANAGERS file.

CA VM:Director maintains this record with the following information:

The VMDIRECT MANAGERS file physical line length is 71 characters. The maximum logical line length, a record continued over several lines, in the VMDIRECT MANAGERS file is 255 characters.

If you need to make a record longer than 71 characters:

Example:

The next two lines are read as one record, and not a record and a comment line. They are equivalent to the third line.

MANAGER CLYDE,
* MAIN
MANAGER CLYDE * MAIN

Note: You cannot extend a comment line (a line beginning with an asterisk). If you have a comment that extends beyond one line, make two comment lines.

CA VM:Director reads the VMDIRECT MANAGERS file as part of its initialization process. If it encounters an invalid MANAGER or SKELETON record, it sends a diagnostic message to the CA VM:Director console and to the CA VM:Director system operator. This operator is a user ID you specify on the SYSOPER record in the PRODUCT CONFIG file.

If CA VM:Director encounters a MANAGER record that specifies a user ID that does not appear in the directory, initialization is terminated with the appropriate error messages.

You can edit the VMDIRECT MANAGERS file while CA VM:Director is running using the ADMIN MANAGERS command.

The Sample VMDIRECT MANAGERS File, shows a sample VMDIRECT MANAGERS file. According to this sample file:

The other managers’ authorizations are apparent after reading those for directory manager DIANEC in the entry which follows:

*ED=
* THIS MANAGERS FILE DEFINES THE DIRECTORY MANAGERS FOR THE XYZ
* DIVISION
MANAGER VMANAGER * POOL1 MAIN
   SKELETON VMANAGER GENERAL
   DEVTYPE VMANAGER 3390
   IDLIMIT VMANAGER 65525
   DEFSIZE VMANAGER 2M
MANAGER DIANEC * MAIN
   SKELETON DIANEC GENERAL
   DEVTYPE DIANEC 3390
   DEFSIZE DIANEC 1M
   IDLIMIT DIANEC 10
MANAGER JOE * FINAPOOL
   SKELETON JOE FINANCE
   DEVTYPE JOE 3390
   IDLIMIT JOE 8
   DEFSIZE JOE 2M
MANAGER MARY *DEVLPOOL
   SKELETON MARY DEVELOP
   DEVTYPE MARY 3380
   DEFSIZE MARY 2M
MANAGER DAVE * POOL5
   SKELETON DAVE GENERAL
   DEVTYPE DAVE 3370
   IDLIMIT DAVE 65525
   DEFSIZE DAVE 23M