Command qualifiers modify the behavior of an Oracle RMU command.
    Although similar in appearance, command qualifiers are different
    from the Oracle RMU commands themselves. The first (and sometimes
    the subsequent) word that follows the RMU keyword is the command
    itself. For instance, in the following example, /DUMP and /AFTER_
    JOURNAL are part of the Oracle RMU command and thus must appear
    in the order shown. /OPTION=STATISTICS and /LOG are command
    qualifiers and can appear in any order after the Oracle RMU
    command. You can determine which portions of an Oracle RMU
    command are the command itself, and which portions are command
    qualifiers by noting the documented name of the command,

    $ RMU/DUMP/AFTER_JOURNAL aij_one.aij /OPTION=STATISTICS/LOG

    Command qualifiers can be entered as upper-, lower-, or mixed-
    case type. They always begin with a slash (/)  followed by a
    qualifier word.

    In some cases, an equal sign (=)  and a qualifier value follow
    the qualifier word. A qualifier value can be simple (a number,
    a string, or a keyword) or compound (a list of numbers, strings,
    or keywords separated by commas, enclosed in parentheses) or an
    indirect command file name. For information on using indirect
    command files, see Indirect-Command-Files.

    A default value for a qualifier indicates what qualifier will be
    used if you omit the qualifier completely. Omitting a qualifier
    is not the same thing as specifying a qualifier with a default
    argument.

    Command qualifiers influence the overall action of a command.
    Command qualifiers must be placed following the command keyword
    but before any parameters.

    In the following example, the command qualifier, Users,
    immediately follows the Dump keyword and precedes the command
    parameter, mf_personnel:

    $ RMU/DUMP/USERS MF_PERSONNEL

    Parameter qualifiers (also referred to as file qualifiers or area
    qualifiers) affect the treatment of parameters in the command.
    If the command includes multiple instances of a given type of
    parameter, the placement of parameter qualifiers affects their
    scope of influence as follows:

    o  If you position the parameter qualifier after a particular
       parameter, the qualifier affects only that parameter. This is
       local use of a parameter qualifier.

    o  If you position the parameter qualifier before the first
       parameter, the qualifier applies to all instances of the
       parameter. This is global use of a parameter qualifier. Not
       all parameter qualifiers can be used globally. To identify
       such qualifiers, read the description of the qualifier.

    o  If you position the parameter qualifier after a parameter, the
       qualifier applies only to that instance of the parameter.
       Local parameter qualifiers take precedence over global
       parameter qualifiers, in most cases. Exceptions are documented
       in the qualifier descriptions for each Oracle RMU command.

    The following example demonstrates the local use of the area
    qualifier, Thresholds, to change the threshold settings for the
    EMPIDS_LOW area:

    $ RMU/RESTORE MF_PERSONNEL EMPIDS_LOW/THRESHOLDS=(70,80,90)

    Note that if you specify a qualifier in both the negative and
    positive forms, the last occurrence of the qualifier is the one
    that takes effect. For example, the Nolog qualifier takes effect
    in this command:

    $ RMU/BACKUP/LOG/NOLOG MF_PERSONNEL MF_PERS

    This is consistent with DCL behavior for negative and positive
    qualifiers.