Re: Timezone change.

2007-03-22 Thread Evans, Kevin R
On the z/OS side, we had some issues that we raised to IBM via an ETR. We ended 
up adding a line to CEECOPT (LE Options) that specified the month, week and 
time to change the clocks (US East Coast time was a default that we used 
(probably without even realizing it). Certainly, the C localtime calls that we 
do worked correctly with the added line to CEECOPT. An IBM APAR gave us some 
issues as we currently have some of our systems at different PTF levels. Is 
there a similar file to change under z/VM?

Kevin

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jose Raul Baron
Sent: Wednesday, March 21, 2007 5:32 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Timezone change.

Yes, I have also date related problems: 

In Madrid it's now 10'30 local time. But: 

 date
mié mar 21 11:30:45 CET 2007 

The DOW is correct and so is the date but the time is one hour in advance. 
Don't know how to handle this. 

-Mensaje original-
De: Linux on 390 Port [mailto:[EMAIL PROTECTED] En nombre de Goodwin,
Derric
Enviado el: martes, 20 de marzo de 2007 22:56
Para: LINUX-390@VM.MARIST.EDU
Asunto: Re: Timezone change.

We patched all of our z/systems and when we rebooted some of them defaulted
back to UTC and the time was showing off. I reset them via yast to reflect
localtime and everything went well after IPL.

 

The following (DST weekend) I patched all my systems, made sure they were
reflecting localtime and now after IPL they are showing up on UTC time, but
in yast their are showing up as localtime.

 

Any ideas why some of my guests (across different lpars) boot in UTC even
though they show localtime and why some of my guests never had a problem
with this and always ipl into the correct hardware clock mode?

 

Anyone else experience this problem? Could it have something to do with VM
and how the guest is picking up its time on ipl?

 

Thanks.

 

 

 

 


--
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-22 Thread Hodge, Robert L
Kevin,
The corresponding LE change on VM is in the EDCLOCI ASSEMBLE file. 
From the MAINT userid enter:
VMFSETUP ZVM LESFS
CUSTLE ZVM LESFS
select option 3, 'C Locale Time Info'
 
I'm using the following for Eastern time in EDCLOCI ASSEMBLE, right or wrong.

EDCLOCI  EDCLOCTZ TZDIFF=300,TNAME='EST',  *
   DSTSTM=3,DSTSTW=2,DSTSTD=0,STARTTM=7200,SHIFT=3600, *
   DSTENM=11,DSTENW=1,DSTEND=0,ENDTM=7200,DSTNAME='EDT',   *
   UCTNAME='UTC'

After filing the changes, CUSTLE will assemble the file and build the new 
modules.
VMFCOPY the new modules to the MAINT 19E, and save CMS. The LE shared segments
SCEE and SCEEX will have to be rebuild for the new modules.

Also, Language Environment APAR VM64117 / PTF UM31924 provides needed changes 
to several C/C++ library functions.

Reference http://www.vm.ibm.com/service/DST2007.html for z/VM DST changes.
Interestingly, EDCLOCI ASSEMBLE is not mentioned on that web page.

Robert Hodge 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Kevin R
Sent: Thursday, March 22, 2007 3:33 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Timezone change.

On the z/OS side, we had some issues that we raised to IBM via an ETR. We ended 
up adding a line to CEECOPT (LE Options) that specified the month, week and 
time to change the clocks (US East Coast time was a default that we used 
(probably without even realizing it). Certainly, the C localtime calls that we 
do worked correctly with the added line to CEECOPT. An IBM APAR gave us some 
issues as we currently have some of our systems at different PTF levels. Is 
there a similar file to change under z/VM?

Kevin

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jose Raul Baron
Sent: Wednesday, March 21, 2007 5:32 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Timezone change.

Yes, I have also date related problems: 

In Madrid it's now 10'30 local time. But: 

 date
mié mar 21 11:30:45 CET 2007 

The DOW is correct and so is the date but the time is one hour in advance. 
Don't know how to handle this. 

-Mensaje original-
De: Linux on 390 Port [mailto:[EMAIL PROTECTED] En nombre de Goodwin, Derric 
Enviado el: martes, 20 de marzo de 2007 22:56
Para: LINUX-390@VM.MARIST.EDU
Asunto: Re: Timezone change.

We patched all of our z/systems and when we rebooted some of them defaulted 
back to UTC and the time was showing off. I reset them via yast to reflect 
localtime and everything went well after IPL.

 

The following (DST weekend) I patched all my systems, made sure they were 
reflecting localtime and now after IPL they are showing up on UTC time, but in 
yast their are showing up as localtime.

 

Any ideas why some of my guests (across different lpars) boot in UTC even 
though they show localtime and why some of my guests never had a problem with 
this and always ipl into the correct hardware clock mode?

 

Anyone else experience this problem? Could it have something to do with VM and 
how the guest is picking up its time on ipl?

 

Thanks.

 

 

 

 


--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
[EMAIL PROTECTED] with the message: INFO LINUX-390 or visit 
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
[EMAIL PROTECTED] with the message: INFO LINUX-390 or visit 
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
[EMAIL PROTECTED] with the message: INFO LINUX-390 or visit 
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-21 Thread Jose Raul Baron
Yes, I have also date related problems: 

In Madrid it's now 10'30 local time. But: 

 date
mié mar 21 11:30:45 CET 2007 

The DOW is correct and so is the date but the time is one hour in advance. 
Don't know how to handle this. 

-Mensaje original-
De: Linux on 390 Port [mailto:[EMAIL PROTECTED] En nombre de Goodwin,
Derric
Enviado el: martes, 20 de marzo de 2007 22:56
Para: LINUX-390@VM.MARIST.EDU
Asunto: Re: Timezone change.

We patched all of our z/systems and when we rebooted some of them defaulted
back to UTC and the time was showing off. I reset them via yast to reflect
localtime and everything went well after IPL.

 

The following (DST weekend) I patched all my systems, made sure they were
reflecting localtime and now after IPL they are showing up on UTC time, but
in yast their are showing up as localtime.

 

Any ideas why some of my guests (across different lpars) boot in UTC even
though they show localtime and why some of my guests never had a problem
with this and always ipl into the correct hardware clock mode?

 

Anyone else experience this problem? Could it have something to do with VM
and how the guest is picking up its time on ipl?

 

Thanks.

 

 

 

 


--
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-21 Thread Rob van der Heij

On 3/21/07, Jose Raul Baron [EMAIL PROTECTED] wrote:

Yes, I have also date related problems:

In Madrid it's now 10'30 local time. But:

 date
mié mar 21 11:30:45 CET 2007

The DOW is correct and so is the date but the time is one hour in advance.
Don't know how to handle this.


For starters, what does CP say? CP Q TIME tells you z/VM's local time,
and CP Q TIMEZONE shows you the definition of the time zone. You may
be able to issue the commands from Linux if vmcp is set up right.
These two, and your wrist watch, should tell you whether the hardware
clock is UTC.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change. - PJBR

2007-03-21 Thread Jose Raul Baron
CP Q TIME is 
TIME IS 19:16:55 UTC WEDNESDAY 03/21/07

I have changed date in z/Linux into 
Wed Mar 21 19:16:48 CET 2007

Seems to be working fine ... 
So far...


-Mensaje original-
De: Linux on 390 Port [mailto:[EMAIL PROTECTED] En nombre de Rob van
der Heij
Enviado el: miércoles, 21 de marzo de 2007 11:11
Para: LINUX-390@VM.MARIST.EDU
Asunto: Re: Timezone change.

On 3/21/07, Jose Raul Baron [EMAIL PROTECTED] wrote:
 Yes, I have also date related problems:

 In Madrid it's now 10'30 local time. But:

  date
 mié mar 21 11:30:45 CET 2007

 The DOW is correct and so is the date but the time is one hour in advance.
 Don't know how to handle this.

For starters, what does CP say? CP Q TIME tells you z/VM's local time, and
CP Q TIMEZONE shows you the definition of the time zone. You may be able to
issue the commands from Linux if vmcp is set up right.
These two, and your wrist watch, should tell you whether the hardware clock
is UTC.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-21 Thread Rob van der Heij

On 3/20/07, Goodwin, Derric [EMAIL PROTECTED] wrote:


Anyone else experience this problem? Could it have something to do with VM and 
how the guest is picking up its time on ipl?


Linux gets the hardware clock from the machine, which should be UTC.
This is not influenced by the timezone you set on z/VM. So all you
would need on Linux is the proper /etc/localtime for your local
timezone. That should not change upon reboot unless you have managed
to set your hardware clock other than UTC.

Linux also expects its hardware clock to be UTC. There's an exception
for dual-boot PC's that have to deal with that other OS that sets the
hardware clock to the current local time. There's a flag in one of the
config files that tells whether your hardware clock is UTC or local
time. When I looked at this in the past, the hardware clock stuff in
SuSE was broken such that it would cause a random offset for your
Linux server when you specified the clock was not UTC. But obviously
that dual-boot stuff does not apply to System z.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change. - PJBR

2007-03-21 Thread Rob van der Heij

On 3/21/07, Jose Raul Baron [EMAIL PROTECTED] wrote:


CP Q TIME is
TIME IS 19:16:55 UTC WEDNESDAY 03/21/07

I have changed date in z/Linux into
Wed Mar 21 19:16:48 CET 2007

Seems to be working fine ...
So far...


No, it's not. I expect 19:16 was local time for you, in that case CP
should have told you 19:16 CET rather than UTC. Right now you have
your hardware clock at UTC+1. And if Linux thinks the hardware clock
is UTC then that's one hour off. That will continue to trouble you.
Set the clock right at next IPL of z/VM. Then Linux will get the time
right as well.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread Rob van der Heij

On 3/2/07, Mark Post [EMAIL PROTECTED] wrote:


You could just make sure ntp isn't running, and set your system clock to 01:58 
on March 11th, and wait two minutes.  Set it back when you know what happens.


And may I add that CP SET VTOD is way cool for playing with this.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread John Summerfield

Fargusson.Alan wrote:

How do you test today to see that the time change will occur at 2:00 AM on 
March 11?


man date

It can do it. I like the of
date -f list





-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
John Summerfield
Sent: Thursday, March 01, 2007 2:39 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Timezone change.


Little, Chris wrote:



-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Fargusson.Alan
Sent: Thursday, March 01, 2007 11:36 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Timezone change.

 *
 * Note: When you run this program your timezone must be Pacific time.
 *   You might need to do env TZ=PST8PDT dst.
 */

#include stdio.h
#include time.h

/* This is the exact time of the switch in 2007 for Pacific
time. */ #define BASE 1173607200

Or subtract 3600 for each zone east


Whatever that means.


Wouldn't it be preferable to compare between local time and UTC for the
period in question? On Linux, it's a matter of using date -u:
[EMAIL PROTECTED]:~$ date -u;date
Thu Mar  1 22:38:00 UTC 2007
Fri Mar  2 07:38:00 WST 2007
[EMAIL PROTECTED]:~$

A shell script to report the difference would be pretty trivial, and not
require unlikely tools. I don't install a CD on everything. Do you?




--

Cheers
John

-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]

Please do not reply off-list

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390




--

Cheers
John

-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]

Please do not reply off-list

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread Rob van der Heij

Back then I ran a script to create a file every second while I crossed
the time zone. I was really pleased to find the file system keep the
time zone in the time stamp (slide 14 in my presentation).
http://rvdheij.nl/Presentations/2005-L76.pdf

--
Rob van der Heij
Velocity Software, Inc
http://velocitysoftware.com/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread Bill Carlson
On Thu, Mar 01, 2007 at 03:16:08PM -0800, Fargusson.Alan wrote:
 How do you test today to see that the time change will occur at 2:00 AM on 
 March 11?

[EMAIL PROTECTED] ~]$ date -d '2007-03-11 03:00:00'
Sun Mar 11 03:00:00 CDT 2007


Note, the date '2007-03-11 02:00' doesn't exist in a timezone observing US
DST, and date makes note of that:

[EMAIL PROTECTED] ~]$ date -d '2007-03-11 02:00:00'
date: invalid date `2007-03-11 02:00:00'


[EMAIL PROTECTED] ~]$ date -d '2007-03-11 01:59:59'
Sun Mar 11 01:59:59 CST 2007



I recommend this over the zdump test, as the ACTUAL system is exercised,
rather than dumping the data from a file that may not be used.

Finally, remember this is all about timezone display, the actual time in UTC
does NOT change!

--
Bill Carlson
--
Systems Administrator [EMAIL PROTECTED]  | Anything is possible,
HCIS  | given time and money.
University of Iowa Hospitals and Clinics  |
Opinions are mine, not my employer's. |

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread RPN01
Interestingly, on my system (at least the one I tested; SuSE SLES 9
2.6.5-7.283-s390x), I don¹t get the invalid date response:

rockhopper:~ # date
Fri Mar  2 09:33:13 CST 2007
rockhopper:~ # date -d 2007-03-11 1:59 am
Sun Mar 11 01:59:00 CST 2007
rockhopper:~ # date -d 2007-03-12 1:59 am
Mon Mar 12 01:59:00 CDT 2007
rockhopper:~ # date -d 2007-03-11 2:01 am
Sun Mar 11 03:01:00 CDT 2007
rockhopper:~ # date -d 2007-03-11 2:00 am
Sun Mar 11 03:00:00 CDT 2007

It does shift it correctly to the next hour, though.
-- 
   .~.Robert P. Nix Mayo Foundation
   /V\RO-OC-1-13  200 First Street SW
 / ( ) \  507-284-0844   Rochester, MN 55905
^^-^^   - 
In theory, theory and practice are the same, but
 in practice, theory and practice are different.


 From: Bill Carlson [EMAIL PROTECTED]

 On Thu, Mar 01, 2007 at 03:16:08PM -0800, Fargusson.Alan wrote:
 How do you test today to see that the time change will occur at 2:00 AM on
 March 11?
 
 [EMAIL PROTECTED] ~]$ date -d '2007-03-11 03:00:00'
 Sun Mar 11 03:00:00 CDT 2007
 
 
 Note, the date '2007-03-11 02:00' doesn't exist in a timezone observing US
 DST, and date makes note of that:
 
 [EMAIL PROTECTED] ~]$ date -d '2007-03-11 02:00:00'
 date: invalid date `2007-03-11 02:00:00'
 
 
 [EMAIL PROTECTED] ~]$ date -d '2007-03-11 01:59:59'
 Sun Mar 11 01:59:59 CST 2007
 
 
 
 I recommend this over the zdump test, as the ACTUAL system is exercised,
 rather than dumping the data from a file that may not be used.
 
 Finally, remember this is all about timezone display, the actual time in UTC
 does NOT change!


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread Bill Carlson
On Fri, Mar 02, 2007 at 10:36:24AM -0500, Mark Pace wrote:
 On 3/2/07, Bill Carlson [EMAIL PROTECTED] wrote:
 
 [EMAIL PROTECTED] ~]$ date -d '2007-03-11 03:00:00'
 Sun Mar 11 03:00:00 CDT 2007
 
 
 Note, the date '2007-03-11 02:00' doesn't exist in a timezone observing US
 DST, and date makes note of that:
 I recommend this over the zdump test, as the ACTUAL system is exercised,
 rather than dumping the data from a file that may not be used.
 

 Odd.  Mine doesn't display invalid date.  But does display what I would
 expect if working properly
 # date -d '2007-03-11 02:00:00'
 Sun Mar 11 03:00:00 EDT 2007

