Operating System - HP-UX
1752689 Members
5486 Online
108789 Solutions
New Discussion

Re: 2011 Russian DST change

 
Dennis Handly
Acclaimed Contributor

Re: 2011 Russian DST change

>Leave it alone and simply create the TZ variable

 

The trouble with a naked TZ variable as described in environ(5), without tztab(4) to back it up, it only works for this year.  It won't tell you the correct time last year nor possibly in the future

Alexander Selektor
Occasional Advisor

Re: 2011 Russian DST change

Is there any news about the patch of the Russian time zones for HP-UX? Change zonetab the only solution right now?


Please check me. 

It was: Moscow Time - UTC +3 with daylight saving time ( UTC+4).

It became: Moscow Time - UTC +4 without daylight saving time

We have in tztab:

# Western Russia (Moscow) Time, Western Russia (Moscow) Daylight Savings
# Time
WST-3WSTDST
0 3 25-31 3  1983-2038 0   WSTDST-4
0 2 24-30 9  1983-1995 0   WST-3
0 2 25-31 10 1996-2038 0   WST-3

 Changed for:

 

# Western Russia (Moscow) Time, Western Russia (Moscow) Daylight Savings
# Time
WST-3WSTDST
0 3 25-31 3  1983-2011 0   WSTDST-4
0 2 24-30 9  1983-1995 0   WST-3
0 2 25-31 10 1996-2010 0   WST-3
0 2 25-31 10 2011-2038 0   WST-4

Is it correct?

 

Thank you!

Dennis Handly
Acclaimed Contributor

Re: 2011 Russian DST change

>Is there any news about the patch of the Russian time zones for HP-UX? Change tztab the only solution right now?

 

Has someone made an official request for a HP-UX patch?  Last time I checked, there wasn't one.  I'll ask again.

 

>Is it correct?

 

Almost, using Clay's dst.pl I get:

$ TZ=WST-3WSTDST dst.pl -y 2011

Sun Mar 27 01:59:59 WST 2011 --> Sun Mar 27 03:00:00 WSTDST 2011

Sun Oct 30 01:59:59 WSTDST 2011 --> Sun Oct 30 02:00:00 WST 2011  # no shift

$ TZ=WST-3WSTDST dst.pl -y 2012

# Return exit status 2

 

Note: For the year 2012, you must use the timezone WST-4 and not WST-3WSTDST.  Otherwise my program indicates some hour shifts:

$ TZ=WST-3WSTDST a.out

Tue Feb 01 00:00:00 2011 WST

Wed Jun 01 01:00:00 2011 WSTDST

Thu Dec 01 00:00:00 2011 WST

Wed Feb 01 01:00:00 2012 WST # extra shift

Fri Jun 01 01:00:00 2012 WST # extra shift

Sat Dec 01 01:00:00 2012 WST # extra shift

$ TZ=WST-4 a.out

Wed Feb 01 00:00:00 2012 WST

Fri Jun 01 00:00:00 2012 WST

Sat Dec 01 00:00:00 2012 WST

Alexander Selektor
Occasional Advisor

Re: 2011 Russian DST change

Dennis,

 

What is it a "Clay's dst.pl"? How it's work?

Dennis Handly
Acclaimed Contributor

Re: 2011 Russian DST change

>What is a "Clay's dst.pl"? How it's work?

 

Clay is the #2 guy on the EBC forum.  dst.pl is a perl script that searches for DST transitions.

A forum search for dst.pl should find it or a bunch of dead links that you also need to search.  ;-)

http://h30499.www3.hp.com/t5/tag/dst.pl/tg-p/category-id/itrc-117

Dennis Handly
Acclaimed Contributor

Re: 2011 Russian DST change

>Last time I checked, there wasn't one.  I'll ask again.

 

Ok, good news.  They are working on an unofficial patch, perhaps released next week.

mist98
Occasional Visitor

Re: 2011 Russian DST change

Hello, guys! I already have an unofficial tztab patches for hp-ux. Who needs can take it here: 

[broken link removed on 03-22-2017 by Admin]

Alexander Selektor
Occasional Advisor

Re: 2011 Russian DST change

 

This patch changes the tztab (almost same what I suggested above):

 

# Western Russia (Moscow) Time, Western Russia (Moscow) Daylight Savings
# Time
WST-3WSTDST
0 3 25-31 3  1983-2011 0   WSTDST-4
0 2 24-30 9  1983-1995 0   WST-3
0 2 25-31 10 1996-2010 0   WST-3
0 2 25-31 10 2011      0   WST-4

 

You think it is right?

Dennis Handly
Acclaimed Contributor

Re: 2011 Russian DST change

>You think it is right?

 

I would have to test it out but I think you still have to use WST-4 for future years.

And you will not be able to use one TZ value to get past and future times accurately.

Dennis Handly
Acclaimed Contributor

Re: 2011 Russian DST change

I tested out the tztab(4) entry.  It seems it works fine for 2011 and also for future years!

 

BTW, I just learned that the Olson database is shutdown because of a lawsuit:

[broken link removed on 03-22-2017 by Admin]