<?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: Invoking a executable with command line arguments in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/invoking-a-executable-with-command-line-arguments/m-p/3795538#M781932</link>
    <description>I agree with Hein that the source code of the C program needs to be looked at in order to find out what's going on. Please post it if you have it.&lt;BR /&gt;&lt;BR /&gt;thanks</description>
    <pubDate>Sat, 27 May 2006 12:39:46 GMT</pubDate>
    <dc:creator>Sandman!</dc:creator>
    <dc:date>2006-05-27T12:39:46Z</dc:date>
    <item>
      <title>Invoking a executable with command line arguments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/invoking-a-executable-with-command-line-arguments/m-p/3795536#M781930</link>
      <description>On HP Unix 11i while calling COBOL executables with command line arguments is prefixing a tab before the first command line argument. The COBOL executables are called by system function call from C.&lt;BR /&gt;Suggest us how to ommit the prefixing of tab for the first command line argument.</description>
      <pubDate>Sat, 27 May 2006 02:20:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/invoking-a-executable-with-command-line-arguments/m-p/3795536#M781930</guid>
      <dc:creator>Gerard Powell</dc:creator>
      <dc:date>2006-05-27T02:20:42Z</dc:date>
    </item>
    <item>
      <title>Re: Invoking a executable with command line arguments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/invoking-a-executable-with-command-line-arguments/m-p/3795537#M781931</link>
      <description>Sounds like a programming error in the C code, where it builds the command string. If that is the case, then we would have to see snippets of the code to try and help further. Notably the variable declarations for the copmmand line passed to system, and the operations used to build it: how is it inialized? memset? static text? how is it filled? sprintf? strncpy?...&lt;BR /&gt;&lt;BR /&gt;I suppose it could also be a cobol special feature.&lt;BR /&gt;If you execute the cobol directly from the shell, does it not show the tab?&lt;BR /&gt;&lt;BR /&gt;Finally how do you even know a 'tab' is there? Could it be interpreting the data wrongly? Could the tab be a character count for the next piece of string?&lt;BR /&gt;&lt;BR /&gt;Good luck,&lt;BR /&gt;Hein.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 27 May 2006 09:41:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/invoking-a-executable-with-command-line-arguments/m-p/3795537#M781931</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2006-05-27T09:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: Invoking a executable with command line arguments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/invoking-a-executable-with-command-line-arguments/m-p/3795538#M781932</link>
      <description>I agree with Hein that the source code of the C program needs to be looked at in order to find out what's going on. Please post it if you have it.&lt;BR /&gt;&lt;BR /&gt;thanks</description>
      <pubDate>Sat, 27 May 2006 12:39:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/invoking-a-executable-with-command-line-arguments/m-p/3795538#M781932</guid>
      <dc:creator>Sandman!</dc:creator>
      <dc:date>2006-05-27T12:39:46Z</dc:date>
    </item>
  </channel>
</rss>

