Job Queue Properties

The Job Queue Properties window is displayed when you create or edit a Job Queue. To view or modify the properties for a Queue, right-click the queues's name in the Console Tree and select the Edit... or View... command.

Property Pages

Queue

Name

Enter a name for this Queue. The name is limited to 255 characters and must be unique.

Hold Status

The Hold Status determines whether and how the job can be executed.

Hold triggers. All Triggers defined for the job are ignored. Note: This option holds all triggers for the job, not just Schedule Triggers.
Prevent chained execution by other jobs. Any Job Control Actions and Job Execution Tasks that target the job will be prevented from executing it. adTempus will log an error message in the job log for the calling job, indicating that the target job cannot be run
Prevent manual execution. Users will be prevented from executing the job on-demand using the Run command or the adtexec utility.

Allow override. When this option is checked, jobs within this Queue can ignore the hold settings from this Queue and set their own. When this option is not checked, jobs in the Queue can add additional hold types, but they cannot remove the hold type(s) configured at this level.

Resubmit pending jobs when adTempus restarts

If jobs were queued (awaiting an available execution slot in the queue) when the adTempus service was shut down, adTempus will resubmit those jobs on startup if this option is checked. Otherwise, they will not be resubmitted.

For example, suppose this Queue has an execution limit of 1 (only one job can run at a time). When the adTempus service is shut down, there is one job executing and three more from this queue that have been triggered and are waiting to be executed. If this option is checked, when the service is restarted adTempus will resubmit those three pending jobs to the queue, in the same order they were in at shutdown.

Note that any jobs that were executing at shutdown are not affected by this option, only jobs waiting to be executed.. The restart options for each job determine whether that job will be restarted.

Limit the number of jobs from this queue that can run concurrently

Use this option to limit the number of jobs from this queue that can run at the same time. See the Job Queue Overview topic for more information.

If Distributed Scheduling is in use, this limit applies individually to each computer. For example, if the limit is set to "1" but the Queue is configured to run jobs on two different Agents, each Agent has a limit of one concurrent job, meaning that there may be two jobs (one on each Agent) running in this Queue at any time. If the Queue is configured for Load Balancing, you can additionally limit the number of concurrent jobs against all computers. See the Distributed Scheduling properties for more information.

When a concurrent job has been specified, job execution occurs as follows:

When a job is triggered, adTempus checks to see if there is a free "execution slot" in the queue. If so, the job begins executing immediately.

If no slot is available, the job is queued for execution.
Jobs are arranged in the queue based on their Priority and then the time at which they are submitted to the queue. For example, if a job with priority 200 is triggered and there are already 5 jobs with priority 100 waiting in the queue, the job with priority 200 (higher priority) will execute before the jobs with lower priority. Among jobs with the same priority, jobs execute in the order they were submitted to the queue.
If a job has Conditions, it does not block the queue while it is waiting for the conditions to be met. For example, if the job with priority 200 is waiting for a File Condition, the lower-priority jobs will execute if they are ready. When a job's conditions are met, it goes back in the queue in its original location (ahead of jobs with lower priority and those with the same priority but triggered later).

Description/Notes

Enter any extended descriptive information or notes for this Queue. There is no limit on the length of the text.

Distributed Scheduling

When you are using the Distributed Scheduling features of adTempus, the Distributed Scheduling settings for the Queue determine which computers the jobs assigned to the Queue will be executed on. If the server you are managing is not configured as a Distributed Scheduling Controller computer, this page of the Queue's properties will not be visible.

Agent Mode

Select the mode adTempus should use when running the jobs in this Queue.

Limit the number of jobs from this queue that can run concurrently across all target computers

This option is only available if the Agent Mode is set to "Load Balance."

Use this option to limit the maximum number of jobs that can run concurrently in this Queue across all computers assigned to this Queue. For example, if the limit is set to "1," only one job at a time will run in this Queue, regardless of how many Agents are assigned to the Queue, or what limit has been set on the Queue page.

Run on Controller

Check this option to run the job on the Controller computer, in addition to any specified agents.

If you select the Basic or Mirror modes, the job will be run on the Controller and on any specified agents. If no agents are specified, the job will run only on the Controller.
If you specify the Load Balance mode, adTempus will consider the Controller and all specified agents when determining which computer to run the job on.

