AUTHORIZE creates new records or modifies existing records in the
    following files:

    o  System user authorization file (SYSUAF.DAT)

       You can use AUTHORIZE to assign values to various fields
       within each SYSUAF record. The values you assign identify
       the user and the user's work environment, and control use of
       system resources.

       You can redirect SYSUAF logical access by defining a logical
       in your local process logical table; for example:

 $ DEFINE/PROCESS/EXEC SYSUAF DISK$USER:[MYPROCESSTABLE]SYSUAF.DAT

       You can, if you like, define the SYSUAF logical in user mode.

       If you move the SYSUAF.DAT file, be sure the logical name
       SYSUAF is defined and points to an existing file. If AUTHORIZE
       is unable to locate the SYSUAF.DAT file, it displays the
       following error message:

       %UAF-E-NAOFIL, unable to open SYSUAF.DAT
       -RMS-E-FNF, file not found
       Do you want to create a new file?

       A response of YES results in creation of a new SYSUAF file
       containing a SYSTEM record and a DEFAULT record. These records
       are initialized with the same values set when the system was
       installed.

    o  Network proxy authorization file

       The default network proxy authorization file is NET$PROXY.DAT.
       However, AUTHORIZE maintains the file NETPROXY.DAT for
       compatibility.

       In a mixed-version cluster where systems are running OpenVMS
       Alpha or a version of OpenVMS VAX earlier than Version 6.1,
       you must make all proxy modifications on an OpenVMS VAX
       Version 6.1 or later system.

       You can redirect NETPROXY logical access by defining a logical
       in your local process logical table; for example:

 $ DEFINE/PROCESS/EXEC NETPROXY DISK$USER:[MYPROCESSTABLE]NETPROXY.DAT

    o  Rights database file (RIGHTSLIST.DAT)

       You can redirect RIGHTSLIST logical access by defining a
       logical in your local process logical table; for example:

 $ DEFINE/PROCESS/EXEC RIGHTSLIST DISK$USER:[MYPROCESSTABLE]RIGHTSLIST.DAT

    These files store system authorization information. By default,
    they are owned by the system (UIC of [SYSTEM]) and are created
    with the following protection:

    SYSUAF.DAT      S:RWED, O:RWED, G, W
    NETPROXY.DAT    S:RWED, O:RWED, G, W
    NET$PROXY.DAT   S, O, G, W
    RIGHTSLIST.DAT  S:RWED, O:RWED, G, W:

    To use AUTHORIZE, you must have write access to all three
    of these files (you must have an account with the user
    identification code (UIC) of [SYSTEM] or the SYSPRV privilege).

    Note that you must have read access to the RIGHTSLIST.DAT file
    (or sufficient privileges) to display the rights identifiers held
    by other users.

    Because certain images (such as MAIL and SET) require access
    to the system user authorization file (UAF) and are normally
    installed with the SYSPRV privilege, ensure that you always grant
    system access to SYSUAF.DAT.

    When you install a new system, the software distribution kit
    provides the following records in the system user authorization
    file in SYS$SYSTEM:

    On Alpha and Integrity server systems:

       DEFAULT
       SYSTEM

    If the SYSUAF.DAT becomes corrupted or is accidentally deleted,
    you can use the template file SYSUAF.TEMPLATE in the SYS$SYSTEM
    directory to recreate the file, as follows:

    $ SET DEFAULT SYS$SYSTEM
    $ COPY SYSUAF.TEMPLATE SYSUAF.DAT

    The file SYSUAF.TEMPLATE contains records that are identical to
    those defined when the system was installed.

    To make an emergency backup for the system SYSUAF file, you
    can create a private copy of SYSUAF.DAT. To affect future
    logins, copy a private version of SYSUAF.DAT to the appropriate
    directory, as shown in the following example:

    $ COPY MYSYSUAF.DAT SYS$COMMON:[SYSEXE]:SYSUAF.DAT-
    _$ /PROTECTION=(S:RWED,O:RWED,G,W)

    Updated Quotas for the DEFAULT and SYSTEM Accounts

    In OpenVMS Version 8.2 the quotas associated with the DEFAULT and
    SYSTEM accounts were updated. These updated quotas are seen only
    on fresh installations of OpenVMS or on the creation of a new
    SYSUAF data file. Existing SYSUAF data files are not updated.

    The updates to the DEFAULT account are as follows:

    Quota       Old Value    New Value

    ASTLM          250           300
    BYTLM       64,000       128,000
    ENQLM        2,000         4,000
    FILLM          100           128
    PGFLQUOTA   50,000       256,000
    TQELM           10           100
    WSDEFAULT     2000         4,096
    WSQUOTA       4000         8,192

    The updates to the SYSTEM account are the same as the DEFAULT
    account with the exception of the following two quotas:

    Quota       Old Value    New Value

    BYTLM       64,000       256,000
    PGFLQUOTA   50,000       700,000

    For upgraded systems with existing SYSUAF files, you might want
    to update the DEFAULT and SYSTEM account quotas to these new
    values.