No, presently JobScheduler is only able to operate on local time of the server where the JS instance is running.
If the requirements for scheduling requests jobs running on different servers in different time zones one can taken into account that this can be achieved by
- using local instances of JobScheduler on these servers and
- with the remote configuration capability (How_does_a_supervisor_scheduler_distribute_the_%27central_configuration_directory%27%3F).
Different instances on different servers has the advantage that the JS is able to operate on the local server even if the network is broken. A local instance of a JS can operate as well at the same time as an "agent" and can execute jobs which are triggered and monitored from other JS.
The scheduling history of different instances can be stored in a single database.
Update: Feature now implemented with beta status
Time zones can be specified for jobs and orders as of JobScheduler version 1.3.12.2347.
Instead of local time the engine uses UTC time.
- The time zone of the scheduler is configurable with <config time_zonh1. "...">.
- Time zone names are from the tz database, for example time_zone"Europe/Berlin".
- The time zone of jobs and orders is configurable with <run_time time_zonh1. "..."> or <schedule time_zone"...">.
- The timestamp column in log files is displayed in the scheduler's time zone.
- scheduler.log uses local time as before.
- Timestamps in XML answer are marked with suffix "Z" for UTC time.
The JobScheduler uses Joda Time for time calculation.
As this feature still has beta status we would be particularly interested to receive feedback (positive and negative) about its use.