o  Start the secondary processor or processors (and any associated
      vector processors) in a VMS multiprocessing system. (see /CPU).

   o  Start the system job queue (see /QUEUE).

   o  Start the system job queue manager (see /QUEUE /MANAGER).

   o  Add a zone to a running VAXft (see /ZONE).

Additional information available:

/CPU/QUEUE/ZONE

   Starts the specified secondary processor or processors (and any
   associated vector processors) in a VMS multiprocessing system. The
   /CPU qualifier is required.

   Applies only to VMS multiprocessing systems. Requires CMKRNL
   (change mode to kernel) privilege.

   Format

     START/CPU  [cpu-id[,...]]

Additional information available:

QUALIFIER

ParameterDescriptionExamples

cpu-id[,...]
   Specifies a decimal value representing the identity of a processor
   in a VMS multiprocessing system. In a VAX 8300 system, for
   instance, the CPU ID is the VAXBI node number of the processor; in
   a VAX 8800, the CPU ID of the left processor is 1 and that of the
   right processor is 0. If you do not specify a CPU ID and do not
   include the /ALL qualifier, the START/CPU command selects a single
   available processor to join the multiprocessing system.

   The START/CPU command starts a secondary processor in a VMS
   multiprocessing system.

   You can issue a START/CPU command only for processors in the
   STOPPED or TIMOUT state, as represented by the SHOW CPU command.
   Otherwise, the START/CPU command has no effect.

Additional information available:

/ALL

   Selects all remaining processors in the system's available set to
   join the multiprocessing system.

   1.  $ START/CPU

     The START/CPU command in this example selects a single inactive
     processor from the set of those processors that are currently
     available but inactive. When it completes its initialization,
     the selected processor becomes part of the system's active set
     and is capable of scheduling and executing processes.

   2.  $ START/CPU 4,7

     The START/CPU command in this example selects the processors
     with CPU IDs 4 and 7, if they are currently available and
     inactive. When they complete initialization, these processors
     become part of the system's active set and are capable of
     scheduling and executing processes.


   3.  $ START/CPU/ALL

     The START/CPU/ALL command in this example selects all
     remaining inactive and available processors. When they
     complete initialization, these processors become part of the
     system's active set and are capable of scheduling and executing
     processes.

   Starts or restarts the specified queue after it has been
   initialized. You also can use this command to change the
   attributes of the specified queue. The /QUEUE qualifier is
   required.

   Requires OPER (operator) privilege or execute (E)  access to the
   specified queue.

   Format

     START/QUEUE  queue-name[:]

Additional information available:

PARAMETERQUALIFIERS

Examples

/MANAGER

queue-name[:]
   Specifies the name of the queue to be started or restarted.

Additional information available:

