Technical data

Managing User Accounts
7.6 Adding User Accounts
Table 7–6 (Cont.) Qualifiers Used with AUTHORIZE
Priority
2
/PRIORITY
Privileges
/DEFPRIVILEGES /PRIVILEGES
Login Access Controls
3
/ACCESS /FLAGS
4
/PRIMEDAYS
/DIALUP /INTERACTIVE /REMOTE
/EXPIRATION /LOCAL
2
Default values are usually adequate for accounts not running real-time processes.
3
By default, users are allowed to log in at any hour of any day. To override the setting of a particular
day, use the DCL command SET DAY. Use this command if a holiday occurs on a day that would
normally be treated as a primary day and you want it treated as a secondary day. See Section 7.8 for
a discussion of using these fields to restrict login times and functions.
4
Not all FLAGS fit into this category.
7.6.2 Adding a User Account with a Command Procedure
As an alternative to using the Authorize utility, you can use a command procedure
to create user accounts. The ADDUSER.COM procedure, which is located in the
SYS$EXAMPLES directory, is an example of such a procedure; it supplies
prompts and several default values for creating the new account.
You can modify ADDUSER.COM as appropriate for the needs of your system.
To run ADDUSER.COM, log in to the SYSTEM account and enter the following
command:
$ @SYS$EXAMPLES:ADDUSER.COM
ADDUSER.COM prompts you to enter values in a number of UAF record fields.
If you press Return without specifying a value for a field, ADDUSER supplies the
following default values:
UAF Field Default Value
User name No default; must supply
Owner No default; must supply
Password User name specified
UIC group number 200
UIC member number No default; must supply number
Account name Optional
Privileges TMPMBX,NETMBX
Login directory User name specified
Login device $DISK1
Disk quota 1000
Overdraft quota 100
7–18 Managing User Accounts