<?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: Insufficient Fluid pages in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740103#M40994</link>
    <description>And in those situations where the global section names aren't known, perhaps only defined at runtime?</description>
    <pubDate>Tue, 18 Jan 2011 13:58:38 GMT</pubDate>
    <dc:creator>Brian Reiter</dc:creator>
    <dc:date>2011-01-18T13:58:38Z</dc:date>
    <item>
      <title>Insufficient Fluid pages</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740100#M40991</link>
      <description>On an OpenVMS 7-3-2 system, not very recently patched (copy of a production system) engineers get the message "%SYSTEM-F-INSFLPGS, insufficient Fluid Pages available" when trying to use $CRMPSC_GDZRO_64 to allocate memory in the P2 addess space.&lt;BR /&gt;&lt;BR /&gt;The uses creating the sections does have the memory resident resource granted to it.&lt;BR /&gt;&lt;BR /&gt;Other than physical memory what determines the number of fluid pages? Is this something we can adjust via sysgen? Just curious as the manuals don't seem overly clear on this.&lt;BR /&gt;&lt;BR /&gt;cheers&lt;BR /&gt;&lt;BR /&gt;Brian&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 18 Jan 2011 11:54:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740100#M40991</guid>
      <dc:creator>Brian Reiter</dc:creator>
      <dc:date>2011-01-18T11:54:23Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient Fluid pages</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740101#M40992</link>
      <description>&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;Other than physical memory what determines the number of fluid pages?&lt;BR /&gt;&amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;The number of available physical pages: pages not permanently used by vms or users who locked their code or date into memory. That probably includes reserved pages for memory resident section.&lt;BR /&gt;&lt;BR /&gt;Did you reserve the memory? You should. Did you run AUTOGEN after reserving the memory? You should. The registration reserves the memory for your named global section. AUTOGEN then checks whether vms has enough memory left to run the maximum processes etc., which you specified with sysgen parameters.&lt;BR /&gt;&lt;BR /&gt;If you already reserved memory, it may either not be enough for an increased section size or the name changed and you will not get the reserved space.&lt;BR /&gt;&lt;BR /&gt;And yes, buy more memory is almost always an option.</description>
      <pubDate>Tue, 18 Jan 2011 12:37:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740101#M40992</guid>
      <dc:creator>H.Becker</dc:creator>
      <dc:date>2011-01-18T12:37:29Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient Fluid pages</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740102#M40993</link>
      <description>From the system services manual for V8.4 (I didn't see this setion in the V7.3-2 manual.)&lt;BR /&gt;&lt;BR /&gt;If the global section is registered in the Reserved Memory Registry, the size of&lt;BR /&gt;the global section need not match the reserved size. If the global section is not&lt;BR /&gt;registered in the Reserved Memory Registry, or if the reserved size is smaller&lt;BR /&gt;than the size of the global section, the error status SS$_INSFLPGS is returned if&lt;BR /&gt;there are not enough fluid pages in the system to satisfy the request.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Dan</description>
      <pubDate>Tue, 18 Jan 2011 12:37:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740102#M40993</guid>
      <dc:creator>abrsvc</dc:creator>
      <dc:date>2011-01-18T12:37:40Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient Fluid pages</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740103#M40994</link>
      <description>And in those situations where the global section names aren't known, perhaps only defined at runtime?</description>
      <pubDate>Tue, 18 Jan 2011 13:58:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740103#M40994</guid>
      <dc:creator>Brian Reiter</dc:creator>
      <dc:date>2011-01-18T13:58:38Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient Fluid pages</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740104#M40995</link>
      <description>&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;And in those situations where the global section names aren't known, perhaps only defined at runtime?&lt;BR /&gt;&amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;When you register you have to specify the name. The names and sizes are read at system initialization. It's documented in the system manager manual.&lt;BR /&gt;I would try to reserve a memory for a section with an arbitrary name and run AUTOGEN. Then I would remove the section but use the adjusted system parameters. I expect that that would leave enough fluid pages around.&lt;BR /&gt;But I don't have a system available right now and can't test it.</description>
      <pubDate>Tue, 18 Jan 2011 18:12:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740104#M40995</guid>
      <dc:creator>H.Becker</dc:creator>
      <dc:date>2011-01-18T18:12:38Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient Fluid pages</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740105#M40996</link>
      <description>&lt;!--!*#--&gt;In your case INSFLPGS error may be indicating that, memory requirement &lt;BR /&gt;of your application is increased. Reserved memory is a mechanism to &lt;BR /&gt;reserve memory for global section to be created. Global sections allocated &lt;BR /&gt;from reserved memory first if no then from fluid pages. So in your case&lt;BR /&gt;either there is no reserved memory or reserved memory already allocated. &lt;BR /&gt;Now you are trying to create a global for which you don't any physical &lt;BR /&gt;memory left.&lt;BR /&gt;&lt;BR /&gt;Try to recover memory by stopping processes which are not necessary.&lt;BR /&gt;&lt;BR /&gt;To me your case look like needs a memory upgrade, because your application&lt;BR /&gt;has more demand for memory.&lt;BR /&gt;&lt;BR /&gt;-Pramod.</description>
      <pubDate>Wed, 19 Jan 2011 03:38:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/insufficient-fluid-pages/m-p/4740105#M40996</guid>
      <dc:creator>Pramod Kumar M</dc:creator>
      <dc:date>2011-01-19T03:38:21Z</dc:date>
    </item>
  </channel>
</rss>

