<?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 busy for a detached process in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625665#M71068</link>
    <description>Roberts, Thanks for the suggestions. Can you please guide me for the queued IO read mechanism ?</description>
    <pubDate>Thu, 15 Sep 2005 11:10:35 GMT</pubDate>
    <dc:creator>Sk Noorul  Hassan</dc:creator>
    <dc:date>2005-09-15T11:10:35Z</dc:date>
    <item>
      <title>CPU busy for a detached process</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625657#M71060</link>
      <description>Hi,&lt;BR /&gt;When running  a dcl script as detached procees, it is taking almost 90% of CPU time. The script monitors the system error messages continuously  and  notifies the operator  if it receives any potential error string on message. So, is there any idea how to reduce the  CPU usage or this script can be submitted in other way which will have less impact on the system. Pls suggest..&lt;BR /&gt;</description>
      <pubDate>Wed, 14 Sep 2005 06:03:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625657#M71060</guid>
      <dc:creator>Sk Noorul  Hassan</dc:creator>
      <dc:date>2005-09-14T06:03:03Z</dc:date>
    </item>
    <item>
      <title>Re: CPU busy for a detached process</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625658#M71061</link>
      <description>Hassan,&lt;BR /&gt;&lt;BR /&gt;You can put a reasonable wait in the script loop. The other posibility is to reduce the process priority to minimum but in this case the process will also take all the idle CPU time.&lt;BR /&gt;&lt;BR /&gt;Bojan</description>
      <pubDate>Wed, 14 Sep 2005 06:08:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625658#M71061</guid>
      <dc:creator>Bojan Nemec</dc:creator>
      <dc:date>2005-09-14T06:08:59Z</dc:date>
    </item>
    <item>
      <title>Re: CPU busy for a detached process</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625659#M71062</link>
      <description>How does the DCL procedure monitor the system error messages?</description>
      <pubDate>Wed, 14 Sep 2005 06:09:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625659#M71062</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-09-14T06:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: CPU busy for a detached process</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625660#M71063</link>
      <description>May we assume that you tested the script interactively and it presented a reasonable load, but when putting in production, detached, it became unreasonable?&lt;BR /&gt;&lt;BR /&gt;What timeout / poll mechanisme do you use?&lt;BR /&gt;&lt;BR /&gt;Is is something like a basic SLEEP where it either waits on a time to elaps, or for terminal action? Running detached there will be no terminal to wait on, and a timeout based on that could well fail.&lt;BR /&gt;&lt;BR /&gt;Hein.&lt;BR /&gt;</description>
      <pubDate>Wed, 14 Sep 2005 06:49:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625660#M71063</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2005-09-14T06:49:03Z</dc:date>
    </item>
    <item>
      <title>Re: CPU busy for a detached process</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625661#M71064</link>
      <description>It sounds like detached process run differently from intereactive one.&lt;BR /&gt;May be your dcl procedure asks for interactive terminal and when detached goes into error section and loops infinitely.&lt;BR /&gt;Have you some log?&lt;BR /&gt; &lt;BR /&gt;Antonio Vigliotti&lt;BR /&gt;</description>
      <pubDate>Thu, 15 Sep 2005 01:42:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625661#M71064</guid>
      <dc:creator>Antoniov.</dc:creator>
      <dc:date>2005-09-15T01:42:15Z</dc:date>
    </item>
    <item>
      <title>Re: CPU busy for a detached process</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625662#M71065</link>
      <description>The DCL script uses the f$search to locate for the latest  error which is generated as part of application errors in the system.We keep a log of 500 such errors.  So, whenever any new warning message generates, the dcl script takes this to a file and in a perticular line it searches  for a string, If it gets that string it will notify otherwise it will again go to loop for searching the latest warning message.when I am giving some time wait, the CPU usage gets reduced to almost negligible. But buffered I/O usage looks 10 to 20 in MON SYSTEM command. So, will it be ok to go ahead with a time wait in the loop, as I do not want to miss the error messages.&lt;BR /&gt;&lt;BR /&gt;I am submitting this DCL script using run loginout.exe/input=dcl script/output=nl:/detached  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 15 Sep 2005 06:57:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625662#M71065</guid>
      <dc:creator>Sk Noorul  Hassan</dc:creator>
      <dc:date>2005-09-15T06:57:38Z</dc:date>
    </item>
    <item>
      <title>Re: CPU busy for a detached process</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625663#M71066</link>
      <description>Did you execute that dcl procdure interactively?&lt;BR /&gt;Also try adding /prio=1&lt;BR /&gt; &lt;BR /&gt;Antonio Vigliotti&lt;BR /&gt;</description>
      <pubDate>Thu, 15 Sep 2005 07:03:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625663#M71066</guid>
      <dc:creator>Antoniov.</dc:creator>
      <dc:date>2005-09-15T07:03:55Z</dc:date>
    </item>
    <item>
      <title>Re: CPU busy for a detached process</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625664#M71067</link>
      <description>You might try varying the wait time in the loop.  The amount of CPU used will depend entirely on how long you make the wait time.&lt;BR /&gt;&lt;BR /&gt;I like to use a symbol to set the wait time as a parameter in the beginning of any DCL script.  Then in the wait loop I refer to the symbol:&lt;BR /&gt;&lt;BR /&gt;$ delta_wait = "0:0:10.0"&lt;BR /&gt;$ ...&lt;BR /&gt;&lt;BR /&gt;$LOOP:&lt;BR /&gt;$ &amp;lt; do some things&amp;gt;&lt;BR /&gt;$ wait 'delta_wait'&lt;BR /&gt;$ goto LOOP&lt;BR /&gt;&lt;BR /&gt;Have you thought about setting up another mechanism to receive the messages?  It would be more efficient if you could read the messages continuously with normall queued IO either from a mailbox or shared read access to the file.  Have you considered these and other possibilities?&lt;BR /&gt;&lt;BR /&gt;Robert</description>
      <pubDate>Thu, 15 Sep 2005 08:08:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625664#M71067</guid>
      <dc:creator>Robert_Boyd</dc:creator>
      <dc:date>2005-09-15T08:08:28Z</dc:date>
    </item>
    <item>
      <title>Re: CPU busy for a detached process</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625665#M71068</link>
      <description>Roberts, Thanks for the suggestions. Can you please guide me for the queued IO read mechanism ?</description>
      <pubDate>Thu, 15 Sep 2005 11:10:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625665#M71068</guid>
      <dc:creator>Sk Noorul  Hassan</dc:creator>
      <dc:date>2005-09-15T11:10:35Z</dc:date>
    </item>
    <item>
      <title>Re: CPU busy for a detached process</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625666#M71069</link>
      <description>May we examine the script for constructive comment ?</description>
      <pubDate>Thu, 15 Sep 2005 23:35:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625666#M71069</guid>
      <dc:creator>Thomas Ritter</dc:creator>
      <dc:date>2005-09-15T23:35:05Z</dc:date>
    </item>
    <item>
      <title>Re: CPU busy for a detached process</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625667#M71070</link>
      <description>The programming concepts manual is always a good place to start when looking for other ways to do something.&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/82FINAL/5841/5841PRO.HTML" target="_blank"&gt;http://h71000.www7.hp.com/doc/82FINAL/5841/5841PRO.HTML&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 16 Sep 2005 04:00:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cpu-busy-for-a-detached-process/m-p/3625667#M71070</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-09-16T04:00:24Z</dc:date>
    </item>
  </channel>
</rss>

