MANAGERS File Reference
You define whom your directory managers are and describe the range of their authority to cacc through the svm MANAGERS file. Each directory manager user ID at your site is represented by a group of records in this file. This group of records can include any of the records summarized in the table that follows.
You define whom your directory managers are and describe the range of their authority to
VMSECUREMANAGERS file. Each directory manager user ID at your site is represented by a group of records in this file. This group of records can include any of the records summarized in the table that follows.
In addition to defining directory managers in this file, you must also authorize these directory managers to use certain
VM:Securecommands, such as ADDENTRY, so that they can use the specifications you enter here. For instance, directory managers cannot use the default device type (which you specify on a DEVTYPE record in this file) unless you let the directory managers create user IDs. You do so by authorizing the directory managers to use the ADDENTRY command.
For more information about creating and enabling directory managers, see Directory Managers.
The following records define the limits of a manager’s authority and the default values that
VM:Secureuses when that directory manager performs directory maintenance functions.
Specifies a directory manager and the default minidisk size that directory manager will allocate.
Specifies a directory manager and the directory manager’s default device type for allocating minidisks.
Specifies a directory manager and maximum number of user IDs that directory manager can manage.
Specifies a directory manager and its default subpool from which to allocate DASD.
Specifies a directory manager and its default directory skeleton.
A record in the
VMSECUREMANAGERS 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
VM:Securemaintains this record with the following information:
- Date and time of last update of theVMSECUREMANAGERS file
- User ID that last updated the file
- Process used to update the file
- Date the file was first updated
VMSECUREMANAGERS file physical line length is 71 characters. The maximum logical line length, a record continued over several lines, in the
VMSECUREMANAGERS file is 255 characters.
If you need to make a record longer than 71 characters:
- Split it over as many physical lines as you need, breaking it between record words.
- Place a comma at the end of each physical line. The comma is the record continuation character and continues the record to the next line that contains text.This is true even if the next line begins with an asterisk, which is otherwise the symbol for a comment line.
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
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.
VMSECUREMANAGERS file as part of its initialization process. If it encounters an invalid MANAGER or SKELETON record, it sends a diagnostic message to the
VM:Secureconsole and to the
VM:Securesystem operator. This operator is a user ID you specify on the SYSOPER record in the PRODUCT CONFIG file.
VM:Secureencounters 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
VMSECUREMANAGERS file while
VM:Secureis running using the ADMIN MANAGERS command.
VMSECUREMANAGERS File, shows a sample
VMSECUREMANAGERS file. According to this sample file:
- DIANEC can allocate an unlimited amount of disk space in the MAIN subpool, as indicated by the asterisk on the MANAGER record
- She is authorized to use the GENERAL skeleton file
- Her default device type is 3390 and displays on the Manager Selection screens
- She can manage up to 10 user IDs at any given time
- When DIANEC uses the Application Program Interface (API) commands and automatic disk allocation, the default size of a new minidisk is 1 MB
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