1    /ADD

    Creates an additional queue manager in the existing queue
    database. If the named queue manager already exists, the request
    will be rejected.

2    /NAME_OF_MANAGER

       /NAME_OF_MANAGER=name

    Creates a non-default queue manager. The required name value may
    be up to 31 characters long and may be a logical. The name will
    serve as the identifier for the queue manager process and the
    portion of the database that it is managing.

3    /NEW_VERSION

       /NEW_VERSION
       /NONEW_VERSION (default)

    Specifies that a new (empty) version of the queue database is to
    be created. This qualifier is required when initially creating
    and starting the queuing system.

    If you specify this qualifier and a queue database already
    exists, the new master and queue files of the queue database
    supersede existing versions of those files; however, the journal
    file of the existing queue database is deleted. Jobs and other
    information are lost.

4    /ON

       /ON=(node[,...])

    In an OpenVMS Cluster, specifies the nodes on which a clusterwide
    queue manager can run. The default value for the node list is
    the asterisk (*)  wildcard character, meaning that all nodes in
    the cluster are eligible to run the queue manager. If the node on
    which the queue manager is running leaves the cluster, the queue
    manager can automatically fail over to any available node in the
    cluster. However, to specify a preferred order in which the nodes
    should claim the queue manager, or to limit the nodes which can
    run it, you must specify the /ON qualifier.

    The node list you specify is stored in the queue database.
    Anytime the START/QUEUE/MANAGER command is entered and neither
    the /NEW_VERSION nor /ON qualifier is specified, the /ON list
    stored in the queue database remains unchanged.

    For highest availability, specify the asterisk (*)  wildcard
    character as the last node in the node list to indicate that
    any remaining unlisted node can claim the queue manager, with
    no preferred order. If you do not specify the asterisk (*)
    wildcard character last in the node list, the queue manager can
    only fail over if one of the nodes in the list is available;
    however, if you want to exclude certain nodes from being eligible
    to run the queue manager, you cannot use the asterisk (*)
    wildcard character. You cannot specify the asterisk (*)  wildcard
    character as part of a node name.

    Anytime the START/QUEUE/MANAGER command is entered (with or
    without the /ON qualifier), the job controller will check to
    see if one or more preferred queue manager nodes was currently
    or previously specified with the /ON qualifier. If one or more
    preferred nodes was specified, and the queue manager is running
    on a node other than the first available node of those specified,
    the queue manager process is moved from its current node and
    restarted on the first available preferred node. Despite the
    transition, queues on the running nodes are not stopped. All
    requests to the queuing system, for example, PRINT, SUBMIT, and
    SHOW ENTRY requests, will complete as expected.