Table 2: Rules for Managing HP 3000 Capabilities

Table 2: Rules for Managing HP 3000 Capabilities

Rules for Capabilities Examples

1. Programs and groups can be assigned any combination of the six program capabilities (IA, BA, DS, PH, PH, and MR). Accounts and users can be assigned any combination of the 21 capabilities. SM (System Manager) capability can be assigned to an account or to a user. It cannot be assigned to a group or to a program.

2. A program cannot be executed on the HP 3000 unless the group in which it resides has at least all the capabilities of the program. A program that has PM capability can be executed on the HP 3000 only if it resides in a group that has PM capability.

3. A user does not need to have a capability in order to run a program with that capability. HP 3000 users can execute privileged mode system programs in the PUB.SYS group even though they do not themselves have PM capability.

4. However, a user does need to have a capability before he can create (i.e., link) a program with that capability. A programmer cannot use the link editor to create a privileged mode program unless that programmer (i.e., his userid) has PM capability.

5. Users and groups cannot be assigned capabilities unless the capabilities are assigned to the accounts to which they belong. An account that does not have PM capability cannot contain users or groups that do have PM capability.

Home | About Interex | Press Room | Volunteers | Contact | Media Info | Management Services | Site Map
©Copyright Interex. All rights reserved. Privacy Practice. Contact the Webmaster.

1.	Programs and groups can be assigned any combination of the six program capabilities (IA, BA, DS, PH, PH, and MR). Accounts and users can be assigned any combination of the 21 capabilities.	SM (System Manager) capability can be assigned to an account or to a user. It cannot be assigned to a group or to a program.
2.	A program cannot be executed on the HP 3000 unless the group in which it resides has at least all the capabilities of the program.	A program that has PM capability can be executed on the HP 3000 only if it resides in a group that has PM capability.
3.	A user does not need to have a capability in order to run a program with that capability.	HP 3000 users can execute privileged mode system programs in the PUB.SYS group even though they do not themselves have PM capability.
4.	However, a user does need to have a capability before he can create (i.e., link) a program with that capability.	A programmer cannot use the link editor to create a privileged mode program unless that programmer (i.e., his userid) has PM capability.
5.	Users and groups cannot be assigned capabilities unless the capabilities are assigned to the accounts to which they belong.	An account that does not have PM capability cannot contain users or groups that do have PM capability.