Run on Remote Agents

Specify the Agents on which the job should run.

When you add or edit an agent, adTempus displays the Remote Execution Options window, which allows you to customize the way the job will be run on this agent.

Evaluate Conditions On

This option is only available if the Agent Mode is set to "Basic."

Use this option to specify where job-level conditions for the job should be evaluated (step-level conditions are always evaluated on the computer where the job is actually running).

Controller: When the job is triggered, the Controller computer evaluates the job-level conditions for the job. If the conditions are met, the execution command is sent to the Agent computers and the job is run. If the conditions are not met, the job is not run.
Agent: When the job is triggered, the Controller computer sends the execution commands to the Agents. Each Agent then evaluates the conditions for the job and determines whether the run the job. Thus it is possible that the job will execute on some Agents but not on others.

Variables

The Variables page defines Job Variables that are inherited by all Jobs in this Queue. You may add, modify, or delete Job Variables, or override the values of Variables that the Queue has inherited.

A Queue inherits the server-level variables.

Job Variable list features and tools

The Job Variable list shows variables defined for the current object as well as variables inherited from a higher level. Icons next to each variable in the list convey information about their inheritance:

	The variable is inherited from a higher level
	The variable is inherited from a higher level and is locked (cannot be overridden)
	The variable is inherited from a higher level and has been modified at this level
	The variable is new at this level
	The variable is inherited from a higher level and must be overridden (a value provided) at this level
	The variable has been overridden (redefined) at a lower level. This icon only appears if you have analyzed variable usage (see below).

When you hove the mouse pointer over the icon for an inherited variable, adTempus will show where the variable was inherited from.

Filtering the variable list

The variable list can be filtered to:

Hide inherited variables (so you only see variables defined at this level)
Hide variables that cannot be modified (inherited variables that are locked to prevent modification)
Show only variables that must be overridden

Analyzing and viewing variable usage5.0

When you click Analyze variable usage, adTempus searches for all the places where the variables are used or overridden. After this analysis is complete, new columns are added to the list to show, for each variable:

Whether it has been overridden (redefined) at a lower level
A count of how many times it is referenced (used)

Clicking Show variable usage opens a new window showing all the references and overrides for the variables. This is the same window shown by the Find Variable and Function References tool.

Analyze variable usage only finds references and overrides that are "below" the current level. For example, if you are viewing the variables for a job, this will find all references and overrides within the job, or within jobs that may receive variables from this jobs (jobs run by Responses or Job Triggers). If you are viewing a group, this will find all references and overrides within groups and jobs below the selected group. That is, the tool only lists places that might be affected by changes to the variables in the list.

This tool does not show other places where the variables might be used. For example if you are viewing job A and some of the variables are also used in job B, those uses will not be listed unless there is a link between job A and job B.

To find all references to a variable:

If the variable is defined at the server level, use the Analyze variable usage tool from the variables list at the server level. This will show all uses everywhere in adTempus.
Use the Find Variable and Function References tool to find a specific variable or all variables.

Responses

The Responses page defines responses that will be executed for all Jobs in the queue.

The events that you can configure Responses for at the Group level are the same as those available for jobs.

Exclusion Periods

Version Compatibility: Server version 5.0 or later Console version 5.0 or later.

The Exclusion Periods page defines the Exclusion Periods that apply to the jobs in this queue. Exclusion Periods define time periods during which jobs will not be executed. On this page, select all the Exclusion Periods that should apply to the queue.

Security

The Security page is used to view or modify the security settings for this object. See the Security Editor topic for more information on editing security settings.

Permissions set for the Queue are inherited by jobs within the Queue.

The following permissions apply to Job Queues:

Permission	Description
Full Control	Permission to perform all actions on the Queue.
List/Reference	Permission to list this Queue.
View	Permission to view the properties of the Queue.
Associate (assign jobs to this queue)	Permission to assign jobs to this Queue.
Modify	Permission to modify the properties of the Queue.
Delete	Permission to delete the Queue.
Administer security	Permission to change the security settings for the Queue.
Change owner	Permission to take ownership of the Queue.

Permission to create new Queues is defined through the Default Queue Security options.