The time selected on a job's schedule set is incorrectly displayed on a report. The job runs correctly at the specified time.
Example: The job start time is define as 23:59. In the report, it shows as 00:59
Job run time is stored in the database as integers (e.g. runhour = 23; runminute = 59). However, when the time is retrieved for a report, it is incorrectly assumed that the time zone is UTC+0. Additionally, a time operation is applied to convert the time to the time zone used by the operating system.
For instance, on the example provided above, the local time zone is CET (+1:00).
23:59 UTC is displayed as 00:59 CET (of the next day).
The problem only affects reports. Jobs will run at the specified local time. Enhancement NV-1062 is under consideration to correct the aforementioned problem. To vote for this enhancement request and add comments, please visit Quest Ideas.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center