On Thu, Oct 27, 2005 at 06:51:51PM -0400, Ed Finnell ([EMAIL PROTECTED]) wrote:
[EMAIL PROTECTED] writes:
ACROBAT READER 7.0.5 was recently released and so far it seems to be
working fine. It's a big update, something like 9+ Mb.
Yup, autoupdate picked it up and another reboot.
Aren't
I'm not sure, but I think IDMS (we are 14.2) still can't handle moving
back an hour so we need to leave it down.
Last year (2004) for the change to EDT we had an operator who thought
they remembered how to change the time on the sysplex timers, ended up
changing GMT time instead of the local
In a message dated 10/27/2005 2:45:48 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
Does anybody reboot their PC due to DST?
No, but I average about 5 times a week for updates, anti-virus,
spyware, ad-ware, on a pretty vanilla system.
[EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]...
In a message dated 10/27/2005 2:45:48 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
Does anybody reboot their PC due to DST?
No, but I average about 5 times a week for updates, anti-virus,
spyware, ad-ware, on
In a recent note, Ed Finnell said:
Date: Thu, 27 Oct 2005 08:54:10 EDT
In a message dated 10/27/2005 2:45:48 A.M. Central Standard Time,
[log in to unmask] writes:
Does anybody reboot their PC due to DST?
No, but I average about 5 times a week for updates, anti-virus,
In a message dated 10/27/2005 8:29:36 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
And not for hangups, blue screens, Dr Watson interventions and other
unsolicited interruptions? You have a nice machine... -;)
ACROBAT READER(7.0.3) is still a little flaky, but if I don't
But I perceive a significant dearth of objectivity in this thread.
Admit it. The PFCSKs are right on this one. There's no justification
nowadays for a requirement to POR (not just IPL, mind you, POR) to
make certain clock changes. Shrug. It's just something the
designers of the TOD clock
] On Behalf
Of Jon Brock
Sent: Wednesday, October 26, 2005 1:07 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Time change this weekend.
Standard answer: It depends.
If your OS and systems software is up to date and you have your OS
configured to run off of GMT and an offset, there is probably no need
? It doesn't require to be down
an
hour, but it is still a change that must be remembered.
Craig
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf
Of Jon Brock
Sent: Wednesday, October 26, 2005 1:07 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Time change
I agree. You can tell everyone all you want about how the mainframe
runs the business-critical applications, that it can handle I/O out the wazoo
(painful concept, when you think about it), how other platforms are only now
implementing things that MVS has had for years, but when you
I am new to this company here and one of the things they do is to shut
the system down on the fall time change and wait one hour before they
bring the system back up. Outside of scheduler issues, is there any
reason to do this? One that keeps coming up is the timestamp on VSAM
files being an
Cletus,
The key to all this is that GMT=GMT on your system, and NOT GMT=LOCAL
time.
If the latter, you will have problems when you change time without
Waiting an hour. Quite sometime ago IBM time proofed almost
Everything by using GMT(which doesn't change) for everything. Of
Course there
Use of time-of-day as a KEY has us shutting down for an hour each year.
Cheers!
JD
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of McGee, Cletus
Sent: Wednesday, October 26, 2005 10:33 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Time change
In a recent note, Jerry Durbin said:
Date: Wed, 26 Oct 2005 10:48:04 -0600
Use of time-of-day as a KEY has us shutting down for an hour each year.
Use GMT instead of local time as the KEY.
-- gil
--
StorageTek
INFORMATION made POWERFUL
, David
Sent: Wednesday, October 26, 2005 9:47 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Time change this weekend.
Cletus,
The key to all this is that GMT=GMT on your system, and NOT GMT=LOCAL
time.
If the latter, you will have problems when you change time without
Waiting an hour. Quite sometime
On Wed, 26 Oct 2005 11:33:12 -0500, McGee, Cletus [EMAIL PROTECTED]
wrote:
I am new to this company here and one of the things they do is to shut
the system down on the fall time change and wait one hour before they
bring the system back up. Outside of scheduler issues, is there any
reason to do
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Wunderlich
Sent: Wednesday, October 26, 2005 2:33 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Time change this weekend.
snip
Cletus,
We run GMT=GMT and all of our system
We have deemed it not worth the
trouble to root
out and fix all the affected code. We just take the outage.
Has anybody on the other side tried to use this as an argument that
z/OS is so poorly designed that it cannot stand changing the clock
without an outage?
...
It's not z/OS! MVS has been
In a message dated 10/26/2005 3:59:07 P.M. Central Standard Time,
[EMAIL PROTECTED] writes:
If you had the same gooberware running under WINTEL, that didn't log
properly, the OS can't help you there, either.
Ever tried to add a 'Time change independent' to an RFP for
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL
Sent: Tuesday, October 25, 2005 7:00 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Time change this weekend.
We have deemed it not worth the
trouble to root
out and fix all
On Wed, 26 Oct 2005 15:31:03 -0500, McKown, John
[EMAIL PROTECTED] wrote:
Has anybody on the other side tried to use this as an argument that
z/OS is so poorly designed that it cannot stand changing the clock
without an outage? Around here, any glitch, however minor, is taken up
by the Windows
21 matches
Mail list logo
