A group is specified on a nonsystem volume set to limit access to files. A group is contained within one volume set or one single volume.
The system is designed to gain access to groups through the system volume set, even though the groups exist on the nonsystem volume set. Therefore, entries must be made in two directories (system and nonsystem directory), and two NEWGROUP commands are necessary.
Example: Creating a Group |
 |
This example shows how to create a group on a nonsystem volume set.
Log on to the new account.
At the system prompt, create the group, DATABASE, on the system volume set with the HOMEVS parameter. HOMEVS is only used with groups. HOMEVS tells the file system to place the files of a group on a particular volume set.
:HELLO MGR.ORDERS
:NEWGROUP DATABASE;HOMEVS=PROD_SET
|
Figure 3-3 Creating the Group on the System Volume
![[Creating the Group on the System Volume]](img/LG200047_014.gif)
Next create the group on the nonsystem volume set with the ONVS parameter. ONVS refers to the nonsystem volume. Refer to the MPE/iX Commands Reference Manual Volumes 1 and 2 (32650-90003 and 32650-90364) for a detailed description of this command.
:NEWGROUP DATABASE;ONVS=PROD_SET
|
Account information is stored on the system volume. This means that even if the PROD_SET volume set is removed from the system, you can still log on to the CUST account, which is on a different volume set. This also means that if the PROD_SET volume set is moved to another system, the account structure (groups and accounts) moves with it and must also exist on the new system volume set's directory in order to access these files. System account information (like passwords and capabilities) resides on the system volume set, as does user information.
Figure 3-4 Creating a Group on the Nonsystem Volume
![[Creating a Group on the Nonsystem Volume]](img/LG200047_015.gif)
Use the REPORT command to verify account and group information.
:REPORT @.ORDERS
ACCOUNT FILESPACE=SECTORS CPU-SECONDS CONNECT-MINUTES
/GROUP COUNT LIMIT COUNT LIMIT COUNT LIMIT
ORDERS 421 ** 0 ** 0 **
/DATABASE 392 ** 0 ** 0 **
/PUB 29 ** 0 ** 0 **
:REPORT @.ORDERS;ONVS=PROD_SET
ACCOUNT FILESPACE=SECTORS CPU-SECONDS CONNECT-MINUTES
/GROUP COUNT LIMIT COUNT LIMIT COUNT LIMIT
ORDERS 392 ** 0 ** 0 **
/DATABASE 392 ** 0 ** 0 **
/PUB 0 ** 0 ** 0 **
|
