<?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: On a VMS cluster, how can you see on which node the Lock manager is running? in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/on-a-vms-cluster-how-can-you-see-on-which-node-the-lock-manager/m-p/4522934#M96645</link>
    <description>Volker,&lt;BR /&gt;&lt;BR /&gt;This is the information we need !! Thanks a lot!</description>
    <pubDate>Wed, 28 Oct 2009 15:23:00 GMT</pubDate>
    <dc:creator>Jan van den Boogaard_1</dc:creator>
    <dc:date>2009-10-28T15:23:00Z</dc:date>
    <item>
      <title>On a VMS cluster, how can you see on which node the Lock manager is running?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/on-a-vms-cluster-how-can-you-see-on-which-node-the-lock-manager/m-p/4522930#M96641</link>
      <description>Question: On a VMS cluster, how can you see on which node the Lock manager is running?</description>
      <pubDate>Wed, 28 Oct 2009 12:49:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/on-a-vms-cluster-how-can-you-see-on-which-node-the-lock-manager/m-p/4522930#M96641</guid>
      <dc:creator>Jan van den Boogaard_1</dc:creator>
      <dc:date>2009-10-28T12:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: On a VMS cluster, how can you see on which node the Lock manager is running?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/on-a-vms-cluster-how-can-you-see-on-which-node-the-lock-manager/m-p/4522931#M96642</link>
      <description>Jan,&lt;BR /&gt;&lt;BR /&gt;it's called DLM - the Distributed Lock Manager ! It's running everywhere...&lt;BR /&gt;&lt;BR /&gt;On a multi-CPU system, you could dedicate ONE CPU to run the lock-manager code and then you would see a LCKMGR_SERVER 'process' always in COM state on that CPU. This feature is called the 'Dedicated CPU Lock Manager'. But if that node is member of a cluster, the 'lock manager' will run on the other nodes as well.&lt;BR /&gt;&lt;BR /&gt;What's the problem ?&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Wed, 28 Oct 2009 12:55:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/on-a-vms-cluster-how-can-you-see-on-which-node-the-lock-manager/m-p/4522931#M96642</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2009-10-28T12:55:13Z</dc:date>
    </item>
    <item>
      <title>Re: On a VMS cluster, how can you see on which node the Lock manager is running?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/on-a-vms-cluster-how-can-you-see-on-which-node-the-lock-manager/m-p/4522932#M96643</link>
      <description>Hallo Volker,&lt;BR /&gt;&lt;BR /&gt;We use Rdb on a cluster and were looking into the possibility to let batchjobs that use the Rdb database , run on the node where the DLM has the highest load, to avoid thrashing of locks between the lock managers on the different nodes.&lt;BR /&gt;To do so, we must somehow measure where the DLm has the highest load.</description>
      <pubDate>Wed, 28 Oct 2009 14:24:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/on-a-vms-cluster-how-can-you-see-on-which-node-the-lock-manager/m-p/4522932#M96643</guid>
      <dc:creator>Jan van den Boogaard_1</dc:creator>
      <dc:date>2009-10-28T14:24:55Z</dc:date>
    </item>
    <item>
      <title>Re: On a VMS cluster, how can you see on which node the Lock manager is running?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/on-a-vms-cluster-how-can-you-see-on-which-node-the-lock-manager/m-p/4522933#M96644</link>
      <description>Jan,&lt;BR /&gt;&lt;BR /&gt;in this case, you need to find out, where the resource tree of the database is being mastered. Then run your batch jobs at that node...&lt;BR /&gt;&lt;BR /&gt;ANAL/SYS&lt;BR /&gt;SDA&amp;gt; LCK SHOW ACT ! available since V7.2-1H1&lt;BR /&gt;&lt;BR /&gt;This will show the most active resources.&lt;BR /&gt;&lt;BR /&gt;There is also SYS$EXAMPLES:RDB$SDA.COM. You can use this procedure to build a RDB$SDA.EXE SDA extension. Then use&lt;BR /&gt;&lt;BR /&gt;$ DEF RDB$SDA dev:&lt;DIR&gt;RDB$SDA.EXE&lt;BR /&gt;$ ANAL/SYS&lt;BR /&gt;SDA&amp;gt; RDB SHOW ACTIVE_DB&lt;BR /&gt;&lt;BR /&gt;This would find the RDB database resource trees and display the desired information. You would be interested in the nodename displayed in the 'Node' column. This is the node mastering the resource tree. If you run your batch jobs on that node, locking operations will be local and a lot faster than 'remote' locking operations.&lt;BR /&gt;&lt;BR /&gt;You can monitor distributing locking operations with MONITOR DLOCK. You want 'local' ENQs/CVTs/DEQs as opposed to incoming or outgoing lock operations.&lt;BR /&gt;&lt;BR /&gt;Volker.&lt;BR /&gt;&lt;/DIR&gt;</description>
      <pubDate>Wed, 28 Oct 2009 15:12:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/on-a-vms-cluster-how-can-you-see-on-which-node-the-lock-manager/m-p/4522933#M96644</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2009-10-28T15:12:16Z</dc:date>
    </item>
    <item>
      <title>Re: On a VMS cluster, how can you see on which node the Lock manager is running?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/on-a-vms-cluster-how-can-you-see-on-which-node-the-lock-manager/m-p/4522934#M96645</link>
      <description>Volker,&lt;BR /&gt;&lt;BR /&gt;This is the information we need !! Thanks a lot!</description>
      <pubDate>Wed, 28 Oct 2009 15:23:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/on-a-vms-cluster-how-can-you-see-on-which-node-the-lock-manager/m-p/4522934#M96645</guid>
      <dc:creator>Jan van den Boogaard_1</dc:creator>
      <dc:date>2009-10-28T15:23:00Z</dc:date>
    </item>
  </channel>
</rss>