Your date appears to be 'helpful'. :)

Mine:

[EMAIL PROTECTED] ~]$ date --version
date (GNU coreutils) 6.4
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software.  You may redistribute copies of it under the terms of
the GNU General Public License http://www.gnu.org/licenses/gpl.html.
There is NO WARRANTY, to the extent permitted by law.


--
Bill Carlson
--
Systems Administrator [EMAIL PROTECTED]  | Anything is possible,
HCIS  | given time and money.
University of Iowa Hospitals and Clinics  |
Opinions are mine, not my employer's. |

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread Mark Post
 On Fri, Mar 2, 2007 at 10:29 AM, in message
[EMAIL PROTECTED], Bill Carlson [EMAIL PROTECTED]
wrote: 
-snip-
 I recommend this over the zdump test, as the ACTUAL system is exercised,
 rather than dumping the data from a file that may not be used.

Why do you assume that the date command uses a different file than the general 
system, and hence the date command?


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread Fargusson.Alan
I need to test this on a production system.  There is no time I could change 
the clock.  One of the not so nice things about the change in DST is that it 
puts it right in the middle of the time we have the most returns received.

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Mark Post
Sent: Thursday, March 01, 2007 9:33 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Timezone change.


 On Thu, Mar 1, 2007 at  6:16 PM, in message