/ALIGN/AUTOSTART_ON/BACKWARD/BASE_PRIORITY
/BLOCK_LIMIT/CHARACTERISTICS/CLOSE/CPUDEFAULT
/CPUMAXIMUM/DEFAULT/DESCRIPTION/DISABLE_SWAPPING
/ENABLE_GENERIC/FORM_MOUNTED/FORWARD/GENERIC/JOB_LIMIT
/LIBRARY/NEXT/ON/OPEN/OWNER_UIC/PROCESSOR
/PROTECTION/RECORD_BLOCKING/RETAIN/SCHEDULE
/SEARCH/SEPARATE/TOP_OF_FILE/WSDEFAULT/WSEXTENT
/WSQUOTA

      /ALIGN[=(option[,...])]

   Prints alignment pages to aid in aligning printer forms. Use this
   qualifier only when restarting an output execution queue from a
   paused state.

   After the alignment is complete, the queue enters a paused state
   until you restart it by reentering the START/QUEUE command.
   Printing resumes from the point where alignment data started; that
   is, the task is backspaced over the pages printed for alignment.

   Possible options are as follows:

   MASK     Specifies that input data are masked by replacing
            alphabetic characters with x's and numbers with 9s;
            nonalphanumeric characters are not masked. Mask
            characters allow you to prevent the printing of sensitive
            information. If you omit the MASK option, data are
            printed unaltered.

   n        Specifies the number of alignment pages to print. The
            value of n can be from 1 to 20. By default, one page of
            alignment data is printed.

      /AUTOSTART_ON=(node::[device][,...])

   Designates the queue as an autostart execution queue and specifies
   the node, or node and device, on which the queue can be located.
   Both node and device must be specified for output queues. For
   batch queues, only node is applicable.

   In a cluster, you can specify more than one node (or node and
   device) on which a queue can run, in the preferred order in which
   nodes should claim the queue. This allows the queue to fail over
   to another node if the node on which the queue is running leaves
   the cluster.

   For autostart queues, the START/QUEUE command activates the queue
   for autostart. The queue will begin processing jobs when the
   ENABLE AUTOSTART/QUEUES command is entered for a node on which
   the queue can run.

   This qualifier cannot be used with the /ON or /GENERIC qualifier.
   However, you can specify the /AUTOSTART_ON qualifier for a queue
   previously created or started with the /ON qualifier. Doing so
   overrides the /ON option and makes the queue an autostart queue.

   For more information about autostart queues, see the
   Guide to Maintaining a VMS System.

      /BACKWARD=n

   Restarts a print queue n pages before the current page; n defaults
   to 1. If you omit the page value, printing resumes at the top
   of the current page. Use this qualifier only when restarting an
   output execution queue from a paused state.

      /BASE_PRIORITY=n

   Specifies the base process priority at which jobs are initiated
   from a batch execution queue. By default, if you omit the
   qualifier, jobs are initiated at the same priority as the base
   priority established by DEFPRI at system generation (usually 4).
   The base priority specifier can be any decimal value from 0 to 15.

      /BLOCK_LIMIT=([lowlim,]uplim)
      /NOBLOCK_LIMIT

   Limits the size of print jobs that can be processed on an output
   execution queue. This qualifier allows you to reserve certain
   printers for certain size jobs. You must specify at least one of
   the parameters.

   The lowlim parameter is a decimal number referring to the minimum
   number of blocks that are accepted by the queue for a print job.
   If a print job is submitted that contains fewer blocks than the
   the lowlim value, the job remains pending until the block limit
   for the queue is changed. After the block limit for the queue is
   decreased sufficiently, the job is processed.

   The uplim parameter is a decimal number referring to the maximum
   number of blocks that are accepted by the queue for a print job.
   If a print job is submitted that exceeds this value, the job
   remains pending until the block limit for the queue is changed.
   After the block limit for the queue is increased sufficiently, the
   job is processed.

   If you specify only an upper limit for jobs, you can omit the
   parentheses. For example, /BLOCK_LIMIT=1000 means that only jobs
   with 1000 blocks or less are processed in the queue. To specify
   only a lower job limit, you must use two consecutive quotation
   marks ("")  to indicate the upper specifier. For example, /BLOCK_
   LIMIT=(500,"") means any job with 500 or more blocks is processed
   in the queue. You can specify both a lower and upper limit. For
   example, /BLOCK_LIMIT=(200,2000) means that jobs with less than
   200 blocks or more than 2000 blocks are not processed in the
   queue.

   The /NOBLOCK_LIMIT qualifier cancels the previous setting
   established by the /BLOCK_LIMIT qualifier for the queue.

      /CHARACTERISTICS=(characteristic[,...])
      /NOCHARACTERISTICS

   Specifies one or more characteristics for processing jobs on an
   execution queue. If a queue does not have all the characteristics
   that have been specified for a job, the job remains pending.
   If you specify only one characteristic, you can omit the
   parentheses. Each time you specify the /CHARACTERISTICS qualifier,
   all previously set characteristics are canceled. Only the
   characteristics specified with the qualifier are established for
   the queue.

   Queue characteristics are installation specific. The
   characteristic parameter can be either a value from 0 to 127
   or a characteristic name that has been defined by the DEFINE
   /CHARACTERISTIC command.

   The /NOCHARACTERISTICS qualifier cancels any settings previously
   established by the /CHARACTERISITCS qualifier for the queue.

   Prevents jobs from being entered in the queue through PRINT or
   SUBMIT commands or as a result of requeue operations. To allow
   jobs to be entered, use the /OPEN qualifier. Whether a queue
   accepts or rejects new job entries is independent of the queue's
   state (such as paused, stopped, or stalled). When a queue is
   marked closed, jobs executing continue to execute. Jobs already
   pending in the queue continue to be candidates for execution.

      /CPUDEFAULT=time

   Defines the default CPU time limit for jobs in this batch
   execution queue. You can specify time as delta time, 0, INFINITE,
   or NONE. You can specify up to 497 days of delta time.

   If the queue does not have a specified CPUMAXIMUM time limit and
   the value established in the user authorization file (UAF) has
   a specified CPU time limit of NONE, either the value 0 or the
   keyword INFINITE allows unlimited CPU time. If you specify NONE,
   the CPU time value defaults to the value specified either in the
   UAF or by the SUBMIT command (if included). CPU time values must
   be greater than or equal to the number specified by the SYSGEN
   parameter PQL_MCPULM.

   For information on specifying delta times, see the VMS DCL
   Concepts Manual.

      /CPUMAXIMUM=time

   Defines the default CPU time limit for all jobs in this batch
   execution queue. You can specify time as delta time, 0, INFINITE,
   or NONE. You can specify up to 497 days of delta time.

   If the queue does not have a specified CPUMAXIMUM time limit and
   the value established in the UAF has a specified CPU time limit of
   NONE, either the value 0 or the keyword INFINITE allows unlimited
   CPU time. If you specify NONE, the CPU time value defaults to
   the value specified either in the UAF or by the SUBMIT command
   (if included). CPU time values must be greater than or equal to
   the number specified by the SYSGEN parameter PQL_MCPULM. The time
   cannot exceed the CPU time limit set by the /CPUMAXIMUM qualifier.
   For information on specifying delta time, see the VMS DCL Concepts
   Manual.

      /DEFAULT=(option[,...])
      /NODEFAULT

   Establishes defaults for certain options of the PRINT command.
   Defaults are specified by the list of options. If you specify
   only one option, you can omit the parentheses. After you set an
   option for the queue with the /DEFAULT qualifier, you do not have
   to specify that option in your PRINT commands. If you do specify
   these options in your PRINT command, the values specified with the
   PRINT command override the values established for the queue with
   the /DEFAULT qualifier. For information on establishing mandatory
   queue attributes, see the description of the /SEPARATE qualifier.

   You cannot use the /DEFAULT qualifier with the /GENERIC qualifier.

   Possible options are as follows:

   [NO]BURST[=keyword]     Controls whether two file flag pages with
                           a burst bar between them are printed
                           preceding output. If you specify the
                           value ALL (default), these flag pages
                           are printed before each file in the job.
                           If you specify the value ONE, these flag
                           pages are printed once before the first
                           file in the job.

   [NO]FEED                Specifies whether a form feed is inserted
                           automatically at the end of a page.

   [NO]FLAG[=keyword]      Controls whether a file flag page is
                           printed preceding output. If you specify
                           the value ALL (default), a flag page is
                           printed before each file in the job. If
                           you specify the value ONE, a flag page is
                           printed once before the first file in the
                           job.

   FORM=type               Specifies the default form for an output
                           execution queue. If a job is submitted
                           without an explicit form definition,
                           this form is used to process the job.
                           See also the description of the /FORM_
                           MOUNTED qualifier.

   [NO]TRAILER[=keyword]   Controls whether a file trailer page is
                           printed following output. If you specify
                           the value ALL (default), a trailer page
                           is printed after each file in the job. If
                           you specify the value ONE, a trailer page
                           is printed once after the last file in the
                           job.

   When you specify the BURST option for a file, the [NO]FLAG option
   does not add or subtract a flag page from the two flag pages that
   are printed preceding the file. For information on specifying
   default queue attributes, see the Guide to Maintaining a VMS
   System.

      /DESCRIPTION=string
      /NODESCRIPTION

   Specifies a string of up to 255 characters that is used to provide
   operator-supplied information about the queue.

   Enclose strings containing lowercase letters, blanks, or other
   nonalphanumeric characters (including spaces) in quotation marks
   (" ").

   The /NODESCRIPTION qualifier removes any descriptive text that may
   be associated with the queue.

      /DISABLE_SWAPPING
      /NODISABLE_SWAPPING

   Controls whether batch jobs executed from a queue can be swapped
   in and out of memory.

      /ENABLE_GENERIC
      /NOENABLE_GENERIC

   Specifies whether files queued to a generic queue that does
   not specify explicit queue names with the /GENERIC qualifier
   can be placed in this execution queue for processing. For more
   information, see the description of the /GENERIC qualifier.

      /FORM_MOUNTED=type

   Specifies the mounted form for an output execution queue. If
   the stock of the mounted form does not match the stock of the
   default form, as indicated by the qualifier /DEFAULT=FORM, all
   jobs submitted to this queue without an explicit form definition
   enter a pending state. If a job is submitted with an explicit form
   and the stock of the explicit form does not match the stock of the
   mounted form, the job enters a pending state. In both cases, the
   jobs remain in a pending state until the stock of the mounted form
   of the queue matches the stock of the form associated with the
   job.

   To specify the form type, use either a numeric value or a form
   name that has been defined by the DEFINE/FORM command. Form
   types are installation specific. You cannot use the /FORM_MOUNTED
   qualifier with the /GENERIC qualifier.

      /FORWARD=n

   Advances the specified number of pages before resuming printing
   the current file in the current job; the default is 1. If you omit
   the page value, printing resumes at the top of the next page. Use
   this qualifier only when restarting an output execution queue from
   a paused state.

      /GENERIC[=(queue-name[,...])]
      /NOGENERIC

   Specifies a generic queue. Also specifies that jobs placed in
   this queue can be moved for processing to compatible execution
   queues. The /GENERIC qualifier optionally accepts a list of target
   execution queues that have been previously defined. For a generic
   batch queue, these target queues must be batch execution queues.
   For a generic output queue, these target queues must be output
   execution queues, but can be of any type (printer, server, or
   terminal). For example, a generic printer queue can feed a mixture
   of printer and terminal execution queues.

   If you do not specify any target execution queues with the
   /GENERIC qualifier, jobs can be moved to any execution queue that
   (1)  is initialized with the /ENABLE_GENERIC qualifier, and (2)
   is the same type (batch or output) as the generic queue.

   To define the queue as a generic batch or output queue, you use
   the /GENERIC qualifier with either the /BATCH or the /DEVICE
   qualifier. If you specify neither the /BATCH nor the /DEVICE
   qualifier on creation of a generic queue, by default the queue
   becomes a generic printer queue.

      /JOB_LIMIT=n

   Specifies the number of batch jobs that can be executed
   concurrently from the queue. Specify a number in the range 0 to
   255.

      /LIBRARY=file-name
      /NOLIBRARY

   Specifies the file name for the device control library. When you
   initialize an output execution queue, you can use the /LIBRARY
   qualifier to specify an alternate device control library. You can
   use only a file name as the parameter of the /LIBRARY qualifier.
   The system always assumes that the file is located in SYS$LIBRARY
   and that the file type is TLB.

   Aborts the currently suspended print job and begins processing of
   the first pending job in the queue. Use this qualifier only when
   restarting an output execution queue from a paused state.

      /ON=[node::]device[:] (printer, terminal, server queue)
      /ON=node:: (batch queue)

   Specifies the node or device, or both, on which this execution
   queue is located. For batch execution queues, you can specify only
   the node name. For output execution queues, you can include both
   the node name and the device name.

   The node name is used only in VAXcluster systems; it must match
   the node name specified by the SYSGEN parameter SCSNODE for the
   VAX computer on which the queue executes.

   Allows jobs to be entered in the queue through PRINT or SUBMIT
   commands or as the result of requeue operations. To prevent jobs
   from being entered in the queue, use the /CLOSE qualifier. Whether
   a queue accepts or rejects new job entries is independent of the
   queue's state (such as paused, stopped, or stalled).

      /OWNER_UIC=uic

   Requires OPER (operator) privilege or control (C)  and execute
   (E)  access to the queue.

   Enables you to change the user identification code (UIC) of the
   queue. Specify the UIC by using standard format as described in
   the VMS DCL Concepts Manual.

      /PROCESSOR=filename
      /NOPROCESSOR

   Allows you to specify your own print symbiont for an output
   execution queue. You can use any valid file name as a parameter
   of the /PROCESSOR qualifier. The system supplies the device and
   directory name SYS$SYSTEM and the file type EXE. If you use this
   qualifier for an output queue, it specifies that the symbiont
   image to be executed is SYS$SYSTEM:filename.EXE.

   By default, SYS$SYSTEM:PRTSMB.EXE is the symbiont image associated
   with an output execution queue.

   The /NOPROCESSOR qualifier cancels any previous setting
   established by the /PROCESSOR qualifier, and causes
   SYS$SYSTEM:PRTSMB.EXE to be used.

      /PROTECTION=(ownership[:access],...)

   Requires OPER (operator) privilege or control (C)  and execute
   (E)  access to the queue.

   Specifies the protection of the queue. Ownership categories are
   system (S),  owner (O), group (G),  and world (W);  each category
   can be abbreviated to its first character. Access categories are
   read (R),  write (W), execute (E),  and delete (D);  a null access
   specification means no access. If you include only one protection
   code, you can omit the parentheses. For more information on
   specifying protection codes, see the VMS DCL Concepts Manual. For
   more information on controlling queue operations through UIC-based
   protection, see the Guide to Maintaining a VMS System.

      /RECORD_BLOCKING
      /NORECORD_BLOCKING

   Determines whether the symbiont can concatenate (or block
   together) output records for transmission to the output device. If
   you specify the /NORECORD_BLOCKING qualifier, the symbiont sends
   each formatted record in a separate I/O request to the output
   device. For the standard VMS print symbiont, record blocking can
   have a significant performance advantage over single-record mode.

      /RETAIN[=option]
      /NORETAIN

   Holds jobs in the queue in a retained status after they have
   executed. The /NORETAIN qualifier enables you to reset the queue
   to the default. Possible options are as follows:

   ALL      Holds all jobs in the queue after execution.

   ERROR    Holds in the queue only jobs that fail to complete.

   A user can request a job retention option for a job by specifying
   the /RETAIN qualifier with the PRINT, SUBMIT, or SET ENTRY
   command. However, the job retention option you specify for a queue
   overrides any job retention option requested by a user for a job
   in that queue.

      /SCHEDULE=[NO]SIZE

   Specifies whether pending jobs in an output queue are scheduled
   for printing based on the size of the job. When the /SCHEDULE=SIZE
   qualifier is in effect, shorter jobs are printed before longer
   ones. When the /SCHEDULE=NOSIZE qualifier is in effect, jobs are
   printed in the order they were submitted, regardless of size.

   If you enter this command while there are pending jobs in any
   queue, its effect on future jobs is unpredictable.

      /SEARCH="search-string"

   Specifies that printing is to resume at the page containing
   the specified string. The search for the string moves forward,
   beginning on the page following the current page. During the
   search, consecutive tabs and spaces are treated as a single space,
   and character case is ignored. The string can be from 1 to 63
   characters and must be enclosed in quotation marks (" ").  Use
   this qualifier only when restarting an output execution queue from
   a paused state.

      /SEPARATE=(option[,...])
      /NOSEPARATE

   Specifies the mandatory queue attributes, or job separation
   options, for an output execution queue. Job separation options
   cannot be overridden by the PRINT command.

   You cannot use the /SEPARATE qualifier with the /GENERIC
   qualifier.

   The job separation options are as follows:

   [NO]BURST                 Specifies whether two job flag pages
                             with a burst bar between them are
                             printed at the beginning of each job.

   [NO]FLAG                  Specifies whether a job flag page is
                             printed at the beginning of each job.

   [NO]TRAILER               Specifies whether a job trailer page is
                             printed at the end of each job.

   [NO]RESET=(module[,...])  Specifies one or more device control
                             library modules that contain the job
                             reset sequence for the queue. The
                             specified modules from the queue's
                             device control library (by default
                             SYS$LIBRARY:SYSDEVCTL) are used to
                             reset the device each time a job reset
                             occurs. The RESET sequence occurs after
                             any file trailer and before any job
                             trailer. Thus, all job separation pages
                             are printed when the device is in its
                             RESET state.

   When you specify /SEPARATE=BURST, the [NO]FLAG separation option
   does not add or subtract a flag page from the two flag pages that
   are printed preceding the job.

   For information on establishing queue attributes that can be
   overridden, see the description of the /DEFAULT qualifier.

   For more information on specifying mandatory queue attributes, see
   the Guide to Maintaining a VMS System.

   Resumes printing at the beginning of the file that was current
   when the output execution queue paused. Use this qualifier only
   when restarting an output execution queue from a paused state.

      /WSDEFAULT=n

   Defines for a batch job a working set default, the default number
   of physical pages that the job can use. The value set by this
   qualifier overrides the value defined in the user authorization
   file (UAF) of any user submitting a job to the queue.

   You also can specify this qualifier for an output execution queue.
   Used in this context, the /WSDEFAULT qualifier establishes the
   working set default of the symbiont process for an execution queue
   when the symbiont process is created.

   If you specify the value 0 or NONE, the working set default
   value defaults to the value specified in the UAF or by the SUBMIT
   command (if included).

      /WSEXTENT=n

   Defines for the batch job a working set extent, the maximum amount
   of physical memory that the job can use. The job uses the maximum
   amount of physical memory only when the system has excess free
   pages. The value set by this qualifier overrides the value defined
   in the user authorization file (UAF) of any user submitting a job
   to the queue.

   You also can specify this qualifier for an output execution queue.
   Used in this context, the /WSEXTENT qualifier establishes the
   working set extent of the symbiont process for an output execution
   queue when the symbiont process is created.

   If you specify the value 0 or NONE, the working set extent value
   defaults to the value specified in the UAF or by the SUBMIT
   command (if included).

      /WSQUOTA=n

   Defines for a batch job a working set quota, the amount of
   physical memory that is guaranteed to the job. The value set
   by this qualifier overrides the value defined in the user
   authorization file (UAF) of any user submitting a job to the
   queue.

   You also can specify this qualifier for an output execution queue.
   Used in this context, the /WSQUOTA qualifier establishes the
   working set quota of the symbiont process for an output execution
   queue when the symbiont process is created.

   If you specify the value 0 or NONE, the working set quota value
   defaults to the value specified in the UAF or by the SUBMIT
   command (if included).

   Working set default, working set quota, and working set extent
   values are included in each user record in the system UAF. You can
   specify working set values for individual jobs or for all jobs in
   a given queue. The decision table shows the action taken for
   different combinations of specifications that involve working set
   size and working set quota values.

   Decision Table - Working Set Default, Extent, and Quota Decision

   Value Specified by
   the SUBMIT          Value Specified
   Command?            for the Queue?    Action Taken

   No                  No                Use the UAF value.

   No                  Yes               Use value for the queue.

   Yes                 Yes               Use smaller of the two
                                         values.

   Yes                 No                Compare specified value with
                                         UAF value; use the smaller.

   1.  $ STOP/QUEUE  LPA0
       $ START/QUEUE/TOP_OF_FILE  LPA0

     The STOP/QUEUE command in this example suspends operation
     of the printer queue LPA0. Then the START/QUEUE/TOP_OF_FILE
     command resumes operation. The file that was being printed when
     the queue was stopped is started again from the beginning.

   2.  $ INITIALIZE/QUEUE  LPA0
          .
          .
          .
       $ START/QUEUE/DEFAULT=FLAG  LPA0

     The INITIALIZE/QUEUE command in this example initializes the
     queue named LPA0. Later, the START/QUEUE command starts the
     queue. The /DEFAULT qualifier requests that a flag page precede
     each file in each job.


   3.  $ START/QUEUE/DEFAULT=FORM=LN01_PORTRAIT LN01_PRINT

     The START/QUEUE command in this example restarts the LN01_PRINT
     queue with the default form LN01_PORTRAIT.

   Starts the clusterwide queue manager for the batch and print
   queuing system and opens the queue database. The /QUEUE qualifier
   is optional, but the /MANAGER qualifier is required.
   For more information, see the Guide to Maintaining a VMS System.

   Requires both OPER (operator) and SYSNAM (system logical name)
   privileges.

   The START/QUEUE/MANAGER command has the following uses:

   o  Enter the command START/QUEUE/MANAGER/NEW_VERSION to create the
      queue database and initially start the queue manager. See the
      description of the /NEW_VERSION qualifier for more information.
      Once the queue manager has been started, it will remain running
      unless it is explicitly stopped with the STOP/QUEUE/MANAGER
      /CLUSTER command.

   o  If the STOP/QUEUE/MANAGER/CLUSTER command has been executed,
      enter the START/QUEUE/MANAGER command to restart the queue
      manager.

   o  In a VAXcluster, enter the START/QUEUE/MANAGER command with
      the /ON qualifier to modify the list of preferred nodes on
      which the queue manager can run. See the description of the /ON
      qualifier for more information.

   o  In a VAXcluster, enter the START/QUEUE/MANAGER command to
      ensure that the queue manager process is executing on the most
      preferred, available node. If the queue manager is not running
      on the most preferred, available node, the queue manager will
      be moved to that node without interruption of service. If you
      are using the default node list (*),  the queue manager will
      not move. For more information, see the description of the /ON
      qualifier.

   If the queue manager does not start when you enter the START/QUEUE
   /MANAGER command, you will receive the following message:

     %JBC-E-QMANNOTSTARTED, queue manager could not be started

   If you see this message, search the operator log file
   SYS$MANAGER:OPERATOR.LOG (or look on the operator console) for
   messages from the facilities QUEUE_MANAGE and JOB_CONTROL for
   information about the problem, as follows:

     $ SEARCH SYS$MANAGER:OPERATOR.LOG /WINDOW=5 QUEUE_MANAGE,JOB_CONTROL

   Format

     START/QUEUE/MANAGER  [dirspec]

