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