[EMAIL PROTECTED],
Fargusson.Alan [EMAIL PROTECTED] wrote: 
 How do you test today to see that the time change will occur at 2:00 AM on 
 March 11?

You could just make sure ntp isn't running, and set your system clock to 01:58 
on March 11th, and wait two minutes.  Set it back when you know what happens.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread Fargusson.Alan
This works on my Linux system, but the z/OS Unix system does not support the -d 
option.

I get an invalid date on date -d '2007-03-11 02:00:00.  This is SuSE 10, date 
--version says the version is 6.4.

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
John Summerfield
Sent: Friday, March 02, 2007 2:40 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Timezone change.


Fargusson.Alan wrote:
 How do you test today to see that the time change will occur at 2:00 AM on 
 March 11?

man date

It can do it. I like the of
date -f list




 -Original Message-
 From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
 John Summerfield
 Sent: Thursday, March 01, 2007 2:39 PM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: Timezone change.


 Little, Chris wrote:

 -Original Message-
 From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
 Behalf Of Fargusson.Alan
 Sent: Thursday, March 01, 2007 11:36 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Timezone change.

  *
  * Note: When you run this program your timezone must be Pacific time.
  *   You might need to do env TZ=PST8PDT dst.
  */

 #include stdio.h
 #include time.h

 /* This is the exact time of the switch in 2007 for Pacific
 time. */ #define BASE 1173607200
 Or subtract 3600 for each zone east

 Whatever that means.


 Wouldn't it be preferable to compare between local time and UTC for the
 period in question? On Linux, it's a matter of using date -u:
 [EMAIL PROTECTED]:~$ date -u;date
 Thu Mar  1 22:38:00 UTC 2007
 Fri Mar  2 07:38:00 WST 2007
 [EMAIL PROTECTED]:~$

 A shell script to report the difference would be pretty trivial, and not
 require unlikely tools. I don't install a CD on everything. Do you?




 --

 Cheers
 John

 -- spambait
 [EMAIL PROTECTED]  [EMAIL PROTECTED]

 Please do not reply off-list

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390



