1.$ START/QUEUE/MANAGER/NEW_VERSION
      $ SHOW QUEUE
      %JBC-E-NOSUCHQUE, no such queue

      The START/QUEUE/MANAGER command in this example starts the
      queue manager and creates the queue and journal files in the
      default location, SYS$COMMON:[SYSEXE]. Because the asterisk
      (*)  wildcard character is used by default as the value for the
      list of nodes on which the queue manager can run, the queue
      manager can fail over to any available node in the cluster.

      This command starts the default queue manager SYS$QUEUE_MANAGER
      because the /NAME_OF_MANAGER qualifier is not specified.

      Both the SYS$COMMON:[SYSEXE] location and the value for the
      /ON qualifier (which is * by default in this example) are
      stored in the queue database for future reference. The newly
      created queue database contains no queues or jobs. The SHOW
      QUEUE command shows that no queues are defined on this cluster.

    2.$ START/QUEUE/MANAGER/NEW_VERSION -
      _$ /ON=(SATURN,VENUS,NEPTUN,*) DUA5:[SYSQUE]

      The START/QUEUE/MANAGER command in this example creates the
      queue and journal files on the cluster-accessible disk volume
      DUA5, in directory SYSQUE. You must mount the disk before you
      enter the START/QUEUE/MANAGER command.

      The /ON qualifier specifies that the queue manager should run
      first on node SATURN. If SATURN leaves the cluster, the queue
      manager will attempt to fail over to VENUS. If VENUS is not
      available, the queue manager will attempt to fail over to
      NEPTUN. If NEPTUN is not available, the queue manager will
      fail over to any other available node in the cluster.

    3.$ START/QUEUE/MANAGER/NEW_VERSION -
      _$ /ON=(SATURN,VENUS,NEPTUN,*) DUA5:[SYSQUE])
         .
         .
         .
      $ START/QUEUE/MANAGER

      The START/QUEUE/MANAGER command in this example creates the
      queue database as shown in the previous example. Suppose the
      queue manager started on node SATURN.

      Later, SATURN is removed from the cluster, and the queue
      manager fails over to node VENUS. When SATURN rejoins the
      cluster, the second START/QUEUE/MANAGER command in the example
      is entered to move the queue manager back to node SATURN.

      The second START/QUEUE/MANAGER command does not specify the
      DUA5:[SYSQUE] parameter value or the /ON qualifier and its node
      list because those previously supplied pieces of information
      are stored in the queue database. The queue manager continues
      to use the queue and journal files found at the location
      stored in its database. The /ON list, stored as a result of the
      previous START/QUEUE/MANAGER command, also remains unchanged.

    4.$ START/QUEUE/MANAGER DUA4:[SYSQUE]
      %JBC-E-QMANNOTSTARTED, queue manager could not be started
      $ SEARCH SYS$MANAGER:OPERATOR.LOG /WINDOW=5 QUEUE_MANAGE,JOB_CONTROL
      %%%%%%%%%%%  OPCOM  14-DEC-2001 18:55:18.23  %%%%%%%%%%%
      Message from user QUEUE_MANAGE on QMUNGR
      %QMAN-E-OPENERR, error opening DUA4:[SYSQUE]SYS$QUEUE_MANAGER.QMAN$QUEUES;

      %%%%%%%%%%%  OPCOM  14-DEC-2001 18:55:18.29  %%%%%%%%%%%
      Message from user QUEUE_MANAGE on QMUNGR
      -RMS-F-DEV, error in device name or inappropriate device type for
 	operation

      %%%%%%%%%%%  OPCOM  14-DEC-2001 18:55:18.31  %%%%%%%%%%%
      Message from user QUEUE_MANAGE on QMUNGR
      -SYSTEM-W-NOSUCHDEV, no such device available
      $ START/QUEUE/MANAGER DUA5:[SYSQUE]

      In this example, the first START/QUEUE/MANAGER command
      specifies device DUA4: as the location of the queue and journal
      files. The error message indicates that the queue manager does
      not start. The SEARCH command searches the operator log file
      for relevant messages, and reveals that device DUA4: does not
      exist. The second START/QUEUE/MANAGER command specifies the
      correct device name, DUA5:.