OpenVMS System Management Guide, 2nd Edition

Standardize username formats
Establish account groups to facilitate access control
Ensure minimum password content standards
Create templates for frequently added accounts
Automate account-management functions
The user account is the primary mechanism that the system uses to control system access and resource usage. Before a user can access the system, you must create an account for the user and assign the account sufficient resources for the user s applications.
Account information is contained in the user-authorization database, which consists of the files in table 9.1. Logical assignments are made when the system is booted via the SYLOGICALS.COM script and are fully discussed in chapter 5.
| Filename | Logical Name | Purpose |
|---|---|---|
| SYSUAF.DAT | SYSUAF | System UAF (user-account entries) |
| RIGHTSLIST.DAT | RIGHTSLIST | Rights-identifier database file (all defined identifiers and holders) |
| NETPROXY.DAT | NETPROXY | DECnet network proxy database file (old) |
| NET$PROXY.DAT | NET$PROXY | DECnet network proxy database file (new) |
| TCPIP$PROXY.DAT | TCPIP$PROXY | TCP/IP network proxy database file |
The SYSUAF file contains most of the information usually associated with an account. The RIGHTSLIST file contains the definitions for all identifiers and tracks to whom they have been granted. The NETPROXY and NET$PROXY files contain proxy definitions used to determine access from remote DECnet users, the latter being accessed by DECnet-Plus and the proxy database system services. (NET$PROXY was added in OpenVMS/VAX v6.1 and later, and in OpenVMS/Alpha v6.2 and later.) Finally, TCPIP$PROXY contains proxy definitions used to determine access from remote TCP/IP and Network File System (NFS)...