--

Cheers
John

-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]

Please do not reply off-list

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread Fargusson.Alan
The ls command adjust for local time.  On SuSE 10:

[EMAIL PROTECTED]:~ env TZ=PST8PDT ls -l args.class
-rw-rw-r-- 1 f4185 users 419 Feb 16 03:03 args.class
[EMAIL PROTECTED]:~ env TZ=EST5EDT ls -l args.class
-rw-rw-r-- 1 f4185 users 419 Feb 16 06:03 args.class
[EMAIL PROTECTED]:~

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Rob
van der Heij
Sent: Friday, March 02, 2007 3:01 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Timezone change.


Back then I ran a script to create a file every second while I crossed
the time zone. I was really pleased to find the file system keep the
time zone in the time stamp (slide 14 in my presentation).
http://rvdheij.nl/Presentations/2005-L76.pdf

--
Rob van der Heij
Velocity Software, Inc
http://velocitysoftware.com/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread Mark Post
 On Fri, Mar 2, 2007 at 11:15 AM, in message
[EMAIL PROTECTED],
Fargusson.Alan [EMAIL PROTECTED] wrote: 
 I need to test this on a production system.  There is no time I could change 
 the clock.  One of the not so nice things about the change in DST is that it 
 puts it right in the middle of the time we have the most returns received.

