<?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: DST Scripting in a Cluster in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/dst-scripting-in-a-cluster/m-p/5161294#M93619</link>
    <description>What OpenVMS version, and is it matched to current?&lt;BR /&gt;&lt;BR /&gt;Current versions generally deal with this stuff correctly, and automatically.&lt;BR /&gt;&lt;BR /&gt;Changing the times simultaneously or near-simultaneously isn't a big difference; if the boxes derail or the times are skewed, it's usually due to something (else) that happens during the change-over.  (Like CMS access, for instance, or batch job that are kicking off; those can get into trouble during a cluster time skew.)  So yes, better to have the changes occur closer together.&lt;BR /&gt;&lt;BR /&gt;I'd tend to use the provided DAYLIGHT_SAVINGS.COM (sic) command procedure, or use the UTC$TIME_SETUP.COM procedure to make the change.  Going directly after the underlying pieces isn't usually a good idea.  (Unless HP has changed how this stuff works, and is now recommending this approach.)&lt;BR /&gt;&lt;BR /&gt;Or you can forget this particular idea (DST) and move the box to UTC, and leave it there permanently.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://64.223.189.234/node/72" target="_blank"&gt;http://64.223.189.234/node/72&lt;/A&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 04 Mar 2009 19:28:46 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2009-03-04T19:28:46Z</dc:date>
    <item>
      <title>DST Scripting in a Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dst-scripting-in-a-cluster/m-p/5161293#M93618</link>
      <description>We have a standalone node where DST change is handled manually.  The script we've used for years by our operators does the following:&lt;BR /&gt;&lt;BR /&gt;...&lt;BR /&gt;$ UTC$CONFIGURE_TDF := -&lt;BR /&gt;             $SYS$SYSTEM:UTC$CONFIGURE_TDF.EXE&lt;BR /&gt;&lt;BR /&gt;$ UTC$CONFIGURE_TDF "SET" "-420" "+60" -&lt;BR /&gt;          "SYS$COMMON:"   ""&lt;BR /&gt;&lt;BR /&gt;$ (restart NTP here)&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;My question is: this year we also need to do the change manually on a 2-node cluster.  Can the operators simply run the script on each cluster node, or should I script SYSMAN to do both cluster nodes simultaneously?  TIA</description>
      <pubDate>Wed, 04 Mar 2009 18:50:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dst-scripting-in-a-cluster/m-p/5161293#M93618</guid>
      <dc:creator>Jack Trachtman</dc:creator>
      <dc:date>2009-03-04T18:50:27Z</dc:date>
    </item>
    <item>
      <title>Re: DST Scripting in a Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dst-scripting-in-a-cluster/m-p/5161294#M93619</link>
      <description>What OpenVMS version, and is it matched to current?&lt;BR /&gt;&lt;BR /&gt;Current versions generally deal with this stuff correctly, and automatically.&lt;BR /&gt;&lt;BR /&gt;Changing the times simultaneously or near-simultaneously isn't a big difference; if the boxes derail or the times are skewed, it's usually due to something (else) that happens during the change-over.  (Like CMS access, for instance, or batch job that are kicking off; those can get into trouble during a cluster time skew.)  So yes, better to have the changes occur closer together.&lt;BR /&gt;&lt;BR /&gt;I'd tend to use the provided DAYLIGHT_SAVINGS.COM (sic) command procedure, or use the UTC$TIME_SETUP.COM procedure to make the change.  Going directly after the underlying pieces isn't usually a good idea.  (Unless HP has changed how this stuff works, and is now recommending this approach.)&lt;BR /&gt;&lt;BR /&gt;Or you can forget this particular idea (DST) and move the box to UTC, and leave it there permanently.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://64.223.189.234/node/72" target="_blank"&gt;http://64.223.189.234/node/72&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 04 Mar 2009 19:28:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dst-scripting-in-a-cluster/m-p/5161294#M93619</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-03-04T19:28:46Z</dc:date>
    </item>
    <item>
      <title>Re: DST Scripting in a Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dst-scripting-in-a-cluster/m-p/5161295#M93620</link>
      <description>Looks like the HP supplied script is better than mine ;) so we'll use it.  Thanks.</description>
      <pubDate>Wed, 04 Mar 2009 19:55:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dst-scripting-in-a-cluster/m-p/5161295#M93620</guid>
      <dc:creator>Jack Trachtman</dc:creator>
      <dc:date>2009-03-04T19:55:52Z</dc:date>
    </item>
    <item>
      <title>Re: DST Scripting in a Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dst-scripting-in-a-cluster/m-p/5161296#M93621</link>
      <description>Make *sure* you're patched to current for whatever release is in use, as there *have* been bugs here.  And it would not surprise me that there are *still* bugs here.</description>
      <pubDate>Wed, 04 Mar 2009 20:16:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dst-scripting-in-a-cluster/m-p/5161296#M93621</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-03-04T20:16:01Z</dc:date>
    </item>
  </channel>
</rss>

