<?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: Process Quota Exceeded during sys$creprc call in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832875#M34571</link>
    <description>Time to change your user name ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
    <pubDate>Wed, 02 Aug 2006 07:05:50 GMT</pubDate>
    <dc:creator>Wim Van den Wyngaert</dc:creator>
    <dc:date>2006-08-02T07:05:50Z</dc:date>
    <item>
      <title>Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832861#M34557</link>
      <description>I am running VAX/VM V6.2. I have an application that fails after running for weeks. The error is "%SYSTEM-F-EXQUOTA, process quota exceeded". This occurs when my program execuates a sys$creprc. When I look at the account that runs the application has a "Prclm" of 100. When I look at the process it typically has about 11 processes in the job. Sub processes terminate occasionally and others are started over time; but it seems to maintain ~11 concurrent. "Help" suggests this is a limit of concurrent subprocesses. Is this true, or is it in fact cummulative?&lt;BR /&gt;&lt;BR /&gt;Any other ideas on what is causing the error or a remedy?</description>
      <pubDate>Fri, 28 Jul 2006 08:24:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832861#M34557</guid>
      <dc:creator>Craigers</dc:creator>
      <dc:date>2006-07-28T08:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832862#M34558</link>
      <description>prclm is the limit on the number of subprocesses. the EXQUOTA errors indicates a quota was exceeded but does not say which one. It one of the process quotas especially one of the pooled (shared between all jobs in tree) quotas.&lt;BR /&gt;&lt;BR /&gt;Watch quota usage of the process that is creating processes to see which quota. You could use SHOW_QUOTA.COM available from&lt;BR /&gt;&lt;A href="http://dcl.openvms.org/stories.php?story=03/06/03/0022504" target="_blank"&gt;http://dcl.openvms.org/stories.php?story=03/06/03/0022504&lt;/A&gt;&lt;BR /&gt;and other places or use AMDS or Availability Manager. &lt;BR /&gt;</description>
      <pubDate>Fri, 28 Jul 2006 08:41:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832862#M34558</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2006-07-28T08:41:04Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832863#M34559</link>
      <description>From the documentation of the $CREPRC system service:&lt;BR /&gt;&lt;BR /&gt;SS$_EXQUOTA may be returned if:&lt;BR /&gt;&lt;BR /&gt;At least one of the following conditions is true:&lt;BR /&gt; &lt;BR /&gt;- The process has exceeded its quota for the creation of subprocesses. &lt;BR /&gt;&lt;BR /&gt;- A quota value specified for the creation of a subprocess exceeds the creating process's corresponding quota. &lt;BR /&gt;&lt;BR /&gt;- The quota is deductible and the remaining quota for the creating process would be less than the minimum. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/82FINAL/4527/4527pro_026.html" target="_blank"&gt;http://h71000.www7.hp.com/doc/82FINAL/4527/4527pro_026.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The OpenVMS documentation is generally quite good at describing possible reasons for returning an error status.&lt;BR /&gt;&lt;BR /&gt;As a first guess, I would check PGFLQUOTA...&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Fri, 28 Jul 2006 11:39:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832863#M34559</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2006-07-28T11:39:49Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832864#M34560</link>
      <description>Could your limit of processes be reached?&lt;BR /&gt;&lt;BR /&gt;When if fails, does SDA show a quota exhausted?&lt;BR /&gt;</description>
      <pubDate>Sat, 29 Jul 2006 06:30:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832864#M34560</guid>
      <dc:creator>comarow</dc:creator>
      <dc:date>2006-07-29T06:30:13Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832865#M34561</link>
      <description>Still find it disappointing (of HP) that after all these years the quota name isn't specified.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Sun, 30 Jul 2006 15:27:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832865#M34561</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-07-30T15:27:45Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832866#M34562</link>
      <description>&amp;gt;after all these years the quota name isn't specified. &lt;BR /&gt;&lt;BR /&gt;Wim,&lt;BR /&gt;&lt;BR /&gt;  There are process quota specific error messages for all quotas, and have been for several years. BUT engineering hasn't been back over all the ancient code paths to "fix" them. $CREPRC is obviously very, very old. Would you rather engineering spend resources polishing ancient history (and potentially breaking very fundamental things), fixing things that people report as broken, or building new things?&lt;BR /&gt;&lt;BR /&gt;Note the customer is running a decade old version of OpenVMS, so it's feasible (but I think unlikely) that this code path HAS been updated...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 30 Jul 2006 21:21:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832866#M34562</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2006-07-30T21:21:42Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832867#M34563</link>
      <description>John,&lt;BR /&gt;&lt;BR /&gt;I choose that they finish the old stuff first. How many people already lost time because of those bad messages. I did. In the eighties !&lt;BR /&gt;&lt;BR /&gt;Wim&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Jul 2006 02:14:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832867#M34563</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-07-31T02:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832868#M34564</link>
      <description>Thanks for your replies, you may have set me on the right track. I am using SHOW_QUOTA.COM now to monitor my process as suggested. My PGFLQUOTA is creeping up slowly (I'm at 60%; of 100K). Only time will tell, as this process takes a month or so to die.&lt;BR /&gt;&lt;BR /&gt;If we determine PGFLQUOTA increases over time, does it imply a memory leak?&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Tue, 01 Aug 2006 08:14:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832868#M34564</guid>
      <dc:creator>Craigers</dc:creator>
      <dc:date>2006-08-01T08:14:38Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832869#M34565</link>
      <description>No. Each time your program consumes memory via e.g. a mallloc of memory and puts data in it the pgflq will increase.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 01 Aug 2006 08:19:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832869#M34565</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-08-01T08:19:30Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832870#M34566</link>
      <description>pagefile usage should increase then stop increasing. If it does not then either there is a memory leak or your current pgflquo is too small.</description>
      <pubDate>Tue, 01 Aug 2006 08:27:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832870#M34566</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2006-08-01T08:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832871#M34567</link>
      <description>Wim,&lt;BR /&gt;&lt;BR /&gt;if a program only uses malloc to allocate data and never returns it via free, once it's done processing that data, I would call this a 'memory leak'.&lt;BR /&gt;&lt;BR /&gt;You can use ACCOUNTING to look at previous instances of the program aborting. Check the Peak page file: value in those previous accounting records. If the values are all near or equal to PGFLQUOTA, you can be sure, that there is a memory leak. Just double the value of PGFLQUOTA and your process may run twice as long. Make sure you have enough free pagefile space.&lt;BR /&gt;&lt;BR /&gt;Volker.&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Aug 2006 08:44:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832871#M34567</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2006-08-01T08:44:56Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832872#M34568</link>
      <description>Volker,&lt;BR /&gt;&lt;BR /&gt;In that case we have lots of memory leaks over here.&lt;BR /&gt;&lt;BR /&gt;E.g. Sybase server, lots of programs that malloc as the cache needs to be extented (the ING.be bank position is kept in memory), etc.&lt;BR /&gt;&lt;BR /&gt;So, it depends on the program.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 01 Aug 2006 08:48:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832872#M34568</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-08-01T08:48:05Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832873#M34569</link>
      <description>I agree with both of you. I should have added the caveat: "if my application is not designed to accumulate anything". In general, a steady memory usage increase in my application would be unexpected. We're holding steady at 60%... /yawn&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Craig</description>
      <pubDate>Tue, 01 Aug 2006 09:56:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832873#M34569</guid>
      <dc:creator>Craigers</dc:creator>
      <dc:date>2006-08-01T09:56:45Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832874#M34570</link>
      <description>Craig,&lt;BR /&gt;&lt;BR /&gt;next time you start this process, consider to use SET PROC/DUMP or RUN/DUMP. This should create a process dump (imagename.DMP) on a fatal error. You could then ANAL/PROC that dump - maybe to find out, what kind of data is being stored in process memory (typically at high end of P0 space for a memory leak, as the address space will expand continously).&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Tue, 01 Aug 2006 10:18:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832874#M34570</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2006-08-01T10:18:38Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832875#M34571</link>
      <description>Time to change your user name ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 02 Aug 2006 07:05:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832875#M34571</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-08-02T07:05:50Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832876#M34572</link>
      <description>Ok, maybe this user name is better... At least it seems more reusable! haha, thanks!&lt;BR /&gt;&lt;BR /&gt;Craig</description>
      <pubDate>Thu, 03 Aug 2006 09:58:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832876#M34572</guid>
      <dc:creator>Craigers</dc:creator>
      <dc:date>2006-08-03T09:58:16Z</dc:date>
    </item>
    <item>
      <title>Re: Process Quota Exceeded during sys$creprc call</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832877#M34573</link>
      <description>Craig,&lt;BR /&gt;&lt;BR /&gt;since you are new to this community, I would like to point out&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/helptips.do?#33" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/helptips.do?#33&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Thu, 03 Aug 2006 15:40:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/process-quota-exceeded-during-sys-creprc-call/m-p/3832877#M34573</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2006-08-03T15:40:09Z</dc:date>
    </item>
  </channel>
</rss>