Ah, I was thinking in terms of a test guest on z/VM.  Having one system, and 
that one in production, is pretty limiting in what you can do.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-02 Thread Bill Carlson
On Fri, Mar 02, 2007 at 09:01:01AM -0700, Mark Post wrote:
  On Fri, Mar 2, 2007 at 10:29 AM, in message
 [EMAIL PROTECTED], Bill Carlson [EMAIL PROTECTED]
 wrote:
 -snip-
  I recommend this over the zdump test, as the ACTUAL system is exercised,
  rather than dumping the data from a file that may not be used.

 Why do you assume that the date command uses a different file than the 
 general system, and hence the date command?

What?

Using date in this manner uses the system libraries in the same manner
programs should.

zdump just lists the info contained in a timezone file. That doesn't mean the
system is correctly configured to use that specific timezone information.

In a few of the SuSe instances I recently upgraded, some had /etc/localtime
as a copy of the timezone file rather than a symlink. Using a verification
such as date -d (or write something that uses ctime and friends) is the final
Yes, the timezone is correct check.


--
Bill Carlson
--
Systems Administrator [EMAIL PROTECTED]  | Anything is possible,
HCIS  | given time and money.
University of Iowa Hospitals and Clinics  |
Opinions are mine, not my employer's. |

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Timezone change.

