Article ID: K00000372
Last Updated: January 18, 2011
Summary
This article describes the changes included in adTempus maintenance update 3.0.8, released on January 18, 2011.
Version Information
After you install this update, the About box in the adTempus Console will show a Product Version of 3.0.8. If your Product Version is already 3.0.8 or later, you do not need to install this update.
Installation Notes
Important: If you are using the Distributed Scheduling features of adTempus, you must update your Master instance and all Agent instances at the same time. If you do not, communication problems may occur between the Master and Agents.
This update is a cumulative update, and contains all fixes released in previous maintenance updates. It is not necessary to install previous maintenance updates before installing this update.
This update may install a new version of the adTempus Update Center. If the update is installed from the Update Center, the setup program will prompt you to close the Update Center to continue. This must be done by terminating the Update Center using the Windows Task Manager.
Obtaining the Update
The latest Maintenance Update can be installed through the adTempus Update Center by selecting "Check for Updates" from the Help menu in the adTempus Console or in the adTempus program group in the Windows Start menu. It can also be downloaded here.
Changes in This Update
The following new changes are included in this update. In addition, this update includes all changes from previous updates. See article K00000361 for information on those changes.
| General |
| | Terminating all instances of a job while other jobs are queued for execution locks up adTempus and consumes all CPU time | CR00000699
Defect | If a job (not a specific instance) is terminated, and one or more other jobs are waiting for execution in the queue (due to queue limits), the adTempus service goes into an endless loop, using all available CPU time.
This problem was resolved. |
| Descriptions missing for some job statuses when JobStatus variable expanded | CR00000716
Defect | When the JobStatus token is expanded (e.g., in a notification message), some job statuses are expanded to "Unknown." The affected statuses are:
- Not Run
- Condition Not Met
- Trigger Failed
- Queued
- Waiting for Agent
- Dispatched to Agent
- Resubmitted
- Missed
This problem was resolved. |
|
| Distributed Scheduling |
| | New job instance incorrectly started when using Load Balancing | CR00000690
Defect | |
When a job is assigned to a queue that uses the Load Balancing mode of Distributed Scheduling, adTempus may incorrectly start multiple instances of the job even though the settings for the job specify that multiple instances should not execute.
This problem was corrected. |
| Job history update not sent to Master in some situations | CR00000702
Defect | |
In some situations, an Agent failed to send a job history update to the Master when the job finished executing. This resulted in the Master showing that the job had finished executing in one place (the main status for the job) but showing the job as still executing in another (the instance details).
This problem was corrected.
|
| when job is moved to mirrored queue that doesn't execute on Master, Next Start in Console doesn't update until service restart | CR00000703
Defect | This problem was resolved. |
| Mirrored jobs using Shared Schedules may disappear from Agents during update | CR00000706
Defect | |
If a job used a Shared Schedule and the job was mirrored to an Agent, the job was removed from the Agent if it was subsequently modified on the Master, instead of being updated on the Agent. This problem was corrected. |
|
| Import/Export |
| | Improvements to Import process for existing objects | CR00000724
Enhancement | |
When an import source contains a job or other object that already exists in adTempus, the Import Wizard now compares the timestamps of the two versions of the object, and by default does not select the object for import if the existing object has the same or a newer timestamp. The Wizard also presents this information to the user. |
| Object Selection window shown on server-to-server export | CR00000725
Enhancement | |
When you export data directly from one server to another, adTempus now displays the Object Selection window, allowing you to view import conflicts and select which objects should be imported to the new server. Previously, this window was available when importing from a file, but not when exporting/importing directly from server to server. |
| "Deselect All" button does not work in export dialog | CR00000653
Defect | | This problem was resolved. |
| Existing objects are being imported even if not selected in import selection dialog | CR00000723
Defect | Some objects were being imported even if they were not selected for import in the Import Wizard.
This problem was resolved. |
|
| Job Execution |
| | Job Control Actions sent to remote computer always execute job, regardless of requested action | CR00000711
Defect | | When a Job Control Action other than an Execute command (e.g., a Hold command) is sent to a remote computer, it is always sent as an Execute command, causing the job to be executed rather than the requested action being performed on the job. |
|
| Performance |
| | Do not count records when querying history | CR00000709
Enhancement | | Changes have been made to improve Console responsiveness for some installations with a large number of jobs or with a large amount of history data. |
|
| Responses |
| | Responses for "Failed" event get executed when job is aborted | CR00000715
Defect | | This behavior was corrected. |
|
| Scheduling |
| | When job has more than one schedule trigger, one of the triggers may get ignored after initial set of runs for that trigger is completed | CR00000700
Defect | |
adTempus calculates an initial set of 5 execution times for each trigger, but in some cases failed to continue calculating execution times for all of the triggers for jobs with more than one schedule trigger.
This problem was resolved. |
| Schedule Triggers may not use correct time zone | CR00000712
Defect | |
When a Schedule Trigger was configured to use a specific time zone, adTempus did not correctly use the specified time zone, and instead executed based on the local time on the server. |
| Job that executes frequently may have gaps of several hours in schedule execution | CR00000719
Defect | A job that is scheduled to run every minute has been executing correctly every minute, but suddenly shows a Next Start time too far in the future, in some cases several hours in the future. Job execution continues normally after that time.
This problem was resolved. |
|
| Scripting |
| | New predefined Job Variables added for job and step description/notes | CR00000717
Enhancement | |
Two new predefined Job Variables were added to contain the Description/Notes values for the executing job and step. The ADTJobNotes and ADTStepNotes variables can be used in scripts and as substitution tokens to retrieve these values or insert the information into notification messages. |
| New predefined job variable for step name | CR00000721
Enhancement | |
The "ADTStepName" variable, containing the name of the step (if defined) is now set for each step. This variable can be used from scripts or in substitution tokens for notification messages, etc. |
| VBScript execution fails on 64-bit platforms | CR00000734
Defect | | This problem was resolved. VBScript scripts will now execute correctly on 64-bit platforms. However, the Script Editor will still display an error when trying to validate these scripts on 64-bit platforms, due to limitations of the Windows Scripting Host used for VBScript. For more information see Knowledge Base article K00000308. |
|
| Triggers |
| | adTempus may crash during File Trigger or Event Log Monitor processing | CR00000698
Defect | |
In some rare cases, the adTempus service crashed if a job was modified, held, or released during a particular phase of trigger evaluation.
This problem was resolved. |
| File Trigger | | | When file trigger starts multiple instances, log message for all jobs has same trigger file name | CR00000720
Defect | | This problem was resolved. |
|
|
| User Interface |
| | Console | | | Notification Subject and Notification Message added to search/replace | CR00000710
Enhancement | |
The Search/Replace feature in the Console now includes notification subjects and messages in the fields that can be searched/replaced. |
| Variables not included when group duplicated | CR00000728
Defect | When a group is duplicated, Job Variables defined for the group are not included.
This problem was resolved. |
| Console crashes when deleting a server-level Job Variable | CR00000735
Defect | Deleting a server-level Job Variable from the General Options window caused the adTempus Console to crash with an unhandled exception error.
The problem has been resolved. |
| Console crashes when editing schedule trigger if computer's timezone database is missing or corrupted | CR00000736
Defect | This problem was resolved. |
| Console may show that Remote Agent is disconnected even though it is connected | CR00000737
Defect | | This problem was resolved. |
|
|
