Time Zones
Many organizations operate in multiple time zones. Operators are frequently not in the same location as the Jobs and Workflows they manage. In such situations, it is important to be able to work with Jobs and Workflows in the time zone that they are likely to run in.
Consider a Job that runs at 5:00 pm in New York, and an Operator based in London talking to a user in New York. The Operator needs to be able to see that the Job's time zone is New York and that the process runs at 5:00 pm, even though that may be 10:00 pm local time for the Operator. If the Operator needs to move the Job to run at a new time (to allow some missing data to be loaded into a database, for example), then doing it in the appropriate, Job-specific time zone reduces errors.
The time zone of a Job or Workflow Job is the time zone specified in the Run Wizard. If a Job or Workflow is run from RedwoodScript, without specific time zone, the central RunMyJobs server time zone is used.
Note: The central RunMyJobs server uses the time zone information from the JVM. This data needs to be kept up-to-date for all time zones you use. This is especially true for Daylight Saving Times, which can change from time to time.
All time and date calculations are done in the context of a time zone. In most cases this time zone is either simply the session time zone or an explicitly provided time zone.
Time zones available are loaded directly from the Java Time Zone database when RunMyJobs is installed. You can view time zones at Configure > Automate > Calendar tools > Time Zones.
Note: You can edit only the Description of a time zone.
Etc/GMT Offsets
RunMyJobs uses the Olson time zone format. The etcetera time zone definitions were added to the Olson timezone database to cater to POSIX notation. These time zone definitions do not take DST changes into account. The offset specifies the time value you must add to the local time to get a Coordinated Universal Time value. So, Paris, France would be Etc/GMT-1, which is reversed from what you might expect. There is no equivalent of GMT+1 notation in the Olson timezone database.
If RunMyJobs encounters a time expression with an offset instead of an Olson time zone name, the date is displayed using the POSIX notation, because it is the only notation available that supports offsets. Note that there are multiple Olson time zone names for any given offset.
Deprecated Time Zones
The following time zones have been deprecated in Java and should not longer be used:
ACT, AET, AGT, ART, AST, BET, BST, CAT, CNT, CST, CTT, EAT, ECT, EST, HST, IET, IST, JST, MIT, MST, NET, NST, PLT, PNT, PRT, PST, SST, and VST.
If you use any of these, you can change it to a supported time zone for your region. Navigate to Configure > Automate > Calendar tools > Time Zones and select an appropriate time zone with the name <continent>/<city>.
Context Menu
Time zones support the following context menu options.
Note: For generally applicable object context menu options, see Object Context Menu.
| Action | Description |
|---|---|
| Hide in timezone lists | Hide the current time zone in timezone lists |
| Show in timezone lists | Show the current time zone in timezone lists |