Exactly how would one go about achieving this, Alan?
Usage note 4 on SET TIMEZONE is intriguing: "CMS levels prior to CMS
level 11 do not request time zone notification using DIAGNOSE code
X'274', therefore, file system time stamps do not reflect the change in
time zone unless you re-IPL CMS."
This seems to indicate that CMS does register for a time zone change
interrupt since SP5 (really?).
How do I register an interest in this event? Neither CSL nor a macro
interface seems to be available. HNDEXT is not on, as it gets us into a
dogfight with everyone else who need to know that the timezone has
changed. (CMSIUCV was created to multiplex CP IUCV.)
And finally, how does STIMER cope with a timezone change?
On 04/09/2016 06:20 AM, Alan Altmark wrote:
All that needs to happen is for WAKEUP and Pipelines to
understand what to do when a zone-change happens.
In particular, they should
a) Register to hear about TZ changes
b) When TZ change occurs, query system to find new TZ and offset
c) Adjust intervals that represent absolute time value to account for new
offset.
d) Wake up any task that was 'swamped' by a forward-motion TZ change
CMS functions shouldn't be worrying about the TZ definitions, per se, but
should be querying CP about the name and the offset.
>
