How Job Management Manager Works › Job Management Manager in an OpenVMS Cluster

Job Management Manager in an OpenVMS Cluster

You can run Job Management Manager jobs only on a node where the manager is running. This rule also applies to OpenVMS Cluster nodes.

To see if the manager is running on your node or OpenVMS Cluster, enter the DCL command SCHEDULE SHOW STATUS. To see if a Job Management Agent is running on a remote node, use the /REMOTE_NODE=remote_node qualifier.

On an OpenVMS Cluster, you can enable a job to run:

• On only one particular node
• On any node
• On a subset of nodes

You can specify a node for a job’s execution by using the /NODE (/CLUSTER_NODE) or /REMOTE_NODE qualifier when creating, copying, or modifying a job.

You can force a job to run manually on a particular node regardless of any node restriction in the job database. To do this, specify the /NODE (or /CLUSTER_NODE) qualifier with the SCHEDULE RUN command.

You can specify a subset of cluster nodes for a job’s execution by using the /LOAD_BALANCE_GROUP qualifier when creating, copying, or modifying a job.

The maximum number of nodes that the manager can support in an OpenVMS Cluster is 200. This feature of the manager is designed to accommodate any future OpenVMS Cluster support increases up to 200 nodes.

The manager is supported on homogeneous and mixed-mode OpenVMS clusters. You should have only one active SYSUAF.DAT file in an OpenVMS Cluster. Use of more than one SYSUAF.DAT file within an OpenVMS Cluster is not supported by CA Technologies (see the OpenVMS Cluster Systems Manual).