Previous Topic: Overview

Next Topic: Run Time Global Symbols Available to Jobs

Job Management Manager Logical Names

The following table lists and describes Job Management Manager logical names. Beginning with Release 3.1, the logical names reside in the two files:

NSCHED$COM:UJM$MANAGER$STARTUP_nodename.COM

NSCHED$COM:UJM$MANAGER$STARTUP_SYSCLUSTER.COM

The nodename in the first filename is replaced by the system node name, and contains system specific logical names. The second file contains cluster-wide logical names.

You can edit these files to modify the values of the logical names. The file NSCHED$COM:UJM$MANAGER$STARTUP_LOCAL.TEMPLATE contains the default values for all logical names, and is provided at installation time.

Logical Name

Description

NSCHED$

Default set up at installation, based on response from user questions. Points to the directory that contains all of the manager’s files.

NSCHED$ALIAS_GROUPS

Logical name to use to repair stale remote cluster aliases in a job record. See Repairing Job Records Containing Stale Cluster Aliases in this guide.

NSCHED$BS_MAX_WAIT

Identifies the maximum seconds to wait for "Batch start."

NSCHED$BS_RETRIES

Identifies the number of times to retry sending "Batch start."

NSCHED$CHECK_RATIO

Returns the ratio of timer events to check procedure.

NSCHED$CLEAR_RESTART_PARAM

A job can have a restart parameter set while it is running, so if it fails during execution, the restart parameter can be passed back when it restarts. If this is defined as TRUE, the restart parameter will be cleared when the job completes and the job will start from the beginning the next time it runs. If defined as FALSE the restart parameter will not be cleared when the job completes, thus the next time the job runs it will continue from the saved restart parameter.

Default: TRUE.

NSCHED$CUSTOM_LOAD_BALANCE

If defined to point to a command procedure to execute, the current (default) load balancing will be overridden. The command file will be executed at the time of considering a load balance. The manager expects that command procedure to have defined a logical called NODE_TO_USE as the nodename to use. Default: UNDEFINED.

NSCHED$DEBUG

Sets debug either on or off.

Default: off.

NSCHED$DEFAULT_JOB_MAX

Defines the maximum number of jobs allowed to run at one time.

Default: 6.

NSCHED$DEFAULT_JOB_PRI

Sets the priority level at which jobs will run.

Default: level 4.

NSCHED$DEFAULT_LOG

Defines the logging events that will be captured. Default: JOB_EVENT and ABNORMAL_EVENT.

NSCHED$DEFAULT_SD_ACTION

Defines the system default Special Day Action, which can be SKIP or HOLD.

Default: SKIP.

NSCHED$LBAL$CPU_WEIGHT

Weighs the CPU rating by multiplying the CPU rating by the translation of this logical. A valid range is from 0.0 to 1.0. Default: 0.5.

NSCHED$LBAL$INTERVAL

Determines the number of seconds between data collection. Default: 30.0 seconds.

NSCHED$LBAL$MEMORY_WEIGHT

Weighs the memory rating by multiplying the memory rating by the translation of this logical. A valid range is from 0.0 to 1.0.

Default: 0.5.

NSCHED$LBAL$UPDATE_RATING

When set to ON, decrease the node rating when a job is sent to a node. Cluster logical. Possible values: OFF, ON.

Default: OFF

NSCHED$LBAL$WAIT_AVAIL_NODE

If TRUE, puts a job in Job Slot Wait for an available node when a Load Balance Group has no available nodes. If FALSE or UNDEFINED, the job is run on the default Job Management Manager node.

Default: UNDEFINED.

NSCHED$LBAL_INSENSITIVE

Defines the percentage difference between node ratings that is considered to be insignificant such that round-robin scheduling can be used. Cluster logical.

Default: 0 (disabled)

 

NSCHED$LOAD_BALANCE

Turns load balancing on or off.

Default: ON.

NSCHED$LOGFILE

Names the Job Management Manager log file.

Default: NSCHED$:VERMONT_CREAMERY.LOG.

NSCHED$MAILBOX

System logical that points to the manager’s message mailbox. Users should not touch this in any way.

NSCHED$MESSAGE_RATIO

Returns the ratio of mailboxes messages to timer_event.

NSCHED$NODEPS

Suppresses the display of job dependencies.

Default: FALSE.

NSCHED$node_SCHED_PORT

The variable node is the OpenVMS node name defined by SYS$NODE in DECnet. If you cannot use the default UDP port 5482 on this system, define this logical to override the default.

Default: 5482.

NSCHED$remnode_EXEC_PORT

The variable remnode is the name of the target remote node. The node name can be, at most, 13 characters. Use this logical in the case of a remote node that must use a UDP port number other than the default (5481). It may require defining an alias for a remote node so its length is fewer than 14 characters. The variable remnode will be the same as the node specified in the job’s REMOTE_NODE characteristic. Default: 5481.

NSCHED$REMOTE_SUPPORT_
ENABLED

The default is defined by the installation, where the installed will be asked questions. If TRUE, remote support will be available. Remote mode jobs and accompanying parameters are supported.

NSCHED$SILENT

Suppresses the connecting messages to remote nodes.

Default: true.

NSCHED$TERM_MAILBOX

System logical that points to the manager’s termination message mailbox. Users should not touch this in any way.

NSCHED$TERMINATION_RATIO

Returns the ratio of termination messages to mailboxes.

NSCHED$UID

Defines the location of the X-window interface user interface definition (UID) file.

NODE_TO_USE

Defined by users if they have selected custom load balancing. It is a local logical, so often it will not have wide impact.

SCHED$BATCH_KEEP_LOG

Retains log files from jobs run in batch queues. Default: TRUE.

SCHED$BATCH_PRINT_LOG

Prints log files from jobs run in batch queues.

Default: FALSE.

SYS$NODE

Must be defined as the name of the node before the manager starts.