New timezone daylight savings rule for 2007

Bennett, Carl

2007-01-10 17:32:13 UTC

I thought that the Update 9 patch for VMS 7.3-2 took care of all of the
necessary changes.

I know I tested here without making any changes to the multinet rules
and had time change as expected for next year...

-----Original Message-----
From: Randy Johnson [mailto:***@sxc.com]
Sent: Wednesday, January 10, 2007 12:19 PM
To: info-***@process.com
Cc: ***@process.com
Subject: RE: New timezone daylight savings rule for 2007

I have the following questions:

1. Do I enter the rule as is (with the >= characters)?

2. Do I remove ALL "COMPILED_IN" characters or do I delete the whole
line(s)?

3. How can I test my changes to be sure it will work?

4. How can I tell if Multinet is managing the changing of the time for
daylight savings time?

5. Are there any other changes needed for OpenVMS?

6. Will Process be making a change to enter something other than FIRST
or LAST?

Randy Johnson
SXC Health Solutions

-----Original Message-----
From: Richard Whalen [mailto:***@process.com]
Sent: Tuesday, January 02, 2007 7:31 AM
To: info-***@process.com
Subject: Re: New timezone daylight savings rule for 2007

The parser only recognizes "FIRST" and "LAST".
To get second you have to use

Rule US 2007 DST 1:00 Sunday >= 8 March 2:00
First Sunday November 2:00

For those of you that are making this change, your timezones.local file
must
have the Zone lines
as well as the above rule. You'll want to remove the "COMPILED_IN" from
the
timezones.local file when you copy the rules from timezones.dat

This is probably really an enhancement request more than a query.
VMS 7.3-2, MN 4.4A
I copied timezones.dat to timezones.local and inserted a new line that
defined the start and end dates for use in the US beginning this new
year. The start time is specified as the second sunday of March,
so the added line was
Rule US 2007 DST 1:00 Second Sunday March 2:00 Last
Sunday November
but a $Multinet Set/timezone/select=("US/PACIFIC")
PST/file=multinet:timezones.local
returned: "SECOND" is not a day number, Bad DST Starting time.
So I just hard coded it to the 11th of March. So I'm good for this
year.:)
Roger, Harvey Mudd College

Attention:
The information contained in this message and or attachments is intended only for the person
or entity to which it is addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination or other use of, or taking of any action in reliance
upon, this information by persons or entities other than the intended recipient is prohibited.
If you received this in error, please contact the sender and delete the material from any system
and destroy any copies.
--------------------------------------------------------------------------------
This email message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal
--------------------------------------------------------------------------------