How Job Management Manager Works › Job Management Manager in an OpenVMS Cluster › How the Default Node Runs a Job Management Manager Job

How the Default Node Runs a Job Management Manager Job

When you run the manager on multiple nodes of an OpenVMS Cluster, one node becomes the default executor. If load balancing is turned off, this node runs all jobs that do not have a node restriction. If load balancing is turned on and the logical name NSCHED$LBAL$WAIT_AVAIL_NODE is not defined (default) or is set to FALSE, a job that cannot be scheduled to any node in its Load Balance group will run on the default node.

Normally, the first node in the OpenVMS Cluster that starts the manager becomes the default executor; however, the system manager can control this by using the SCHEDULE SET DEFAULT command.

If the default agent node fails or the manager is stopped on that node, another node takes over this function.

To see which node is the current default agent; enter the SCHEDULE SHOW DEFAULT command.