5.2.21 /OPEN
/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).
5.2.22 /OWNER_UIC
/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 VSI OpenVMS Guide to System Security. The default UIC is
[1,4].
5.2.23 /PROCESSOR
/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.
5.2.24 /PROTECTION
/PROTECTION=(ownership[:access],...)
Specifies the protection of the queue:
o Specify the ownership parameter as system (S), owner (O),
group (G), or world (W).
o 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
VSI OpenVMS Guide to System Security. For more information on
controlling queue operations through UIC-based protection, see
the chapter on queues in the VSI OpenVMS System Manager's Manual.
5.2.25 /RAD
/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.
5.2.26 /RECORD_BLOCKING
/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.
5.2.27 /RETAIN
/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 Holds all jobs in the queue after execution.
(default)
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.
5.2.28 /SCHEDULE
/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.
5.2.29 /SEPARATE
/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 VSI OpenVMS System Manager's Manual.
5.2.30 /START
/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.
5.2.31 /WSDEFAULT
/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 VSI 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.
5.2.32 /WSEXTENT
/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.
5.2.33 /WSQUOTA
/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 VSI 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 shows the action taken
for different combinations of specifications that involve working
set values.
Is the SUBMIT Is the
command value queue value
specified? 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.
5.3 – Examples
1.$ INITIALIZE/QUEUE/PROCESSOR=TELNETSYM -
_$ /ON="192.168.1.101:9100" SYS$PRINT
This example initializes the SYS$PRINT print queue, specifying
the TELNETSYM print symbiont, for the printer with the IP
address 192.168.1.101 at TCP port 9100. For more information
about TELNETSYM, see the TCP/IP Services for OpenVMS Management
Guide.
2.$ INITIALIZE/QUEUE/BATCH/START -
_$ /AUTOSTART_ON=(DATA::, WARF::, DEANNA::) BATCH_1
The INITIALIZE/QUEUE command in this example creates the
batch queue BATCH_1, and designates it as an autostart queue
capable of executing on node DATA, WARF, or DEANNA. The /START
qualifier activates the queue for autostart. The queue will
begin executing on the first node (in the list of nodes
specified) for which the ENABLE AUTOSTART/QUEUES command is
entered.
If the node on which BATCH_1 is executing is taken out of the
OpenVMS Cluster, the queue will be stopped on that node and
will fail over to the first available node in the node list
on which autostart is enabled for a queue manager SYS$QUEUE_
MANAGER.
As long as autostart is enabled on one of the nodes in the
list, this queue will be started and available to execute batch
jobs. If all three nodes in the example are shut down or if
autostart is disabled, the queue will remain stopped until
one of the three nodes in the node list joins the cluster and
executes the ENABLE AUTOSTART/QUEUES command.
The ENABLE AUTOSTART/QUEUES and INITIALIZE/QUEUE commands
affect only the queues managed by the default queue manager
SYS$QUEUE_MANAGER because the /NAME_OF_MANAGER qualifier is not
specified.
3.$ INITIALIZE/QUEUE/START/BATCH/JOB_LIMIT=3 SYS$BATCH
$ INITIALIZE/QUEUE/START/BATCH/JOB_LIMIT=1/WSEXTENT=2000 BIG_BATCH
In this example, the first INITIALIZE/QUEUE command creates
a batch queue called SYS$BATCH that can be used for any batch
job. The /JOB_LIMIT qualifier allows three jobs to execute
concurrently. The second INITIALIZE/QUEUE command creates
a second batch queue called BIG_BATCH that is designed for
large jobs. Only one job can execute at a time. The working
set extent can be as high as 125 pages on OpenVMS Alpha (on a
system with 8KB pages).
4.$ INITIALIZE/QUEUE/START/DEFAULT=(FLAG,TRAILER=ONE)-
_$ /ON=LPA0: LPA0_PRINT
$ INITIALIZE/QUEUE/START/DEFAULT=(FLAG,TRAILER=ONE)-
_$ /BLOCK_LIMIT=(1000,"")/ON=LPB0: LPB0_PRINT
$ INITIALIZE/QUEUE/START/GENERIC=(LPA0_PRINT,LPB0_PRINT) SYS$PRINT
$ INITIALIZE/QUEUE/START/FORM_MOUNTED=LETTER-
_$ /BLOCK_LIMIT=50/ON=TXA5: LQP
In this example, the first three INITIALIZE/QUEUE commands set
up printer queues. Both queue LPA0_PRINT and LPB0_PRINT are
set up to put a flag page before each file within a job and a
trailer page after only the last page in a job. In addition,
LPB0_PRINT has a minimum block size of 1000; therefore, only
print jobs larger than 1000 blocks can execute on that queue.
SYS$PRINT is established as a generic queue that can direct
jobs to either LPA0_PRINT or LPB0_PRINT. Jobs that are too
small to run on LPB0_PRINT will be queued from SYS$PRINT to
LPA0_PRINT.
The last INITIALIZE/QUEUE command sets up a terminal queue on
TXA5. A job queued with a form that has a stock type other
than the stock type of form LETTER remains pending in the
queue until a form with the same stock type is mounted on the
queue, or until the entry is deleted from the queue or moved
to another queue. LETTER has been established at this site to
indicate special letterhead paper. The block size limit is 50,
indicating that this queue is reserved for jobs smaller than
51 blocks.
5.$ INITIALIZE/QUEUE/ON=QUEBID::/BATCH/RAD=0 BATCHQ1
$ SHOW QUEUE/FULL BATCHQ1
Batch queue BATCHQ1, stopped, QUEBID::
/BASE_PRIORITY=4 /JOB_LIMIT=1 /OWNER=[SYSTEM]
/PROTECTION=(S:M,O:D,G:R,W:S) /RAD=0
This example creates or reinitializes the batch queue BATCHQ1
to run on node QUEBID. All jobs assigned to this queue will run
on RAD 0.