How Job Management Manager Works › Using Batch Mode › Job Management Manager Batch Execution

Job Management Manager Batch Execution

The manager queues the job at the specified next run time for the job. The job starts executing when the queues on the system allow it to execute.

If the queues are stopped, full, stalled, or in some other nonrun state, the job remains marked as Queued until the queue allows the job to execute. In this respect, the jobs are controlled by the system batch queues.

If the queue is generic, the job may run on a different node than that specified.

When a job’s mode is set, all the mode-specific characteristics are reset to the default values, or to specified values at the time of setting the mode. These values can be modified later.

Any characteristics of the queue will impact Job Management Manager jobs, including the queue’s run priority.

Note: QUEUE, QPRIORITY, and CPULIMIT are supported only for batch mode. Only detached mode supports NODE_RESTRICTION and RUN_PRIORITY. Only remote mode supports REMOTE_NODE in the form of either user@node or node.

If a job’s execution queue is on a machine that does not have the manager installed, the job does not execute properly, and is marked as a failed run attempt.

Note: Resource accounting information for Job Management Manager batch jobs in the event log has slightly smaller values than the corresponding process-id information in the OpenVMS accounting file. Also, peak pagefile use and total mounted volumes are not available.

If a job is deleted while pending, the manager will not actually delete the job before execution.

During the time a job is in a queued state, if a request for another run of the same job comes in, the existing request is deleted from the queue and the new one replaces it. Such requests will thus be processed until the job reaches the head of the queue and starts its run.

During the time a job is in a queued state, if a request for characteristic modifications comes in, the existing request is deleted from the queue and the new one replaces it. Such requests will thus be processed until the job reaches the head of the queue and starts its run.

Note: If SYS$COMMAND is used in a command procedure being run in the Job Management Manager batch mode (instead of to OpenVMS batch mode without the manager), it may run the command file twice.