<?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 lib$spawn returns LOGIN-F-CLISYMTBL in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/lib-spawn-returns-login-f-clisymtbl/m-p/3519512#M67678</link>
    <description>I have an OpenVMS Alpha 7.1 system.  We're installed a new version of our application package and we're receiving intermittant failures on a LIB$SPAWN call.  &lt;BR /&gt;&lt;BR /&gt;Nothing else has changed, so I guess this new (larger) image is hitting some type of limit.&lt;BR /&gt;&lt;BR /&gt;I would first check virtualpagecnt, but that shows in sysgen as an 'obsolete' parameter.  Of course, the 'system messages' doc talks about virtualpagecnt.&lt;BR /&gt;&lt;BR /&gt;Any ideas of what specific parameters to review?&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
    <pubDate>Wed, 06 Apr 2005 14:09:13 GMT</pubDate>
    <dc:creator>Mark Cunningham</dc:creator>
    <dc:date>2005-04-06T14:09:13Z</dc:date>
    <item>
      <title>lib$spawn returns LOGIN-F-CLISYMTBL</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lib-spawn-returns-login-f-clisymtbl/m-p/3519512#M67678</link>
      <description>I have an OpenVMS Alpha 7.1 system.  We're installed a new version of our application package and we're receiving intermittant failures on a LIB$SPAWN call.  &lt;BR /&gt;&lt;BR /&gt;Nothing else has changed, so I guess this new (larger) image is hitting some type of limit.&lt;BR /&gt;&lt;BR /&gt;I would first check virtualpagecnt, but that shows in sysgen as an 'obsolete' parameter.  Of course, the 'system messages' doc talks about virtualpagecnt.&lt;BR /&gt;&lt;BR /&gt;Any ideas of what specific parameters to review?&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Wed, 06 Apr 2005 14:09:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lib-spawn-returns-login-f-clisymtbl/m-p/3519512#M67678</guid>
      <dc:creator>Mark Cunningham</dc:creator>
      <dc:date>2005-04-06T14:09:13Z</dc:date>
    </item>
    <item>
      <title>Re: lib$spawn returns LOGIN-F-CLISYMTBL</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lib-spawn-returns-login-f-clisymtbl/m-p/3519513#M67679</link>
      <description>&lt;BR /&gt;The text for $HELP/MESS CLISYMTBL has improved in VMS V7.3-1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;How about changing the parameter with the very name your are worried about: CLISYMTBL&lt;BR /&gt;This is a dynamic param.&lt;BR /&gt;On my 7.1 system it looks like:&lt;BR /&gt;&lt;BR /&gt;SYSGEN&amp;gt;  SHOW CLISYMTBL&lt;BR /&gt;Parameter Name           Current    Default     Min.      Max.     Unit  Dynamic&lt;BR /&gt;--------------           -------    -------    -------   -------   ----  -------&lt;BR /&gt;CLISYMTBL                     512        512        48       1024 Pagelets   D&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;You may want to look at the number of logical names before and afer the change.&lt;BR /&gt;&lt;BR /&gt;Any chance to push some logical over from process to job or a dedicated logical name table? The process ones will be cloned for a spawn. That is a lot of resources (cpu and memory).&lt;BR /&gt;&lt;BR /&gt;Hein.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Apr 2005 14:24:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lib-spawn-returns-login-f-clisymtbl/m-p/3519513#M67679</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2005-04-06T14:24:37Z</dc:date>
    </item>
    <item>
      <title>Re: lib$spawn returns LOGIN-F-CLISYMTBL</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lib-spawn-returns-login-f-clisymtbl/m-p/3519514#M67680</link>
      <description>Mark,&lt;BR /&gt;&lt;BR /&gt;I think the idea about the sysgen parameter is a good one, but it appears this problem is related to the number of symbols defined and/or the size of the symbols or their values, not the logical names.&lt;BR /&gt;&lt;BR /&gt;$ SHOW SYM/ALL/GLO&lt;BR /&gt;&lt;BR /&gt;is a good way to see what symbols are defined.&lt;BR /&gt;&lt;BR /&gt;It's funny that the help/mess gives quite different advice about what's wrong, though.  Even if it is a virtual address space problem, I don't understand how increasing the PHYSICAL memory of the machine would provide more VIRTUAL memory.&lt;BR /&gt;&lt;BR /&gt;--Travis Craig&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Apr 2005 14:49:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lib-spawn-returns-login-f-clisymtbl/m-p/3519514#M67680</guid>
      <dc:creator>Travis Craig</dc:creator>
      <dc:date>2005-04-06T14:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: lib$spawn returns LOGIN-F-CLISYMTBL</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/lib-spawn-returns-login-f-clisymtbl/m-p/3519515#M67681</link>
      <description>DCL symbols and process logicals are created from a pool of memory in the process sized by CTLPAGES (not a dynamic parameter). The size of the symbol table within that is controlled by CLISYMTBL which is a dynamic paramter. Information about this area of memory can be seen with the command SHOW PROCESS/MEMORY&lt;BR /&gt;</description>
      <pubDate>Thu, 07 Apr 2005 08:13:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/lib-spawn-returns-login-f-clisymtbl/m-p/3519515#M67681</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-04-07T08:13:57Z</dc:date>
    </item>
  </channel>
</rss>

