arcanadev

This SQL query demonstrates how to list all jobs and steps in the adTempus 4.x database, including the full group name for each job.

The group name is assembled by following the group hierarchy up to a limit of 10 levels. The top level group of the hierarchy is always the "Root" group and its name is not included in the group name; jobs in the root group show an empty string for the group name.

The JobStep.StepName is populated only if a name has been set in the Console. The Console displays a description for each step that is generated from the step's settings, but this description is not stored in the database.

arcanadev

param (
    [string]$server = ".",
    [int]$days = 180
 )
add-type -path "c:\program files\arcana development\adtempus\4.0\ArcanaDevelopment.adTempus.Client.dll"

$cutoffDate=[DateTime]::UtcNow.Subtract([TimeSpan]::FromDays($days))
$adtempus=[ArcanaDevelopment.adTempus.Client.Scheduler]::Connect($server,[ArcanaDevelopment.adTempus.Shared.LoginAuthenticationType]::Windows,"","")
$context=$adtempus.NewDataContext()
$restartPaging=$false

arcanadev

This example uses the adTempus API to terminate all running jobs on the server.

arcanadev

This script can be run to add a delay between job steps, response actions, etc.

To use it between job steps, insert a new step configured to run a script, and use this code as the script body.

Adjust the sleepTimeInSeconds value as appropriate to get the desired delay.

arcanadev

This sample uses the adTempus API to create a recurring schedule for a job.

This code assumes you have already created the job and have a DataContext names context and a Job named job.

It creates a Schedule that executes every hour from 5am to 9pm, Monday through Friday.

arcanadev

This script finds jobs that missed executions while they were held.

The script retrieves all jobs for the server and then examines those that are currently held. For each held job it retrieves the most recent execution (status.ExecutionFinish), then asks the server to calculate all expected executions beween the last execution and the current time. If any scheduled executions are found in that interval, we know that they were missed because the job was held.

arcanadev

This script retrieves scheduled execution times for all jobs on the server.

The script calls GetJobExecutionTimes to calculate the scheduled executions for all jobs on the server for the next 24 hours.

arcanadev

This script creates a tab-delimited file listing the Job Variables defined for all groups, jobs, and steps.

This script lists the variables explicitly defined (or overridden) at each level; it does not list inherited variables. Note that jobs may be inheriting variables defined at other levels that are not included here:

• Server
• Queue
• Remote Agent

See Also

• Finding overridden variables

arcanadev

This script looks at all groups, jobs, and steps to find places where Job Variables defined at a higher level have been overridden.

The script finds all places where a group, job, or step overrides a variable that is defined at a higher level (server, group, queue, or job).

The script does not compare the variable value to the higher-level value: it only checks whether the variable has been defined at the lower level. That is, if a group has variable "Environment" defined as "Production" and a job in the group has variable "Environment" defined as "Production" that is still reported as an override, because the job has an explicit value for the variable, and if the variable is changed at the group level the job will not get the new value.

See Also:

• List job variables

arcanadev

These samples demonstrate how to retrieve recent job instances

The samples below show:

1. Fetch all instances for the last 30 days for a job
2. Fetch the most recent 5 instances for a job
3. Fetch all instances for the last 30 days for all jobs. This sample also demonstrates how to use paging when fetching large amounts of data.