Hello Nick,
We change the times when we switched over to the z890.
We used to have the MP3000 set to no time zone (GMT=00.00) and set the
time
to the hour/minute right here in OHIO. Everything was fine except when
we sent emails, which were always 4 or 5 hours off. The times were off
because the servers were set to GMT -5:00.
The z890 time is set to be GMT Eastern time and is -5:00 hours
off of
GMT. We set z/VM to that "proper" time zone.
q timezone
Zone Direction Offset Status
UTC ---- 00.00.00 Inactive
GMT ---- 00.00.00 Inactive
EDT West 04.00.00 Active
EST West 05.00.00 Inactive
We do not set any VSE machine as they default to whatever z/VM
has.
The MP3000 had both z/VM zones and VSE Zones.
Now all emails and ftps that go anywhere have the proper times.
Everyone is happy and the birds are chirping, sky is blue, yadda yadda.
Ed Martin
Aultman Health Foundation
330-588-4723
[EMAIL PROTECTED]
ext. 40441
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
> Behalf Of Nick Laflamme
> Sent: Wednesday, September 06, 2006 10:32 AM
> To: [email protected]
> Subject: MP 3000 console time zone?
>
> Can anyone explain to me the relationship between the time as
displayed
> on our MP/3000's OS/2 Warp sessions and the hardware clock of the
"real
> computer" hosted by the OS/2 Warp system?
>
> This past weekend, as we were coming up after an outage, I decided I
was
> tired of the HMC's time being off by an hour, especially since it
didn't
> put a time zone on date stamps, like in the hardware error message
logs.
> So, I manually fixed the time via the OS/2 clock "properties" page.
>
> When I brought up our z/VM 4.4 system, its clock was off by exactly an
> hour which, alas, I didn't notice. When I came in last night to fix
this
> gaffe, I went looking all over the OS/2 Warp system for some sort of
> timezone setting I could tweak so it'd know we were on EDT, not EST,
and
> so the underlying GMT would be correct.(I hate systems whose nominal
GMT
> times are wrong, especially those that are "local" time, but I
> digress....) Alas, I never could find a time zone setting in OS/2 for
> EDT vs. EST vs. Alaskan time or anything else, and it's been more than
a
> decade since I used an OS/2 system regularly.
>
> I ended up telling z/VM upon IPL that I had to change the hardware
> clock, so that now at least the mainframe GMT is correct, but I have
no
> idea if I have just made a muddle of things or what.
>
> Help?
>
> Thanks,
> Nick
