Kbase 12494: Things to consider when submitting batch jobs on VMS
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Things to consider when submitting batch jobs on VMS
This notebook entry describes an issue that might occur when you start
the PROGRESS server in batch mode.
By default, when you send a file to batch, VMS sends it to the batch
queue SYS$BATCH. If the queue SYS$BATCH is directed to only one
batch queue, there is no problem. However, if the queue SYS$BATCH is
defined as generic, the PROGRESS server could start on a node
different from the node on which you want it to start.
For example, if SYS$BATCH is defined as:
/GENERIC=(OWL$BATCH, CONDOR$BATCH, FALCON$BATCH . . . ), each of these
queues is located on a different VAX/VMS machine (node) on the
network. When you send a batch job from node CONDOR, to SYS$BATCH,
it is sent to whichever queue is the least busy. If OWL$BATCH is the
least busy, then the PROGRESS server is started on node OWL, not on
CONDOR as you might expect.
To make sure your batch job is sent to a particular node, define
SYS$BATCH to specify the node. For example, if you want the PROGRESS
server to start on CONDOR, type the logical as follows and then
submit your batch job.
$define sys$batch condor$batch
Progress Software Technical Support Note # 12494