1    /ATTRIBUTES

       /ATTRIBUTES=(keyword[,...])

    Specifies attributes to be associated with the new identifier.
    The following keywords are valid:

    DYNAMIC       Allows unprivileged holders of the identifier to
                  remove and to restore the identifier from the
                  process rights list by using the DCL command SET
                  RIGHTS_LIST.

    HOLDER_       Prevents people from getting a list of users who
    HIDDEN        hold an identifier, unless they own the identifier
                  themselves.

    NAME_HIDDEN   Allows holders of an identifier to have it
                  translated, either from binary to ASCII or from
                  ASCII to binary, but prevents unauthorized users
                  from translating the identifier.

    NOACCESS      Makes any access rights of the identifier null
                  and void. If a user is granted an identifier with
                  the No Access attribute, that identifier has no
                  effect on the user's access rights to objects. This
                  attribute is a modifier for an identifier with the
                  Resource or Subsystem attribute.

    RESOURCE      Allows holders of an identifier to charge disk
                  space to the identifier. Used only for file
                  objects.

    SUBSYSTEM     Allows holders of the identifier to create and
                  maintain protected subsystems by assigning the
                  Subsystem ACE to the application images in the
                  subsystem. Used only for file objects.

    By default, none of these attributes is associated with the new
    identifier.

2    /USER

       /USER=user-spec

    Scans the UAF record for the specified user and creates the
    corresponding identifier. Specify user-spec by user name or
    UIC. You can use the asterisk wildcard to specify multiple user
    names or UICs. Full use of the asterisk and percent wildcards
    is permitted for user names; UICs must be in the form [*,*],
    [n,*], [*,n], or [n,n]. A wildcard user name specification (*)
    creates identifiers alphabetically by user name; a wildcard UIC
    specification ([*,*]) creates them in numerical order by UIC.

3    /VALUE

       /VALUE=value-specifier

    Specifies the value to be attached to the identifier. The
    following formats are valid for the value-specifier:

    IDENTIFIER:n  An integer value in the range of 65,536 to
                  268,435,455. You can also specify the value in
                  hexadecimal (precede the value with %X) or octal
                  (precede the value with %O).

                  The system displays this type of identifier in
                  hexadecimal. To differentiate general identifiers
                  from UIC identifiers, the system adds %X80000000 to
                  the value you specify.

    GID:n         GID is the POSIX group identifier. It is an integer
                  value in the range 0 to 16,777,215 (%XFFFFFF).
                  The system will add %XA400.0000 to the value you
                  specify and then enter this new value into the
                  system RIGHTSLIST as an identifier.

    UIC:uic       A UIC value in standard UIC format consists of a
                  member name and, optionally, a group name enclosed
                  in brackets. For example, [360,031].

                  In numeric UICs, the group number is an octal
                  number in the range of 1 to 37776; the member
                  number is an octal number in the range of 0 to
                  177776. You can omit leading zeros when you are
                  specifying group and member numbers.

                  Regardless of the UIC format you use, the system
                  translates a UIC to a 32-bit numeric value.

                  Alphanumeric UICs are not allowed.

    Typically, system managers add identifiers as UIC values to
    represent system users; the system applies identifiers in integer
    format to system resources.