Additional information available:

PARAMETER

QualifiersExamples

dirspec
   Specifies the directory location to contain the system queue
   and journal files of the queue database. The queue file,
   SYS$QUEUE_MANAGER.QMAN$QUEUES, contains queue definitions. The
   journal file, SYS$QUEUE_MANAGER.QMAN$JOURNAL, contains job and
   other information that lets the queue manager to return to its
   last known state should a system be stopped unexpectedly. These
   files must reside in the same directory.

   The default location of the queue and journal files is
   SYS$COMMON:[SYSEXE]. The optional dirspec parameter is used
   only for specifying an alternate location for the queue and
   journal files. The specification must include at least the device
   and directory name. Wildcard characters are not allowed in the
   directory specification.

   The directory you specify must be available to all nodes that
   can run the queue manager. If the directory specification is a
   concealed logical name, it must be identically defined on all
   nodes in the cluster.

   The location of the queue and journal files is stored in the
   master file of the queue database. You do not have to respecify
   the directory location with subsequent START/QUEUE/MANAGER
   commands.

   For information about changing the location of any of the queue
   database files, see the Guide to Maintaining a VMS System.

Additional information available:

/NEW_VERSION/ON

      /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.

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

   In a VAXcluster, specify the nodes on which the 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
   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. You cannot specify
   the asterisk wildcard 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.

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

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

     Both the SYS$COMMON:[SYSEXE] location and the asterisk value
     for the /ON qualifier 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-AUG-1991 18:55:18.23  %%%%%%%%%%%
       Message from user QUEUE_MANAGE on QMUNGR
       %QMAN-E-OPENERR, error opening
                        DUA5:[SYSQUE]SYS$QUEUE_MANAGER.QMAN$QUEUES;

       %%%%%%%%%%%  OPCOM  14-AUG-1991 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-AUG-1991 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 relevent messages, and reveals that device DUA4: does not
     exist. The second START/QUEUE/MANAGER command specifies the
     correct device name, DUA5:.

   Adds a zone to the running VAXft system. Applies only to
   the VAXft system.  For VAXft systems only, use HELP FTSS
   for more information on the START/ZONE command or see
   the VAXft System Services Reference Guide.

   Requires CMKRNL (change mode to kernel) privilege.

   Format

     START/ZONE