Use the INITIALIZE/QUEUE command to create a queue or to change the
options of an existing queue that is stopped.
Normally you create output and batch queues by entering the necessary
INITIALIZE/QUEUE commands when you set up your system or OpenVMS
Cluster. Later, you can use the INITIALIZE/QUEUE command to create
additional queues as they are needed. When you create a queue with the
INITIALIZE/QUEUE command, information about the queue is stored in the
queue database.
To create and start the queue at the same time, you can use the
INITIALIZE/QUEUE/START command. If you want to create the queue only
and start it at another time, you can enter only the INITIALIZE/QUEUE
command. Later you can enter the START/QUEUE command to begin queue
operations.
You can use the INITIALIZE/QUEUE, START/QUEUE, and SET QUEUE commands
to change queue options; as you change queue options, information about
the queue in the queue database is updated.
You can use the INITIALIZE and START commands only on stopped queues.
To change options on a running queue, use the SET QUEUE command. To
change queue options that cannot be altered with the SET QUEUE command,
use the following procedure:
- Stop the queue with the STOP/QUEUE/NEXT command.
- Restart the queue with the START/QUEUE or the
INITIALIZE/QUEUE/START command, specifying the appropriate qualifiers
for the options you desire.
Any qualifiers that you do not specify
remain as they were when the queue was previously initialized, started,
or set.
Note that initializing an existing queue does not delete any current
jobs in that queue. Any new queue settings established by the new
INITIALIZE/QUEUE command affect all jobs waiting in the queue or
subsequently entering the queue. Any jobs that are executing in the
queue when it is stopped complete their execution under the old
settings.
The following qualifiers apply to generic and execution queues:
/OWNER_UIC
/PROTECTION
/[NO]RETAIN
/[NO]START
/NAME_OF_MANAGER
The following qualifiers apply to all types of execution queues:
/AUTOSTART_ON
/BASE_PRIORITY
/[NO]CHARACTERISTICS
/[NO]ENABLE_GENERIC
/[NO]NO_INITIAL_FF
/ON
/WSDEFAULT
/WSEXTENT
/WSQUOTA
The following qualifiers apply only to batch execution queues:
/CPUDEFAULT
/CPUMAXIMUM
/[NO]DISABLE_SWAPPING
/JOB_LIMIT
The following qualifiers apply only to printer, terminal, or server
execution queues:
/[NO]BLOCK_LIMIT
/[NO]DEFAULT
/FORM_MOUNTED
/[NO]LIBRARY
/[NO]PROCESSOR
/[NO]RECORD_BLOCKING
/[NO]SEPARATE
Types of Queues
There are several different types of queues. In general, queues can be
divided into two major classes: generic and execution. When a job is
sent to an execution queue, it is executed in that queue. No processing
takes place in generic queues. Generic queues hold jobs that will
execute on an execution queue.
Generic Queues
The following are several types of generic queues:
- Generic batch queue---Holds batch jobs for execution on batch
execution queues.
- Generic output queue---Holds jobs for execution on output queues.
There are three types of generic output queues:
- Generic printer queue---Holds print jobs for printing on output
execution queues.
- Generic server queue---Holds jobs for processing on output
execution queues.
- Generic terminal queue---Holds print jobs for printing on output
execution queues.
The /GENERIC qualifier designates a queue as a generic queue. You
specify the execution queues to which a generic queue feeds jobs in one
of two ways:
- You can explicitly name execution queues assigned to the generic
queue by including a list of queues with the /GENERIC qualifier.
- You can specify the execution queues that may receive jobs from any
generic queue that does not specify an explicit target list by
specifying the /ENABLE=GENERIC qualifier when you create the execution
queue.
Generic queues, unlike execution queues, are not automatically stopped
when the system is shut down or the queue manager is stopped;
therefore, generic queues do not normally need to be restarted each
time the system reboots.
Logical Queues
Another type of queue is the logical queue. A logical queue is a
special type of generic queue that can place work only into the
execution queue specified in the ASSIGN/QUEUE command. The logical
queue's relation to an execution queue remains in effect until you
enter a DEASSIGN/QUEUE command to negate the assignment.
Execution Queues
The following are several types of execution queues:
- Batch execution queue---Executes batch jobs.
- Output execution queue---Processes print output jobs. There are
three types of output execution queues:
- Printer execution queue---Invokes a symbiont to process print jobs
for a printer.
- Server execution queue---Invokes a customer-written symbiont to
process jobs.
- Terminal execution queue---Invokes a symbiont to process print jobs
for a terminal printer.
Batch execution queues execute batch jobs. Batch jobs request the
execution of one or more command procedures in a batch process.
Output execution queues process print jobs. A print job requests the
processing of one or more files by a symbiont executing in a symbiont
process. The default system symbiont is designed to print files on
hardcopy devices (printers or terminals). Customer-written symbionts
can be designed for this or any other file processing activity.
Server queues process jobs using the server symbiont specified with the
/PROCESSOR qualifier. Server queue symbionts are written by the
customer.
Either the /AUTOSTART_ON qualifier or the /ON qualifier designates a
queue as an execution queue, and specifies where the queue is to run.
By using the /ON qualifier, you can specify one node (for batch queues)
or node and device (for output queues) on which the queue can be
started. A queue initialized with the /ON qualifier needs to be started
by a command explicitly naming the queue.
You can specify one or more nodes (or nodes and devices) on which the
queue can be started by using the /AUTOSTART_ON qualifier. A queue
initialized with the /AUTOSTART_ON qualifier is automatically started
by the queue manager when any of the queue's nodes have been enabled
for autostart by that queue manager.
Autostart Queues
An execution queue (either batch or output) can be designated as an
autostart queue. Because all of a queue manager's autostart queues on a
node can be started with a single command, autostart queues eliminate
the need for lengthy queue startup procedures.
In an OpenVMS Cluster, autostart queues can be set up to run on one of
several nodes. If a queue is set up this way, and the node on which the
queue is running leaves the cluster, the queue can fail over to another
node and remain available to the cluster.
The /AUTOSTART_ON qualifier designates an execution queue as an
autostart queue.
/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. 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.
When you enter the INITIALIZE/QUEUE command with the /AUTOSTART_ON
qualifier, you must initially activate the queue for autostart, either
by specifying the /START qualifier with the INITIALIZE/QUEUE command or
by entering a START/QUEUE command. However, the queue will not begin
processing jobs until the ENABLE AUTOSTART/QUEUES command is entered
for a node on which the queue can run.
This qualifier cannot be used in conjunction with the /ON or /GENERIC
qualifier. However, if you are reinitializing an existing queue, you
can specify the /AUTOSTART_ON qualifier for a queue previously created
or started with the /ON qualifier. Doing so overrides the /ON qualifier
and makes the queue an autostart queue.
For more information about autostart queues, see the chapter about
queues in HP OpenVMS System Manager's Manual, Volume 1: Essentials.
/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.
You also can specify this qualifier for an output execution queue. In
this context the /BASE_PRIORITY qualifier establishes the base priority
of the symbiont process when the symbiont process is created.
/BATCH
/NOBATCH (default)
Specifies that you are initializing a batch queue. If you are
reinitializing an existing queue, you can use the /BATCH qualifier only
if the queue was created as a batch queue.
A batch queue is classified as either an execution queue or a generic
queue. By default, the /BATCH qualifier initializes an execution queue.
To specify a generic batch queue, use the /GENERIC qualifier together
with the /BATCH qualifier.
The /BATCH and /DEVICE qualifiers are mutually exclusive; the /NOBATCH
and /NODEVICE qualifiers cannot be used together.
/BLOCK_LIMIT=([lowlim,]uplim)
/NOBLOCK_LIMIT (default)
Limits the size of print jobs that can be processed on an output
execution queue. The /BLOCK_LIMIT 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 accepted by the queue for a print job. If a
print job is submitted that contains fewer blocks than 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 the queue accepts 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 a null string ("") 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 that queue.
/CHARACTERISTICS=(characteristic[,...])
/NOCHARACTERISTICS (default)
Specifies one or more characteristics for processing jobs on an
execution queue. If you specify only one characteristic, you can omit
the parentheses. If a queue does not have all the characteristics that
have been specified for a job, the job remains pending. Each time you
specify the /CHARACTERISTICS qualifier, all previously set
characteristics are cancelled. 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 /CHARACTERISTICS qualifier for that queue.
/CLOSE
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 pending in the queue continue to be
candidates for execution.
/CPUDEFAULT=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
(default). 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 system parameter PQL_MCPULM. The time
cannot exceed the CPU time limit set by the /CPUMAXIMUM qualifier. For
information on specifying delta time, see the OpenVMS User's Manual or the
online help topic Date. For more information on specifying CPU time
limits, see Table DCLI-1.
/CPUMAXIMUM=time
Defines the maximum CPU time limit for all jobs in a batch execution
queue. You can specify time as delta time, 0, INFINITE, or NONE
(default). You can specify up to 497 days of delta time.
The /CPUMAXIMUM qualifier overrides the time limit specified in the
user authorization file (UAF) for any user submitting a job to the
queue. 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 system parameter PQL_MCPULM.
For information on specifying delta times, see the OpenVMS User's Manual or the
online help topic Date. For more information on specifying CPU time
limits, see Table DCLI-1.
A CPU time limit for processes is specified by each user record in the
system UAF. You also can specify the following: a default CPU time
limit or a maximum CPU time limit for all jobs in a given queue, or a
default CPU time limit for individual jobs in the queue. Table DCLI-1
shows the action taken for each value specified and possible
combinations of specifications.
Table DCLI-1 CPU Time Limit Specifications and Actions
| CPU Time Limit Specified by the SUBMIT Command? |
Default CPU Time Limit Specified for the Queue? |
Maximum CPU Time Limit Specified for the Queue? |
Action Taken |
|
No
|
No
|
No
|
Use the UAF value.
|
|
Yes
|
No
|
No
|
Use the smaller of SUBMIT command and UAF values.
|
|
Yes
|
Yes
|
No
|
Use the smaller of SUBMIT command and UAF values.
|
|
Yes
|
No
|
Yes
|
Use the smaller of SUBMIT command and queue's maximum values.
|
|
Yes
|
Yes
|
Yes
|
Use the smaller of SUBMIT command and queue's maximum values.
|
|
No
|
Yes
|
Yes
|
Use the smaller of queue's default and maximum values.
|
|
No
|
No
|
Yes
|
Use the maximum value.
|
|
No
|
Yes
|
No
|
Use the smaller of UAF and queue's default values.
|
/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 command. 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.
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
|
Controls 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 file flag page is printed before
each file in the job. If you specify the value ONE, a file 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. If no form type is explicitly specified with the FORM
keyword, the system assigns the form DEFAULT to the queue. See also the
description of the /FORM_MOUNTED=type qualifier.
|
|
[NO]TRAILER[=keyword]
|
Controls whether a file trailer page is printed following output. If
you specify the value ALL (default), a file 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 establishing mandatory queue options, see the
description of the /SEPARATE qualifier. For more information on
specifying default queue options, see the chapter on queues in the
HP OpenVMS System Manager's Manual.
/DESCRIPTION=string
/NODESCRIPTION (default)
Specifies a string of up to 255 characters 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.
/DEVICE[=option]
/NODEVICE
Specifies that you are initializing an output queue of a particular
type. If you are reinitializing an existing queue, you can use the
/DEVICE qualifier only if the queue was created as an output queue.
Possible options are as follows:
|
PRINTER
|
Indicates a printer queue.
|
|
SERVER
|
Indicates a server queue. A server queue is controlled by the
user-modified or user-written symbiont specified with the /PROCESSOR
qualifier.
|
|
TERMINAL
|
Indicates a terminal queue.
|
If you specify the /DEVICE qualifier without a queue type, the
/DEVICE=PRINTER qualifier is used by default.
An output queue is classified as either an execution or generic queue.
By default, the /DEVICE qualifier initializes an execution queue of the
designated type. To specify a generic printer, server, or terminal
queue, use the /GENERIC qualifier with the /DEVICE qualifier.
You specify the queue type with the /DEVICE qualifier for informational
purposes. When an output execution queue is started, the symbiont
associated with the queue determines the actual queue type. The
standard symbiont examines device characteristics to establish whether
the queue should be marked as printer or terminal. By convention,
user-modified and user-written symbionts mark the queue as a server
queue. The device type of a generic queue need not match the device
type of its execution queues.
The /DEVICE and /BATCH qualifiers are mutually exclusive; the /NODEVICE
and /NOBATCH qualifiers cannot be used together.
/DISABLE_SWAPPING
/NODISABLE_SWAPPING (default)
Controls whether batch jobs executed from a queue can be swapped in and
out of memory.
/ENABLE_GENERIC (default)
/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 no form type is explicitly specified, the system assigns the form
DEFAULT to the queue.
If the stock of the mounted form does not match the stock of the
default form, as indicated by the /DEFAULT=FORM qualifier, all jobs
submitted to this queue without an explicit form definition enter a
pending state and remains pending until the stock of the mounted form
of the queue is identical to the stock of the form associated with the
job.
If a job is submitted with an explicit form and the stock of the
explicit form is not identical to the stock of the mounted form, the
job enters a pending state and remains pending until the stock of the
mounted form of the queue is identical to 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.
/GENERIC[=(queue-name[,...])]
/NOGENERIC (default)
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 /BATCH nor /DEVICE on creation of a generic queue,
the queue becomes a generic printer queue by default.
You cannot use the /SEPARATE qualifier with the /GENERIC qualifier.
/JOB_LIMIT=n
Indicates the number of batch jobs that can be executed concurrently
from the queue. Specify a number in the range 1 to 65535. The job limit
default value for n is 1.
/LIBRARY=filename
/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. The default
library is SYS$LIBRARY:SYSDEVCTL.TLB. 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.
/NAME_OF_MANAGER=name
Identifies the name of the queue manager to control the queue. Once the
queue is created, the queue manager assignment may not be altered.
If the /NAME_OF_MANAGER qualifier is omitted, then the default name
SYS$QUEUE_MANAGER is used.
If the INITIALIZE/QUEUE command is used to modify a queue, and that
queue is not controlled by the default queue manager, then the name of
the controlling queue manager should be specified with the
/NAME_OF_MANAGER qualifier. Alternately, the logical name
SYS$QUEUE_MANAGER can be defined to be the correct queue manager,
making that queue manager the default for the current process.
/NO_INITIAL_FF
/NONO_INITIAL_FF (default)
Allows user to specify whether a form feed should be sent to a printer
device when a queue starts. To suppress the initial form feed, use the
/NO_INITIAL_FF qualifier.
The /NONO_INITIAL_FF qualifier sends a form feed to the output device
to ensure the paper is at the top of a page before printing begins.
/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. By default, a queue executes on the same node from
which you start the queue. The default device parameter is the same as
the queue name.
You can specify an IP address and port number, in quotation marks, for
the device. For more information about specifying IP addresses, see the
TCP/IP Services for OpenVMS documentation.
The node name is used in OpenVMS Cluster systems; it must match the
node name specified by the system parameter SCSNODE for the OpenVMS
computer on which the queue executes.
You cannot use the /ON qualifier with the /AUTOSTART_ON or /GENERIC
qualifier; however, if you are reinitializing an existing queue, you
can specify the /ON qualifier for a queue previously created or started
with the /AUTOSTART_ON qualifier. Doing so overrides the /AUTOSTART_ON
option and makes the queue a nonautostart queue.
/OPEN (default)
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
Enables you to change the user identification code (UIC) of the queue.
Specify the UIC by using standard UIC format as described in the
HP OpenVMS Guide to System Security. The default UIC is [1,4].
/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
with the /PROCESSOR qualifier and causes SYS$SYSTEM:PRTSMB.EXE to be
used.
/PROTECTION=(ownership[:access],...)
Specifies the protection of the queue:
- Specify the ownership parameter as system (S), owner (O),
group (G), or world (W).
- Specify the access parameter as read (R), submit (S),
manage (M), or delete (D).
A null access specification means no access. The default protection is
(SYSTEM:M, OWNER:D, GROUP:R, WORLD:S). If you include only one
protection code, you can omit the parentheses. For more information on
specifying protection codes, see the HP OpenVMS Guide to System Security. For more
information on controlling queue operations through UIC-based
protection, see the chapter on queues in the HP OpenVMS System Manager's Manual.
/RAD=n
Specifies the RAD number on which to run batch jobs assigned to the
queue. The RAD value is validated as a positive integer between 0 and
the value returned by the $GETSYI item code, SYI$_RAD_MAX_RADS.
RAD is supported on AlphaServer GS series systems and starting from OpenVMS Version 8.4, support is extended to NUMA capable Integrity servers.
/RECORD_BLOCKING (default)
/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
OpenVMS print symbiont, record blocking can have a significant
performance advantage over single-record mode.
/RETAIN[=option]
/NORETAIN (default)
Holds jobs in the queue in a retained state after they have executed.
The /NORETAIN qualifier enables you to reset the queue to the default.
Possible options are as follows:
|
ALL (default)
|
Holds all jobs in the queue after execution.
|
|
ERROR
|
Holds in the queue only jobs that complete unsuccessfully.
|
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=SIZE (default)
/SCHEDULE=NOSIZE
Specifies whether pending jobs in an output execution queue are
scheduled for printing based on the size of the job. When the default
qualifier /SCHEDULE=SIZE is in effect, shorter jobs print before longer
ones.
When the /SCHEDULE=NOSIZE qualifier is in effect, jobs are not
scheduled according to size.
If you enter this command while there are pending jobs in any queue,
its effect on future jobs is unpredictable.
/SEPARATE=(option[,...])
/NOSEPARATE (default)
Specifies the mandatory queue options, 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 at the end of each job. 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 the /SEPARATE=BURST qualifier, 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 options that can be overridden,
see the description of the /DEFAULT qualifier.
For more information on specifying mandatory queue options, see the
chapter on queues in the HP OpenVMS System Manager's Manual.
/START
/NOSTART (default)
Starts the queue being initialized by the current INITIALIZE/QUEUE
command.
For autostart queues, this qualifier activates the queue for autostart.
The queue begins processing jobs when autostart is enabled with the
ENABLE AUTOSTART/QUEUES command on any node on which the queue can run.
/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.
Specify the value of n as a number of 512-byte pagelets on
Alpha systems. Note that OpenVMS rounds this value up to the nearest
CPU-specific page so that the actual amount of physical memory allowed
may be larger than the specified amount on Alpha. For further
information, see the HP OpenVMS System Manager's Manual.
If you specify 0 or NONE, the working set default value defaults to the
value specified in the UAF or by the SUBMIT command (if it includes a
WSDEFAULT value).
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 output execution queue when the
symbiont process is created.
For more information about the way a working set default affects batch
jobs, see Table DCLI-2.
/WSEXTENT=n
Defines for the batch job a working set extent, the maximum amount of
physical memory that the job can use. The job only uses the maximum
amount of physical memory 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.
Specify the value of n as a number of 512-byte pagelets on
Alpha. Note that OpenVMS rounds this value up to the nearest
CPU-specific page so that the actual amount of physical memory allowed
may be larger than the specified amount on Alpha.
If you specify 0 or NONE, the working set extent value defaults to the
value specified in the UAF or by the SUBMIT command (if it includes a
WSEXTENT value).
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.
For more information about the way a working set extent affects batch
jobs, see Table DCLI-2.
/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.
Specify the value of n as a number of 512-byte pagelets on
OpenVMS Alpha. OpenVMS rounds this value up to the nearest CPU-specific
page so that the actual amount of physical memory allowed may be larger
than the specified amount on OpenVMS Alpha. For further information,
see the HP OpenVMS System Manager's Manual.
If you specify 0 or NONE, the working set quota value defaults to the
value specified in the UAF or by the SUBMIT command (if it includes a
WSQUOTA value).
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.
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 (Table DCLI-2) shows the action taken for
different combinations of specifications that involve working set
values.
Table DCLI-2 Working Set Default, Extent, and Quota Decision
| Is the SUBMIT command value specified? |
Is the queue value specified? |
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.
|
