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

Reply via email to