<?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: CPU loop in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/cpu-loop/m-p/4349370#M45148</link>
    <description>Mulder,&lt;BR /&gt;&lt;BR /&gt;do a &lt;BR /&gt;$ SHOW PROC/CONT/ID=&lt;PID-OF-PROCESS-UNDER-INVESTIGATION&gt;&lt;BR /&gt;then type V for a dynamic show of current addresses.&lt;BR /&gt;&lt;BR /&gt;Addresses below %X80000000 are process space, above is system space&lt;BR /&gt;&lt;BR /&gt;HELP is your friend (here HELP SHOW PROC/CONT)&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe&lt;/PID-OF-PROCESS-UNDER-INVESTIGATION&gt;</description>
    <pubDate>Mon, 02 Feb 2009 12:27:08 GMT</pubDate>
    <dc:creator>Jan van den Ende</dc:creator>
    <dc:date>2009-02-02T12:27:08Z</dc:date>
    <item>
      <title>CPU loop</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-loop/m-p/4349369#M45147</link>
      <description>How to find out in which address space is the CPU looping (system space, program space or between the 2) ?&lt;BR /&gt;&lt;BR /&gt;thanks</description>
      <pubDate>Mon, 02 Feb 2009 10:05:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-loop/m-p/4349369#M45147</guid>
      <dc:creator>Mulder_1</dc:creator>
      <dc:date>2009-02-02T10:05:35Z</dc:date>
    </item>
    <item>
      <title>Re: CPU loop</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-loop/m-p/4349370#M45148</link>
      <description>Mulder,&lt;BR /&gt;&lt;BR /&gt;do a &lt;BR /&gt;$ SHOW PROC/CONT/ID=&lt;PID-OF-PROCESS-UNDER-INVESTIGATION&gt;&lt;BR /&gt;then type V for a dynamic show of current addresses.&lt;BR /&gt;&lt;BR /&gt;Addresses below %X80000000 are process space, above is system space&lt;BR /&gt;&lt;BR /&gt;HELP is your friend (here HELP SHOW PROC/CONT)&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe&lt;/PID-OF-PROCESS-UNDER-INVESTIGATION&gt;</description>
      <pubDate>Mon, 02 Feb 2009 12:27:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-loop/m-p/4349370#M45148</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2009-02-02T12:27:08Z</dc:date>
    </item>
    <item>
      <title>Re: CPU loop</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-loop/m-p/4349371#M45149</link>
      <description>Mulder,&lt;BR /&gt;&lt;BR /&gt;welcome to the OpenVMS ITRC forum.&lt;BR /&gt;&lt;BR /&gt;If you have a recent version of OpenVMS (V7.3-2 or higher), you can also use the PCS$SDA extension to capture PC samples in the running system.&lt;BR /&gt;&lt;BR /&gt;$ ANAL/SYS&lt;BR /&gt;SDA&amp;gt; PCS ! contain brief help&lt;BR /&gt;SDA&amp;gt; PCS LOAD&lt;BR /&gt;PCS$DEBUG load status = 00000001&lt;BR /&gt;SDA&amp;gt; pcs start trace&lt;BR /&gt;Sampling started...&lt;BR /&gt;SDA&amp;gt; pcs stop trace&lt;BR /&gt;Sampling stopped...&lt;BR /&gt;SDA&amp;gt; pcs sho trace&lt;BR /&gt;...&lt;BR /&gt;SDA&amp;gt; PCS UNLOAD&lt;BR /&gt;SDA&amp;gt; EXIT&lt;BR /&gt;&lt;BR /&gt;This can be used for looping processes as well, e.g. if you just capture PC sampels from a given process ID.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Mon, 02 Feb 2009 13:15:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-loop/m-p/4349371#M45149</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2009-02-02T13:15:40Z</dc:date>
    </item>
  </channel>
</rss>

