Re: Multiple timezones?
I can think of a couple more possibilities: 1. A job scheduler such as IBM Operations Manager for z/VM (IBM program number 5697-J10), CA VM:Schedule, etc. might handle this requested use case directly. 2. A job scheduler -- on z/OS notably -- could start a job via RSCS or FTPS in z/VM. (This is a variation on the Linux idea.) These two possibilities depend somewhat on how smart the scheduler is about periodic shifts in local time, e.g. daylight savings time. Many job schedulers are pretty smart. I'm generally in favor of scheduling jobs in one logical place if possible and absent a compelling reason otherwise. Note that the local time changes rather often in the world, hence the previous paragraph and its once and once well view. Operating system release X.Y.Z may not have a current understanding of the correct local time in a particular geography if enough time passes. Timothy Sipples GMU VCT Architect Executive (Based in Singapore) E-Mail: sipp...@sg.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Multiple timezones?
On Sun, 11 Aug 2013 17:41:04 +0800, Timothy Sipples wrote: I can think of a couple more possibilities: 1. A job scheduler such as IBM Operations Manager for z/VM (IBM program number 5697-J10), CA VM:Schedule, etc. might handle this requested use case directly. 2. A job scheduler -- on z/OS notably -- could start a job via RSCS or FTPS in z/VM. (This is a variation on the Linux idea.) Of these, how many can handle more timezones than GMT and LOCAL? (After all, the topic is Multiple timezones and the OP's requirement is clear.) These two possibilities depend somewhat on how smart the scheduler is about periodic shifts in local time, e.g. daylight savings time. Many job schedulers are pretty smart. I'm generally in favor of scheduling jobs in one logical place if possible and absent a compelling reason otherwise. Note that the local time changes rather often in the world, hence the previous paragraph and its once and once well view. Operating system release X.Y.Z may not have a current understanding of the correct local time in a particular geography if enough time passes. Indeed, the data base must be updated in a timely, hopefully nondisruptive fashion. For a Horrid Example, Independent Samoa advanced its clocks by 24 hours on December 1, 2012. So: 512 $ TZ=UTC0 date Sun Aug 11 15:13:36 UTC 2013 513 $ ssh 192.168.0.5 uname; TZ=Pacific/Apia date Linux Mon Aug 12 04:13:43 WST 2013 Ubuntu Linux had it right, even in anticipation of the change (admittedly, the system has been restarted since the change, so I can't vouch for nondisruptive), but: 514 $ uname; TZ=Pacific/Apia date Darwin Sun Aug 11 04:14:16 WST 2013 OS X (above; admittedly an out-of-support release), Solaris, and various other Linuxen still haven't got it right 16 months after the fact. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Multiple timezones?
On Thu, 8 Aug 2013 22:23:23 -0700, Donald Russell wrote: zVM 6.1 (6.2 coming) The system runs with a UTC timezone, but it would be convenient if I had a userid that could run in a different time zone. UTC doesn't change with Daylight Saving Time, and I have a process I want to schedule at a specific time that is subject to DST changes. i.e. I want something to run at 3:00 AM Pacific Time, in summer and winter. If I can have a disconnected service machine running in the proper timezone, then a simple (k)wakeup exec can do what I need at the correct time. I thought TODENABLE might give me a clue, but I don't want a different time, I just want a different view of the same time. :-) Or, I just have to write my own little time calculator to make the adjustment... Not a difficult thing, but if there's a wheel I can use... It's all been done: http://www.iana.org/time-zones http://en.wikipedia.org/wiki/Tz_database IBM simply has a bad case of NIH. And someone points out that even IBM does it on AIX. Can your service machine run Linux? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Multiple timezones?
H, yes, I can run Linux, and in fact have Linux running in the same lpar already. I can just create a Linux Userid (no need for another linux instance) and set their time zone accordingly and use a cron tab to trigger the event. Brilliant! Thanks for the tip. :-) Donald Russell On Friday, August 9, 2013, Paul Gilmartin wrote: On Thu, 8 Aug 2013 22:23:23 -0700, Donald Russell wrote: zVM 6.1 (6.2 coming) The system runs with a UTC timezone, but it would be convenient if I had a userid that could run in a different time zone. UTC doesn't change with Daylight Saving Time, and I have a process I want to schedule at a specific time that is subject to DST changes. i.e. I want something to run at 3:00 AM Pacific Time, in summer and winter. If I can have a disconnected service machine running in the proper timezone, then a simple (k)wakeup exec can do what I need at the correct time. I thought TODENABLE might give me a clue, but I don't want a different time, I just want a different view of the same time. :-) Or, I just have to write my own little time calculator to make the adjustment... Not a difficult thing, but if there's a wheel I can use... It's all been done: http://www.iana.org/time-zones http://en.wikipedia.org/wiki/Tz_database IBM simply has a bad case of NIH. And someone points out that even IBM does it on AIX. Can your service machine run Linux? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu javascript:; with the message: INFO IBM-MAIN -- Sent from iPhone Gmail Mobile -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Multiple timezones?
On Fri, 9 Aug 2013 01:35:52 -0700, Donald Russell wrote: H, yes, I can run Linux, and in fact have Linux running in the same lpar already. I can just create a Linux Userid (no need for another linux instance) and set their time zone accordingly and use a cron tab to trigger the event. Brilliant! Thanks for the tip. :-) One caution: Crontab always uses the system timezone setting; it's oblivious to the user's setting of TZ (unless Linux has an extension). The at command, however, is TZ-savvy, so I've circumvented by using crontab to trigger an event a few hours befor the intended time, which triggers an at command to trigger the event in the desired timezone. Possibly another caution: If the system is halted at the scheduled time, crontab simply skips the event until the next day, unlike WAKEUP which processes the event immediately upon restart. z/OS Unix System Services has some timezone smarts, but, unlike Linux, it is oblivious to legislative changes in timezone conventions. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Multiple timezones?
Thanks Paul, Yes, a quick experiment found that to be true. And my workaround was just what you did, use the at command. Too bad cron doesn't respect the tz of the cron tab owner But apparently there is something called fcron which does. But vanilla cron + at should work fine for what I need. Cheers, Donald Russell On Friday, August 9, 2013, Paul Gilmartin wrote: On Fri, 9 Aug 2013 01:35:52 -0700, Donald Russell wrote: H, yes, I can run Linux, and in fact have Linux running in the same lpar already. I can just create a Linux Userid (no need for another linux instance) and set their time zone accordingly and use a cron tab to trigger the event. Brilliant! Thanks for the tip. :-) One caution: Crontab always uses the system timezone setting; it's oblivious to the user's setting of TZ (unless Linux has an extension). The at command, however, is TZ-savvy, so I've circumvented by using crontab to trigger an event a few hours befor the intended time, which triggers an at command to trigger the event in the desired timezone. Possibly another caution: If the system is halted at the scheduled time, crontab simply skips the event until the next day, unlike WAKEUP which processes the event immediately upon restart. z/OS Unix System Services has some timezone smarts, but, unlike Linux, it is oblivious to legislative changes in timezone conventions. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu javascript:; with the message: INFO IBM-MAIN -- Sent from iPhone Gmail Mobile -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
