Not many chances in production for sure, but if you happened to do a restart at some point I trust your e-mail would show up at 8:15 again instead of the 9:15 you are seeing it the last couple of times. Actually deactivating your chore (wait at least 5 seconds) and activating it again will do the trick as well come to think of it.
Original Message:
Sent: Tue April 02, 2024 05:25 AM
From: Wim Gielis
Subject: Chores and Daylight Savings Time (DST)
Hello Hubert,
Thanks. I can confirm that what I showed, was done before the DST switch.
However, no model restart was done. It did not occur to me that that was needed/a good test to try.
There aren't many chances in a year to test this behaviour, unless we change the server clock or something like that ?
All the best,
Wim
------------------------------
Wim Gielis
Original Message:
Sent: Tue April 02, 2024 04:51 AM
From: Hubert Heijkers
Subject: Chores and Daylight Savings Time (DST)
Hoi Wim,
You got all these shores set to DSTSensitive now but you did update them on Saturday to become like that right? Before that they were not DSTSensitive correct? Did you restart the server since those updates of these DSTSensitive flags?
I'm asking because, trying to understand all the logic around it, I've gotten suspicious of the fact that this DSTSensitive flag, whilst correctly set on the Chore, might not get updated on the scheduler thread on which I see that value being cached.
------------------------------
Hubert Heijkers
STSM, Program Director TM1 Functional Database Technology and OData Evangelist
Original Message:
Sent: Mon April 01, 2024 09:34 AM
From: Wim Gielis
Subject: Chores and Daylight Savings Time (DST)
Hi @Svetlana Pestsova, @Hubert Heijkers
That would be very good, thanks. But, unfortunately, I don't have the impression that the DST setting is honoured.
To give a bit more context, I have a daily chore that sends an email to myself. In local times, please find below the timings (I deleted some emails but the pattern is clear):
All chores are DSTSensitive = True.
The server message log is shown too. It's in UTC timings. To prove the latter, I ran a process manually just now (3.36 PM local time) and it is registered as 1.26 PM.
I have no clue what I should still do to get consistent local timings.
Thanks,
Wim
------------------------------
Wim Gielis
Original Message:
Sent: Sun March 31, 2024 08:51 PM
From: Svetlana Pestsova
Subject: Chores and Daylight Savings Time (DST)
Thank you for the ask/info,
We'd add the option to select DST to the Workbench,
Best regards,
------------------------------
Svetlana Pestsova
IBM Planning Analytics Product Manager
Original Message:
Sent: Sat March 30, 2024 03:55 PM
From: Wim Gielis
Subject: Chores and Daylight Savings Time (DST)
Thanks Hubert. With this REST API call I was able to PATCH the chores, so all good.
I agree, that checkbox in the interface would be useful. Including a multi-select of more than 1 chore and applying the action of, in this case, the DST sensitivity.
------------------------------
Wim Gielis
Original Message:
Sent: Fri March 29, 2024 09:18 PM
From: Hubert Heijkers
Subject: Chores and Daylight Savings Time (DST)
Hoi Wim,
Realize we just hit 24 hours before we change to DST but TM1 does support what you are asking for. It is correct that TM1 has always stored the start time in UTC (to be independent of local system settings) but at the same time has a DSTSensitive property/flag which, when set to true, will cause the start time to be offset accordingly and as such result in the start time remaining the same in local time.
If PA doesn't allow you to set this property/flag (which they should add/fix) than I'd quickly download Arc from our friends at Cubewise and use it to check that Daylight Savings Sensitive check-box there. Obviously you can also quickly PATCH the chore using the REST API and pass `{"DSTSensitive": true}`as the payload as well.
Happy Easter!
------------------------------
Hubert Heijkers
STSM, Program Director TM1 Functional Database Technology and OData Evangelist
Original Message:
Sent: Wed March 27, 2024 08:38 AM
From: Wim Gielis
Subject: Chores and Daylight Savings Time (DST)
Hello,
Through an IBM support ticket, my gut feeling was confirmed. Chores run on UTC, not local time.
This has implications for potentially all chores and the upcoming Easter weekend we might face issues. A warned man counts as two.
No willingness at IBM to change this behaviour. An idea was loaded 3 years ago, it's not under consideration and we need to use IBM Cognos Command Center.
Best regards,
Wim
------------------------------
Wim Gielis
Original Message:
Sent: Mon March 25, 2024 06:53 AM
From: Wim Gielis
Subject: Chores and Daylight Savings Time (DST)
Hello all,
This may seem an easy topic but I still have my doubts. My part of the world is Western Europe and we use CET, which is now UTC + 1 hour. Next Sunday, we jump to DST and it will be UTC + 2 hours.
I am asking myself the question whether we need to update chores given this change in timings.
What you actually require is that a chore, running now at 6 AM LOCAL time, remains at 6 AM local time in DST.
PAW and Architect have different settings, where Architect allows the choice of Local or UTC. PAW does not offer a choice.
What is strange: when I create 2 new chores in Architect and set them to 6 AM, one with Local, one with UTC, they show the same when refreshed in PAW !
Does anyone have a clear and correct guide on this ? What to do, if anything ? What to do end of October when leaving DST and going back to normal ?
Create the chore in PAW (with no choice), or create in Architect (then, how ?). Creating a chore in the NEW (DST) time on Sunday morning to force them in the, then active, timing ?
Many thanks,
Wim
------------------------------
Wim Gielis
------------------------------