<?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: different TDF in a cluster? in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188110#M61909</link>
    <description>and some tools like Cyrano (appeared for W2K testing in 1999 or before) "play" with the time. That may suit your needs.</description>
    <pubDate>Tue, 10 Feb 2004 16:27:41 GMT</pubDate>
    <dc:creator>labadie_1</dc:creator>
    <dc:date>2004-02-10T16:27:41Z</dc:date>
    <item>
      <title>different TDF in a cluster?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188108#M61907</link>
      <description>Is it possible to run nodes with diffent time zones in a cluster. The nodes will have their own system disk (as they are at diffent sites).&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Feb 2004 13:13:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188108#M61907</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-02-10T13:13:00Z</dc:date>
    </item>
    <item>
      <title>Re: different TDF in a cluster?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188109#M61908</link>
      <description>I do not have a direct response to this problem. But if memory serves me, there used to be a tool that allowed different users to use different times. So a user USER1 could send batches with a time of 2 years ago, a USER2 could use a time of next year...&lt;BR /&gt;&lt;BR /&gt;It was a hack (what a surprise !) :-)&lt;BR /&gt;&lt;BR /&gt;and needed some more code to work with Vms 7.3+</description>
      <pubDate>Tue, 10 Feb 2004 16:16:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188109#M61908</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2004-02-10T16:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: different TDF in a cluster?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188110#M61909</link>
      <description>and some tools like Cyrano (appeared for W2K testing in 1999 or before) "play" with the time. That may suit your needs.</description>
      <pubDate>Tue, 10 Feb 2004 16:27:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188110#M61909</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2004-02-10T16:27:41Z</dc:date>
    </item>
    <item>
      <title>Re: different TDF in a cluster?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188111#M61910</link>
      <description>One such tool is datesim from software partners&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.sp32.com/" target="_blank"&gt;http://www.sp32.com/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Besides of the general confusion a cluster in several timezones is sure to create (have fun with submit/after to generic queues ;-) Problem might also be cluster communication if the timestamps of messages differ to wildly.&lt;BR /&gt;&lt;BR /&gt;Greetings, Martin</description>
      <pubDate>Tue, 10 Feb 2004 18:52:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188111#M61910</guid>
      <dc:creator>Martin P.J. Zinser</dc:creator>
      <dc:date>2004-02-10T18:52:36Z</dc:date>
    </item>
    <item>
      <title>Re: different TDF in a cluster?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188112#M61911</link>
      <description>Ian,&lt;BR /&gt;&lt;BR /&gt;  There is no supported way to operate a cluster with any substantial difference in times between nodes. Odd things happen!&lt;BR /&gt;&lt;BR /&gt;  Although there are numerous tricks and hacks which can give the appearance of different times or time zones between nodes or processes, there are architectural reasons why these won't work in 100% of cases. Unfortunately "time" under OpenVMS wasn't abstracted enough in the original design, so there isn't a single place to catch requests. Dates and times are distributed too far and wide. For example, consider date stamps on every file. You'd need to know the zone of the writer in order to translate it into the zone of the reader. &lt;BR /&gt;&lt;BR /&gt;  Individual processes can explicitly manipulate times using the various time services, but there is no way to (safely) do it transparently.&lt;BR /&gt;&lt;BR /&gt;  (ideally, any OS will keep track of, and store all times in UTC. It's then possible for each process to impose its own timezone when displaying the time. OpenVMS doesn't do this, so we're stuck with the single time zone per node model. Changing this would be an horrendous project).</description>
      <pubDate>Tue, 10 Feb 2004 19:34:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188112#M61911</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2004-02-10T19:34:50Z</dc:date>
    </item>
    <item>
      <title>Re: different TDF in a cluster?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188113#M61912</link>
      <description>Ian,&lt;BR /&gt;&lt;BR /&gt;We use DATESIM (from Software Partners) although we are not using it in a cluster.  The "system" runs at GMT and each "user" has their own timezone defined.  Because of the separation of user and system activity this would continue to work within a cluster (for our situation).  If you run all the systems at GMT (or at least in the same timezone) and have the user activity the only thing that is fiddled with, then it should work -- it would depend entirely on the software you are using and the types of user activity involved.&lt;BR /&gt;(I am not affiliated in any way with Software Partners or the creator of DATESIM)&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Dave</description>
      <pubDate>Tue, 10 Feb 2004 20:57:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188113#M61912</guid>
      <dc:creator>David B Sneddon</dc:creator>
      <dc:date>2004-02-10T20:57:08Z</dc:date>
    </item>
    <item>
      <title>Re: different TDF in a cluster?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188114#M61913</link>
      <description>Hi Ian,&lt;BR /&gt;&lt;BR /&gt;If your systems are at differen locations, and not sharing system and data storage, then why you want them to be in cluster ? Why not separate system networked together...and using NFS, DFS etc..&lt;BR /&gt;&lt;BR /&gt;Thanks &amp;amp; regards,&lt;BR /&gt;Lokesh Jain</description>
      <pubDate>Wed, 11 Feb 2004 03:23:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188114#M61913</guid>
      <dc:creator>Lokesh_2</dc:creator>
      <dc:date>2004-02-11T03:23:44Z</dc:date>
    </item>
    <item>
      <title>Re: different TDF in a cluster?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188115#M61914</link>
      <description>thank you for your thoughts. As its not supported then I will have to think about non-clustered configurations or keeping the cluster on the same timezone.</description>
      <pubDate>Wed, 11 Feb 2004 04:06:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/different-tdf-in-a-cluster/m-p/3188115#M61914</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-02-11T04:06:03Z</dc:date>
    </item>
  </channel>
</rss>

