<?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: 31 character module name limit? in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506481#M31928</link>
    <description>We'll try Itanium.  If it has lifted the 31 character limit and also made object formats more compatible, that should be a huge step in the direction of portability.&lt;BR /&gt;</description>
    <pubDate>Fri, 18 Mar 2005 11:58:49 GMT</pubDate>
    <dc:creator>Phil Naecker</dc:creator>
    <dc:date>2005-03-18T11:58:49Z</dc:date>
    <item>
      <title>31 character module name limit?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506474#M31921</link>
      <description>We are porting a Linux C++ application to VMS and have encountered the 31 character limit in module names.  We will try /NAMES=SHORTENED.   But does anyone know of any plans by OpenVMS engineering to address this issue more properly?  Who can we beat on to ask for such support?</description>
      <pubDate>Wed, 16 Mar 2005 20:52:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506474#M31921</guid>
      <dc:creator>Phil Naecker</dc:creator>
      <dc:date>2005-03-16T20:52:20Z</dc:date>
    </item>
    <item>
      <title>Re: 31 character module name limit?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506475#M31922</link>
      <description>Phil,&lt;BR /&gt;&lt;BR /&gt;   I don't think there are any plans to increase the module name limit. I'm curious why the *MODULE* name limit matters as it's largely an OpenVMS construct of interest only to the librarian, linker and DEBUG. &lt;BR /&gt;&lt;BR /&gt;  I thought C++ solved the problem of unlimited symbol length by "mangling" names? If not, /NAMES=SHORTENED should generate unique names in a transparent and consistent manner.&lt;BR /&gt;&lt;BR /&gt;  That said, if you have a business need for increased symbol lengths, please log a case against your service contract and ask to have the issue elevated into engineering.</description>
      <pubDate>Wed, 16 Mar 2005 22:16:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506475#M31922</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2005-03-16T22:16:19Z</dc:date>
    </item>
    <item>
      <title>Re: 31 character module name limit?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506476#M31923</link>
      <description>&lt;LIBRARIAN&gt;, and, as Guy Peleg has explained, image activator. So pretty basic..., though the change in itself wouldn't be a big issue in itself...(That's my interpretation)&lt;BR /&gt;&lt;BR /&gt;This is a wish that is shared by a lot of, if not all developers - for years already. I can live with the limitation (gives me enough room for distictive, sensable names) but that may not be valid for all systems - would be great if this limitation was FINALLY lifted....&lt;/LIBRARIAN&gt;</description>
      <pubDate>Thu, 17 Mar 2005 05:27:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506476#M31923</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2005-03-17T05:27:48Z</dc:date>
    </item>
    <item>
      <title>Re: 31 character module name limit?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506477#M31924</link>
      <description>Willem, this is not an issue of preference for constructing names.  We are porting software from another platform - the choice of naming style has already been made, and the software is in use, with external APIs used by dozens of other applications.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Mar 2005 09:40:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506477#M31924</guid>
      <dc:creator>Phil Naecker</dc:creator>
      <dc:date>2005-03-17T09:40:02Z</dc:date>
    </item>
    <item>
      <title>Re: 31 character module name limit?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506478#M31925</link>
      <description>OpenVMS on Itanium allows modules&lt;BR /&gt;names up to 1024 characters.&lt;BR /&gt;&lt;BR /&gt;Guy</description>
      <pubDate>Fri, 18 Mar 2005 02:17:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506478#M31925</guid>
      <dc:creator>Guy Peleg</dc:creator>
      <dc:date>2005-03-18T02:17:08Z</dc:date>
    </item>
    <item>
      <title>Re: 31 character module name limit?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506479#M31926</link>
      <description>&lt;BR /&gt;Guy,&lt;BR /&gt;&lt;BR /&gt;As Phil said&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;We are porting software from another platform...&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;There is more to it than just lifting the length limit on module names, even if you say that&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;OpenVMS on Itanium allows modules names up to 1024 characters.&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;AFAIK, the C compiler by default will truncate definitions &amp;amp; references of external symbols to 31 characters. Furthermore, if you specify preservation of case (/NAMES=AS_IS) then e.g. MMS gets confused, especially when you put "lowercase" modules in libraries.&lt;BR /&gt;&lt;BR /&gt;An excerpt of the log file of the first build of Jam 2.4 should give some clarification.&lt;BR /&gt;(see also &lt;A href="http://www.quadratrix.be/products/open_source_material.html" target="_blank"&gt;http://www.quadratrix.be/products/open_source_material.html&lt;/A&gt; )&lt;BR /&gt;&lt;BR /&gt;&amp;gt; set default OPENSOURCE$ROOT:[JAM.JAM-2_4]&lt;BR /&gt;&amp;gt; cc /prefix=all/name=(as_is)/warn/reent=multi /define=("QPORT=1,VMS=1") /include=(OPENSOURCE$ROOT:[JAM.JAM-2_4],OPENSOURCE$ROOT:[JAM.JAM-2_4.CONTRIB.Q]) /object=OPENSOURCE$ROOT:[JAM.JAM-2_4.CONTRIB.Q.IA64.OBJ]hash.obj OPENSOURCE$ROOT:[JAM.JAM-2_4]hash.c&lt;BR /&gt;&amp;gt; if f$search("OPENSOURCE$ROOT:[JAM.JAM-2_4.CONTRIB.Q.IA64.LIBlibjam.olb") .eqs. "" then library/create/object OPENSOURCE$ROOT:[JAM.JAM-2_4.CONTRIB.Q.IA64.LIB]libjam.olb&lt;BR /&gt;&amp;gt; library/replace/object OPENSOURCE$ROOT:[JAM.JAM-2_4.CONTRIB.Q.IA64.LIB]libjam.olb OPENSOURCE$ROOT:[JAM.JAM-2_4.CONTRIB.Q.IA64.OBJ]hash.obj&lt;BR /&gt;&lt;BR /&gt;%MMS-W-GWKACTNOUPD, Actions didn't update OPENSOURCE$ROOT:[JAM.JAM-2_4.CONTRIB.Q.IA64.LIB]LIBJAM.OLB(HASH=HASH.OBJ)&lt;BR /&gt;&lt;BR /&gt;So, what I'm trying to say is that, when porting to VMS, naming conventions from other platforms (e.g. U**x) can play tricks on you.&lt;BR /&gt;&lt;BR /&gt;Just my 2 cents,&lt;BR /&gt;Kris (aka Qkcl)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Fri, 18 Mar 2005 03:25:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506479#M31926</guid>
      <dc:creator>Kris Clippeleyr</dc:creator>
      <dc:date>2005-03-18T03:25:04Z</dc:date>
    </item>
    <item>
      <title>Re: 31 character module name limit?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506480#M31927</link>
      <description>Kris,&lt;BR /&gt;&lt;BR /&gt;OpenVMS (on Itanium) uses industry standard format for images and debug information&lt;BR /&gt;(aka ELF/DWARF)&lt;BR /&gt;&lt;BR /&gt;All the compilers and tools (should be) aware of it.&lt;BR /&gt;&lt;BR /&gt;Linux on Itanium uses the same standards...&lt;BR /&gt;so if it worked on Linux it *should* work&lt;BR /&gt;on VMS on Itanium....&lt;BR /&gt;&lt;BR /&gt;Guy&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Mar 2005 03:30:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506480#M31927</guid>
      <dc:creator>Guy Peleg</dc:creator>
      <dc:date>2005-03-18T03:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: 31 character module name limit?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506481#M31928</link>
      <description>We'll try Itanium.  If it has lifted the 31 character limit and also made object formats more compatible, that should be a huge step in the direction of portability.&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Mar 2005 11:58:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506481#M31928</guid>
      <dc:creator>Phil Naecker</dc:creator>
      <dc:date>2005-03-18T11:58:49Z</dc:date>
    </item>
    <item>
      <title>Re: 31 character module name limit?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506482#M31929</link>
      <description>Note that the librarian shipping with V8.2&lt;BR /&gt;has a bug and will not allow module&lt;BR /&gt;names with more than 31 characters. If you&lt;BR /&gt;are using the librarian, file a call with &lt;BR /&gt;your local support center to get the&lt;BR /&gt;fixed librarian.&lt;BR /&gt;&lt;BR /&gt;Guy</description>
      <pubDate>Fri, 18 Mar 2005 12:05:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/31-character-module-name-limit/m-p/3506482#M31929</guid>
      <dc:creator>Guy Peleg</dc:creator>
      <dc:date>2005-03-18T12:05:11Z</dc:date>
    </item>
  </channel>
</rss>