2007-03-01 Thread Fargusson.Alan
I wrote a little program to test the timezone change.  Since there has been 
some discussion on the Linux on Z list about this I decided to post it.  At the 
end is the expected output generated from OpenSUSE 10 on Intel.  I also tested 
this on z/OS Unix.

/*
 * Test the DST change for 2007.
 * This program displays the time starting 5 seconds before the switch
 * until 5 seconds after the switch.
 *
 * Note: When you run this program your timezone must be Pacific time.
 *   You might need to do env TZ=PST8PDT dst.
 */

#include stdio.h
#include time.h

/* This is the exact time of the switch in 2007 for Pacific time. */
#define BASE 1173607200

int main( int argc, char **argv )
{
time_t t;
char *p;

for ( t = BASE - 5; t  BASE + 5; t++ ) {
p = ctime( t );
if ( p ) {
fprintf( stdout, %s, p );
} else {
fprintf( stderr, ctime failed\n );
}
}

return 0;
}
[EMAIL PROTECTED]:~/src/misc ./dst
Sun Mar 11 01:59:55 2007
Sun Mar 11 01:59:56 2007
Sun Mar 11 01:59:57 2007
Sun Mar 11 01:59:58 2007
Sun Mar 11 01:59:59 2007
Sun Mar 11 03:00:00 2007
Sun Mar 11 03:00:01 2007
Sun Mar 11 03:00:02 2007
Sun Mar 11 03:00:03 2007
Sun Mar 11 03:00:04 2007
[EMAIL PROTECTED]:~/src/misc

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-01 Thread Little, Chris
 

 -Original Message-
 From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On 
 Behalf Of Fargusson.Alan
 Sent: Thursday, March 01, 2007 11:36 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Timezone change.
 
  *
  * Note: When you run this program your timezone must be Pacific time.
  *   You might need to do env TZ=PST8PDT dst.
  */
 
 #include stdio.h
 #include time.h
 
 /* This is the exact time of the switch in 2007 for Pacific 
 time. */ #define BASE 1173607200

