/CAPABILITY
       /NOCAPABILITY

    Allows bits in the process user capability mask to be set or
    cleared individually, in groups, or all at once. This qualifier
    is mutually exclusive with the /AFFINITY qualifier.

                                   NOTE

       The SET PROCESS/[NO]CAPABILITY command fails if there is no
       CPU with the required set of capabilities.

    The /NOCAPABILITY qualifier clears all user capability bits
    currently set in the current or permanent capability masks,
    based on the setting of the /PERMANENT qualifier. Specifying the
    /CAPABILITY qualifier has no direct effect, but merely indicates
    the target of the operations specified by the following secondary
    qualifiers:

    /SET=(n[,..Sets all user capabilities defined by the position
               values n, where n has the range of 1 to 16.
    /CLEAR=(n[,Clears all user capabilities defined by the position
               values n, where n has the range of 1 to 16.
    /PERMANENT Performs the operation on the permanent user capability
               mask as well as the current user capability mask,
               making the changes valid for the life of the kernel
               thread. (The default behavior is to affect only the
               capabilities mask for the running image.)

    The secondary qualifiers can all be used at once as long as the
    user capability bits defined in the /SET and /CLEAR parameters do
    not overlap.

    The privileges required to execute the SET PROCESS/CAPABILITY
    command match those required by the $PROCESS_CAPABILITIES system
    service. ALTPRI is the base privilege required to make any
    modifications, and the only privilege required to modify the
    current owner's kernel thread. Modifications within the same UIC
    group require GROUP privilege. Modifications to any unrelated
    kernel thread require WORLD privilege.

    As with the other SET PROCESS qualifiers, the bit operations
    occur on the current process if no /IDENTIFICATION qualifier
    or explicit process name parameter is specified. Specifying a
    process name does not imply that all kernel threads associated
    with the process are affected; the SET PROCESS command affects
    only the initial kernel thread of a multithreaded process.