Antwort: Re: time journey on a SP node [Virus checked]

• Previous message: Green, Simon: "Re: time journey on a SP node [Virus checked]"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date:         Wed, 3 Nov 2004 12:05:14 +0100
To: aix-l@Princeton.EDU

Yes you are right. I read something about Y2K, but this was a change in the
future, I must go back. But I think this are the same effects.

- We have no SP-switch, so that it isn't a problem.
- host_responds and so on is not so important for the time during the test.
I think only some sp-daemons don't work to this node. But this isn't
critical for the other nodes, or?
- NTP. Yes I must change the environmet for this node so that don't try
automatically to correct the time.
- log files for the application. I think it isn't critical, because I
delete the application after the test....
- yes, I think I want to restore the node (mksysb) after the test.

Best regards,
Frank Mueller

                      "Green, Simon"
                      <Simon.Green@EU.A An: aix-l@Princeton.EDU
                      LTRIA.COM> Kopie:
                      Gesendet von: IBM Thema: Re: time journey on a SP node [Virus checked]
                      AIX Discussion
                      List
                      <aix-l@Princeton.
                      EDU>

                      03.11.2004 11:44
                      Bitte antworten
                      an IBM AIX
                      Discussion List

If you feel up to it, you might like to check back to posts from 1999 when
everyone was doing testing for Y2K: there was a lot of talk of the effects
of changing dates, as I recall.

Setting the time on any SP2 node different to the rest of the cluster is
not
something I would recommend. If you have the SP Switch, that won't work.
You won't get a valid host_responds - which will also affect anything
dependant on that.

Obviously you'll get some very strange log files. Any database
applications
are likely to get a bit confused. Applications producing daily log files
may get confused when they find that the file they want to create already
exists.

NTP will be present, (until you remove it), so it will automatically try to
correct the time, although my experience has been that if the time is too
far out xntpd just fails.

I would plan on re-installing the node and restoring all application data
after the test, just to be on the safe side.

--
Simon Green
Altria ITSC Europe Ltd
AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html
New to AIX? http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX
N.B. Unsolicited email from vendors will not be appreciated.
Please post all follow-ups to the list.
> -----Original Message-----
> From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On
> Behalf Of fmu@OERAG.DE
> Sent: 03 November 2004 10:14
> To: aix-l@Princeton.EDU
> Subject: time journey on a SP node [Virus checked]
>
>
> Hi,
>
> I must test something in our application concerning system time and
> timestamp. The server is a SP-Wide-Node with AIX 5.2_ML02 and PSSP 3.5
> The application runs on a DB2 - Database on version 7.2.
>
> Now I would like to place the system time back (some weeks or
> month). Get I
> problems with the other nodes or the cws? I know I get problems with
> kerberos tickets, rsh-commands and so on for this test-node. But which
 > problems can I get additionally?

• Previous message: Green, Simon: "Re: time journey on a SP node [Virus checked]"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]