Or subtract 3600 for each zone east

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-01 Thread Mark Pace

I used.
# zdump -v /etc/localtime |grep 2007
/etc/localtime  Sun Mar 11 06:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 EST
isdst=0 gmtoff=-18000
/etc/localtime  Sun Mar 11 07:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 EDT
isdst=1 gmtoff=-14400
/etc/localtime  Sun Nov  4 05:59:59 2007 UTC = Sun Nov  4 01:59:59 2007 EDT
isdst=1 gmtoff=-14400
/etc/localtime  Sun Nov  4 06:00:00 2007 UTC = Sun Nov  4 01:00:00 2007 EST
isdst=0 gmtoff=-18000


--
Mark Pace
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-01 Thread John Summerfield

Little, Chris wrote:




-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of Fargusson.Alan
Sent: Thursday, March 01, 2007 11:36 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Timezone change.

 *
 * Note: When you run this program your timezone must be Pacific time.
 *   You might need to do env TZ=PST8PDT dst.
 */

#include stdio.h
#include time.h

/* This is the exact time of the switch in 2007 for Pacific
time. */ #define BASE 1173607200


Or subtract 3600 for each zone east


Whatever that means.


Wouldn't it be preferable to compare between local time and UTC for the
period in question? On Linux, it's a matter of using date -u:
[EMAIL PROTECTED]:~$ date -u;date
Thu Mar  1 22:38:00 UTC 2007
Fri Mar  2 07:38:00 WST 2007
[EMAIL PROTECTED]:~$

A shell script to report the difference would be pretty trivial, and not
require unlikely tools. I don't install a CD on everything. Do you?




--

Cheers
John

-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]

Please do not reply off-list

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-01 Thread Fargusson.Alan
How do you test today to see that the time change will occur at 2:00 AM on 
March 11?

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
John Summerfield
Sent: Thursday, March 01, 2007 2:39 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Timezone change.


Little, Chris wrote:


 -Original Message-
 From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
 Behalf Of Fargusson.Alan
 Sent: Thursday, March 01, 2007 11:36 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Timezone change.

  *
  * Note: When you run this program your timezone must be Pacific time.
  *   You might need to do env TZ=PST8PDT dst.
  */

 #include stdio.h
 #include time.h

 /* This is the exact time of the switch in 2007 for Pacific
 time. */ #define BASE 1173607200

 Or subtract 3600 for each zone east

Whatever that means.


Wouldn't it be preferable to compare between local time and UTC for the
period in question? On Linux, it's a matter of using date -u:
[EMAIL PROTECTED]:~$ date -u;date
Thu Mar  1 22:38:00 UTC 2007
Fri Mar  2 07:38:00 WST 2007
[EMAIL PROTECTED]:~$

A shell script to report the difference would be pretty trivial, and not
require unlikely tools. I don't install a CD on everything. Do you?




--

Cheers
John

-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]

Please do not reply off-list

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


Re: Timezone change.

2007-03-01 Thread Mark Post
 On Thu, Mar 1, 2007 at  6:16 PM, in message
[EMAIL PROTECTED],
Fargusson.Alan [EMAIL PROTECTED] wrote: 
 How do you test today to see that the time change will occur at 2:00 AM on 
 March 11?

You could just make sure ntp isn't running, and set your system clock to 01:58 
on March 11th, and wait two minutes.  Set it back when you know what happens.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390