<?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: Image size on VAX in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162915#M41879</link>
    <description>Hein,&lt;BR /&gt;Good shot, but it did not work, the image is still some 24000 blocks</description>
    <pubDate>Thu, 12 Mar 2009 10:53:42 GMT</pubDate>
    <dc:creator>Fekko Stubbe</dc:creator>
    <dc:date>2009-03-12T10:53:42Z</dc:date>
    <item>
      <title>Image size on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162913#M41877</link>
      <description>I have a problem with an executable-size on VAX.&lt;BR /&gt;&lt;BR /&gt;When I compile/link the program (some 55 files) on alpha the image size&lt;BR /&gt;is about 3500 blocks. &lt;BR /&gt;&lt;BR /&gt;The same sources compiled on vax gives me an image of 24000 blocks. &lt;BR /&gt;Looking at the image I see there are a lot of zero pages (upto 16000 contiguous pages).&lt;BR /&gt;I wonder why the linker does not create a new demand zero image section.&lt;BR /&gt;When I add the DZRO_MIN=1 to the linker options file, the size does not change.&lt;BR /&gt;Adding ISD_MAX=96 to the linker options file does not make any difference.&lt;BR /&gt;&lt;BR /&gt;The number of image sections is 27, so the must be room enough for more.&lt;BR /&gt;&lt;BR /&gt;PROCSECTCT is set to 128</description>
      <pubDate>Thu, 12 Mar 2009 09:50:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162913#M41877</guid>
      <dc:creator>Fekko Stubbe</dc:creator>
      <dc:date>2009-03-12T09:50:16Z</dc:date>
    </item>
    <item>
      <title>Re: Image size on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162914#M41878</link>
      <description>&lt;BR /&gt;Try linking with an option file and the option:&lt;BR /&gt;&lt;BR /&gt;UNSUPPORTED = 1 ! force demand zero pages&lt;BR /&gt;&lt;BR /&gt;Groetjes,&lt;BR /&gt;Hein.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Mar 2009 10:26:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162914#M41878</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2009-03-12T10:26:09Z</dc:date>
    </item>
    <item>
      <title>Re: Image size on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162915#M41879</link>
      <description>Hein,&lt;BR /&gt;Good shot, but it did not work, the image is still some 24000 blocks</description>
      <pubDate>Thu, 12 Mar 2009 10:53:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162915#M41879</guid>
      <dc:creator>Fekko Stubbe</dc:creator>
      <dc:date>2009-03-12T10:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: Image size on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162916#M41880</link>
      <description>&lt;BR /&gt;Along with remembering the UNSUPPORTED option I seem to vaguely remember something about their being a 16 bit limit in the maximum number of Dzero pages. There may be a threshold at 65K.&lt;BR /&gt;That would mean that when you need it most, you don't get it!&lt;BR /&gt;Just for an experiment can you reduce the need under 65K pages and see if it gets squished?&lt;BR /&gt;&lt;BR /&gt;Can you divide the space up in clusters?&lt;BR /&gt;&lt;BR /&gt;Ultimately you may be better of using some GETVM / MALLOC / CRMPSC scheme to just grab that memory on the fly.&lt;BR /&gt;&lt;BR /&gt;Hein.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Mar 2009 11:26:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162916#M41880</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2009-03-12T11:26:00Z</dc:date>
    </item>
    <item>
      <title>Re: Image size on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162917#M41881</link>
      <description>After increasing ISD_MAX to 256 the image came down to some 2800 blocks.&lt;BR /&gt;There seems to be a discrepancy between the map (telling me in the image synopsys)&lt;BR /&gt;Number of image sections: 222&lt;BR /&gt;&lt;BR /&gt;And the anal/image looking for "image section"&lt;BR /&gt;pipe ana/ima dix_vax.exe |search sys$input "image section"/noout/stat&lt;BR /&gt;...&lt;BR /&gt;Records matched 155.&lt;BR /&gt;&lt;BR /&gt;In the old  (big image) the map said&lt;BR /&gt;Number of image sections : 95&lt;BR /&gt;and ana/ima said "27"&lt;BR /&gt;&lt;BR /&gt;The 95 is close to the default isd_max of 96.&lt;BR /&gt;&lt;BR /&gt;So summarizing : adding the ISD_MAX=256 solved the problem.&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Mar 2009 11:52:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162917#M41881</guid>
      <dc:creator>Fekko Stubbe</dc:creator>
      <dc:date>2009-03-12T11:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: Image size on VAX</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162918#M41882</link>
      <description>Increasing isd_max in the linker options file solved the problem</description>
      <pubDate>Mon, 16 Mar 2009 09:22:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/image-size-on-vax/m-p/5162918#M41882</guid>
      <dc:creator>Fekko Stubbe</dc:creator>
      <dc:date>2009-03-16T09:22:08Z</dc:date>
    </item>
  </channel>
</rss>

