The system control file specifies the future timezone changes. SET TIMEZONE must be issued to change the timezone of a running system. This drives an interrupt in the virtual machines for them to recalculate their local time. It would appear that CMS fails to do so.
On 8 November 2011 19:47, Paul Gilmartin <[email protected]> wrote: > I have an event that I intended to occur daily at 12:30: > > 'literal 36:30 | dup * | ... delay | ...' > > Last week it was happening at 12:30. This week, it is > happening at 11:30. It's easy to suspect the Daylight > Time change. The event timestamps its output with the > Rexx time() function, which shows 11:30, so it appears > that the system local time offset is correct. > > I have not restarted the pipeline for several weeks. > Is it possible that Pipelines fetches the clock offset > once, when the pipeline starts, and never again? > > Or might this depend on how ops set the local time? > > Thanks, > gil >
