<?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 ANSI c in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731948#M254658</link>
    <description>The customer installed the product B3901BA.&lt;BR /&gt;He,however, could not install the license. He was advised to create an ASCII file and insert this in the newconfig directory.  I suspect this is not the only place he need to insert the license file.  He get the following error message.&lt;BR /&gt;____________________________________________&lt;BR /&gt;&lt;BR /&gt;The errors are as follows when the code is compiled&lt;BR /&gt;&lt;BR /&gt;"/triceps/triprod/source $ mkrts1.hp SCR&lt;BR /&gt;&amp;gt; &amp;gt; Internal Error: Codeword file(s) missing or empty.&lt;BR /&gt;&amp;gt; &amp;gt; Internal Error: Codeword file(s) missing or empty.&lt;BR /&gt;&amp;gt; &amp;gt; Internal Error: Codeword file(s) missing or empty.&lt;BR /&gt;&amp;gt; &amp;gt; Internal Error: Codeword file(s) missing or empty.&lt;BR /&gt;&amp;gt; &amp;gt; cc: &amp;nbsp;487: warning : Possibly incorrect message catalog.&lt;BR /&gt;&amp;gt; &amp;gt; Internal Error: Codeword file(s) missing or empty.&lt;BR /&gt;&amp;gt; &amp;gt; cob32: error(s) in C compilation: rts1serl.c Rename rts1.SCR to rts1&lt;BR /&gt;&amp;gt; &amp;gt;&lt;BR /&gt;&amp;gt; &amp;gt;&lt;BR /&gt;&amp;gt; &amp;gt; mkrts1.hp has 4 C compiler commands, i.e.:&lt;BR /&gt;&amp;gt; &amp;gt;&lt;BR /&gt;&amp;gt; &amp;gt; cc -c +u1 -DHPUX cstuff2.c&lt;BR /&gt;&amp;gt; &amp;gt; cc -c +u1 -DHPUX dmn_c.c&lt;BR /&gt;&amp;gt; &amp;gt; cc -c +u1 -DHPUX rts1tcp.c&lt;BR /&gt;&amp;gt; &amp;gt; cc -c +u1 -DHPUX y.tab.c&lt;BR /&gt;&amp;gt; &amp;gt; cp rts1serl.$1 rts1serl.c&lt;BR /&gt;&amp;gt; &amp;gt; cob -xe "" cstuff2.o rts1serl.c rts1tcp.o y.tab.o dmn_c.o&lt;BR /&gt;&amp;gt; &amp;gt; /lib/libcur_colr.a -o"&lt;BR /&gt;&lt;BR /&gt;We found another reference to this error on the forums as follows&lt;BR /&gt;_________________________________________&lt;BR /&gt;</description>
    <pubDate>Wed, 15 Feb 2006 06:57:43 GMT</pubDate>
    <dc:creator>Mogamat</dc:creator>
    <dc:date>2006-02-15T06:57:43Z</dc:date>
    <item>
      <title>ANSI c</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731948#M254658</link>
      <description>The customer installed the product B3901BA.&lt;BR /&gt;He,however, could not install the license. He was advised to create an ASCII file and insert this in the newconfig directory.  I suspect this is not the only place he need to insert the license file.  He get the following error message.&lt;BR /&gt;____________________________________________&lt;BR /&gt;&lt;BR /&gt;The errors are as follows when the code is compiled&lt;BR /&gt;&lt;BR /&gt;"/triceps/triprod/source $ mkrts1.hp SCR&lt;BR /&gt;&amp;gt; &amp;gt; Internal Error: Codeword file(s) missing or empty.&lt;BR /&gt;&amp;gt; &amp;gt; Internal Error: Codeword file(s) missing or empty.&lt;BR /&gt;&amp;gt; &amp;gt; Internal Error: Codeword file(s) missing or empty.&lt;BR /&gt;&amp;gt; &amp;gt; Internal Error: Codeword file(s) missing or empty.&lt;BR /&gt;&amp;gt; &amp;gt; cc: &amp;nbsp;487: warning : Possibly incorrect message catalog.&lt;BR /&gt;&amp;gt; &amp;gt; Internal Error: Codeword file(s) missing or empty.&lt;BR /&gt;&amp;gt; &amp;gt; cob32: error(s) in C compilation: rts1serl.c Rename rts1.SCR to rts1&lt;BR /&gt;&amp;gt; &amp;gt;&lt;BR /&gt;&amp;gt; &amp;gt;&lt;BR /&gt;&amp;gt; &amp;gt; mkrts1.hp has 4 C compiler commands, i.e.:&lt;BR /&gt;&amp;gt; &amp;gt;&lt;BR /&gt;&amp;gt; &amp;gt; cc -c +u1 -DHPUX cstuff2.c&lt;BR /&gt;&amp;gt; &amp;gt; cc -c +u1 -DHPUX dmn_c.c&lt;BR /&gt;&amp;gt; &amp;gt; cc -c +u1 -DHPUX rts1tcp.c&lt;BR /&gt;&amp;gt; &amp;gt; cc -c +u1 -DHPUX y.tab.c&lt;BR /&gt;&amp;gt; &amp;gt; cp rts1serl.$1 rts1serl.c&lt;BR /&gt;&amp;gt; &amp;gt; cob -xe "" cstuff2.o rts1serl.c rts1tcp.o y.tab.o dmn_c.o&lt;BR /&gt;&amp;gt; &amp;gt; /lib/libcur_colr.a -o"&lt;BR /&gt;&lt;BR /&gt;We found another reference to this error on the forums as follows&lt;BR /&gt;_________________________________________&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Feb 2006 06:57:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731948#M254658</guid>
      <dc:creator>Mogamat</dc:creator>
      <dc:date>2006-02-15T06:57:43Z</dc:date>
    </item>
    <item>
      <title>Re: ANSI c</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731949#M254659</link>
      <description>Hi,&lt;BR /&gt;I would go back and try to complete the install. If you are the sys admin, why is the user doing installs? You can always use sam to step you through the process. This should also take care of switching the compiler from HP C to ANSI C.</description>
      <pubDate>Wed, 15 Feb 2006 07:13:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731949#M254659</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-02-15T07:13:13Z</dc:date>
    </item>
    <item>
      <title>Re: ANSI c</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731950#M254660</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;If the software is codeword protected, your customer should not be able to install it at all.&lt;BR /&gt;&lt;BR /&gt;Seems they found a way.&lt;BR /&gt;&lt;BR /&gt;The correct response is to swremove the software, correcly install the codeword with swinstall and then install the software from the Application CD's.&lt;BR /&gt;&lt;BR /&gt;Its meaningless to post code, because the compiler itself is the suspect. Perhaps however, I misunderstood. I stand ready for enlightenment.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 15 Feb 2006 07:14:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731950#M254660</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-02-15T07:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: ANSI c</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731951#M254661</link>
      <description>The installed anci c and he has a license key. He explains;&lt;BR /&gt;&lt;BR /&gt;"how do I install the code words from swinstall?&lt;BR /&gt;i go to actions, but i don't see anything such as "add new code"&lt;BR /&gt;&lt;BR /&gt;he then tried to manually insert the key. It would seem, however, that he does not know the path in which the key must be inserted. The only path is described as;&lt;BR /&gt;&lt;BR /&gt;â ¢ IPF Ansi C compiler: /opt/ansic/newconfig/ansic.cwd&lt;BR /&gt;&lt;BR /&gt;My question is: is the only path from which the key will be seen, or is there another path in which the key must appear to stop the error from appearing as described in my initial mail.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Wed, 15 Feb 2006 07:21:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731951#M254661</guid>
      <dc:creator>Mogamat</dc:creator>
      <dc:date>2006-02-15T07:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: ANSI c</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731952#M254662</link>
      <description>Hi,&lt;BR /&gt;after the software installation, he should select the software from the list in swinstall, then look at the action, there should be an option to add key. However, I would still question letting users try to do anything like this.</description>
      <pubDate>Wed, 15 Feb 2006 07:32:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731952#M254662</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-02-15T07:32:48Z</dc:date>
    </item>
    <item>
      <title>Re: ANSI c</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731953#M254663</link>
      <description>Hi,&lt;BR /&gt;after the software installation, he should select the software from the list in swinstall, then look at the action, there should be an option to add key. However, I would still question letting users try to do anything like this. &lt;BR /&gt;For a full description/guide:&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B2355-90789/ch02s01.html" target="_blank"&gt;http://docs.hp.com/en/B2355-90789/ch02s01.html&lt;/A&gt;</description>
      <pubDate>Wed, 15 Feb 2006 07:34:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731953#M254663</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-02-15T07:34:26Z</dc:date>
    </item>
    <item>
      <title>Re: ANSI c</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731954#M254664</link>
      <description>During the installation, when swinstall (I assume you are using the GUI at this point) is pointed at the software depot (normally the application CD/DVD's) a message window pops up saying that software in this depot is codeword protected and you should add the codeword to unlock the software.  There is a "Add New Codeword" selection available in the Actions menu for this purpose.&lt;BR /&gt;&lt;BR /&gt;Once the new codeword is added via swinstall, the ANSI C product will now be listed in the selection window, where it was not before the codeword was added.  Install the product in this manner and the problems will go away.</description>
      <pubDate>Thu, 16 Feb 2006 06:26:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ansi-c/m-p/3731954#M254664</guid>
      <dc:creator>Tom Henning</dc:creator>
      <dc:date>2006-02-16T06:26:14Z</dc:date>
    </item>
  </channel>
</rss>

