<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DTSS behaving strangely ? in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167036#M91682</link>
    <description>BTW : we use this version with unchanged settings since 2003 without any problems.&lt;BR /&gt;&lt;BR /&gt;Found another cluster where only 1 node changed time. The node that changed was up 1185 days, the node that didn't change was up 222 days.&lt;BR /&gt;&lt;BR /&gt;Fwiw&lt;BR /&gt;&lt;BR /&gt;Wim</description>
    <pubDate>Tue, 25 Mar 2008 06:49:02 GMT</pubDate>
    <dc:creator>Wim Van den Wyngaert</dc:creator>
    <dc:date>2008-03-25T06:49:02Z</dc:date>
    <item>
      <title>DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167035#M91681</link>
      <description>We have VMS 7.3 with decnet 7.3 eco 3 (yes I know, not fully patched).&lt;BR /&gt;&lt;BR /&gt;This Sunday time changed twice while it should happend next Sunday. The strange thing is : all our nodes have the same settings but only a subset of 10% (2 clusters and 1 stand alone node) had the problem.&lt;BR /&gt;&lt;BR /&gt;See enclosure for more data.&lt;BR /&gt;&lt;BR /&gt;Why oh Why ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 25 Mar 2008 06:35:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167035#M91681</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-03-25T06:35:29Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167036#M91682</link>
      <description>BTW : we use this version with unchanged settings since 2003 without any problems.&lt;BR /&gt;&lt;BR /&gt;Found another cluster where only 1 node changed time. The node that changed was up 1185 days, the node that didn't change was up 222 days.&lt;BR /&gt;&lt;BR /&gt;Fwiw&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 25 Mar 2008 06:49:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167036#M91682</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-03-25T06:49:02Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167037#M91683</link>
      <description>It could be that the same thing happened before but we only enabled time audit in 2007.</description>
      <pubDate>Tue, 25 Mar 2008 09:30:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167037#M91683</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-03-25T09:30:17Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167038#M91684</link>
      <description>could it be that the latest patches update the DST change rules?&lt;BR /&gt;&lt;BR /&gt;Are the all the systems running the same versions ?</description>
      <pubDate>Tue, 25 Mar 2008 15:34:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167038#M91684</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2008-03-25T15:34:43Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167039#M91685</link>
      <description>All running the 2002 version of DTSS. No patches at all since 2003.&lt;BR /&gt;&lt;BR /&gt;Note that time was changed and 3 minutes later again. A bug ? In that case there should be other victems. I checked release notes but found nothing in that direction.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 25 Mar 2008 15:37:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167039#M91685</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-03-25T15:37:46Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167040#M91686</link>
      <description>The log file clearly shows:&lt;BR /&gt;&lt;BR /&gt;Next TDF Change                   = 2008-03-30-01:59:59.999+01:00I0.000&lt;BR /&gt;&lt;BR /&gt;So this does not look like a TDF change but a time change brought about by the MASTER servers having an incorrect time. Current configuration on this node only requires two servers to make a time change. &lt;BR /&gt;&lt;BR /&gt;This node is configured as a CLERK - have you checked the MASTER nodes to see if they made a time change?</description>
      <pubDate>Tue, 25 Mar 2008 18:17:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167040#M91686</guid>
      <dc:creator>Walter Miller_1</dc:creator>
      <dc:date>2008-03-25T18:17:03Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167041#M91687</link>
      <description>Walter,&lt;BR /&gt;&lt;BR /&gt;The change was at 3:00 sharp ! And the change back 3(!!!) minutes later.&lt;BR /&gt;&lt;BR /&gt;But I checked our 2 providers (again , did it yesterday).&lt;BR /&gt;&lt;BR /&gt;1st : sync at 2:45. Got 3 acceptable date-times. Next sync at 3:45 idem. Nothing happened in between. Nothing in operator log.&lt;BR /&gt;&lt;BR /&gt;2nd : sync at 2:28. Got 3 times. Next sync at 3:28. Nothing in operator log.&lt;BR /&gt;&lt;BR /&gt;None of the 2 nodes connected to the external clocks changed their times. Each node is connected thru a decserver to the 2 external clocks that are about 5 km apart.&lt;BR /&gt;&lt;BR /&gt;There are 2 other nodes not connected to the clock that are server of time. Nothing in their log files and no time change.&lt;BR /&gt;&lt;BR /&gt;Wim&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Mar 2008 06:30:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167041#M91687</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-03-26T06:30:32Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167042#M91688</link>
      <description>Walter,&lt;BR /&gt;&lt;BR /&gt;On the nodes that did change, operator log says :&lt;BR /&gt;DTSS-I-SERTDF DTSS#SERVICE set new timezone differential&lt;BR /&gt;&lt;BR /&gt;So, it did think that it was the change of winter/summer.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 26 Mar 2008 08:14:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167042#M91688</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-03-26T08:14:51Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167043#M91689</link>
      <description>Yes, that definitely looks like it was a TDF change. Are you running a TCPIP stack and if so - what version? I seem to remember there was a UCX$TDF logical in pre-V5.0 that could possibly conflict with DTSS.</description>
      <pubDate>Wed, 26 Mar 2008 13:13:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167043#M91689</guid>
      <dc:creator>Walter Miller_1</dc:creator>
      <dc:date>2008-03-26T13:13:10Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167044#M91690</link>
      <description>TCP 5.3 eco 2. On ALL systems, those that have the problem and those that don't.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 26 Mar 2008 13:17:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167044#M91690</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-03-26T13:17:48Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167045#M91691</link>
      <description>And show logical *tdf* fails on all nodes.</description>
      <pubDate>Wed, 26 Mar 2008 13:34:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167045#M91691</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-03-26T13:34:51Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167046#M91692</link>
      <description>Found that time audit was only enabled on production nodes. Thus found 1 more cluster where it changed.&lt;BR /&gt;&lt;BR /&gt;But we have 50 stations that are clones from 1 node. Most did do the change and some did not (including 1 I checked in the beginning). No relation with uptime or physical location.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 26 Mar 2008 15:58:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167046#M91692</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-03-26T15:58:28Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167047#M91693</link>
      <description>I find that sys$system:dtss$timezone)differential.dat contains a 2nd line with "/03" only. Is that normal ?&lt;BR /&gt;&lt;BR /&gt;It can not be the problem because it's like this on all machines.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Thu, 27 Mar 2008 08:30:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167047#M91693</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-03-27T08:30:49Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167048#M91694</link>
      <description>Time changed without problems (except known ones) last Sunday of Mar. Next TDF correct on all nodes (26/10).</description>
      <pubDate>Mon, 07 Apr 2008 09:00:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167048#M91694</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-04-07T09:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: DTSS behaving strangely ?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167049#M91695</link>
      <description>Went fine on 26/10. Not 1 problem. Next tdf 29/03 as expected.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Mon, 03 Nov 2008 11:54:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dtss-behaving-strangely/m-p/4167049#M91695</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-11-03T11:54:39Z</dc:date>
    </item>
  </channel>
</rss>

