Job Schedule Fields

Name of the job. For example, Emergency Schedule.

This field is required and job names must be unique.

If no agent name is defined, Job Types will be unavailable in the Job Data dialog box.

Login name of the user under which the batch job is run and the corresponding password.

These credentials are the same as those used to log in to the Trapeze4 Workstation. The PASS Schedule Agent passes the user name and password to the Schedule Server, which uses it to facilitate provider and security checking.

PASS-CT imposes provider security based on the security group of the user login and only batch schedules trips and runs for which the user has privileges.

Specifies which job is executed first, second, and so on when there are multiple batch jobs. Lower numbers take precedence over higher numbers.

For example, if there are two batch jobs (one with priority 5 and one with priority 10), and batch job priority 10 is performing a batch schedule, it will pause to let batch job priority 5 perform its batch schedule and will not resume until batch job priority 5 is finished.

Leaving this check box cleared disables the job without deleting the job record.

Specifies the start and end dates during which the job runs.

If no date (or 0) is typed in the To Date field, the job runs indefinitely.

For example, the From Time is 9:00, the To Time is 18:00, and the Interval is 3600 (seconds), the job is run every hour at 9:00, 10:00, 11:00, and so on until 17:00. The job will not run at 18:00.

If 0 is typed or if the field is left blank, the job is run only at the From Time.

The job is canceled if it has not been completed by this time. If 0 is typed or if the field is left blank, there is no time limit and the job runs to completion.

Number of times the job is to be repeated at each interval. If 0 is typed or if the field left blank, then the job runs only once per interval.

The count resets at each new interval. However, if a repeating job does not complete by the next interval, it may cause the next interval to be skipped.

In the Repeat Delay field, type a time (in seconds) to determine how long the job pauses between each repeat run.

Job ID of another job which is to be started as soon as this job is completed. The next job only starts if the previous job finishes, and is not started if the first job is stopped due to its reaching the value defined in Max Length.

This field allows jobs to be chained together. For example, Job A’s next job could be Job B, and Job B’s next job could be Job C.

Jobs that are defined as Next Jobs by another job cannot be run independently. Next jobs will not run unless they are valid at the date/time when they are triggered.