<?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: ksh return code in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885602#M280679</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;According to this scripting guide:&lt;BR /&gt;&lt;A href="http://www.aero.jussieu.fr/services/INFO/documentation/mendel/HTML/exitcodes.html" target="_blank"&gt;http://www.aero.jussieu.fr/services/INFO/documentation/mendel/HTML/exitcodes.html&lt;/A&gt;&lt;BR /&gt;the recommended user-defined range for exit codes is 64-113.&lt;BR /&gt;&lt;BR /&gt;PCS</description>
    <pubDate>Tue, 24 Oct 2006 09:40:45 GMT</pubDate>
    <dc:creator>spex</dc:creator>
    <dc:date>2006-10-24T09:40:45Z</dc:date>
    <item>
      <title>ksh return code</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885598#M280675</link>
      <description>I have a script that is giving me a return code of 64. Where can I look up that return code for more information?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 24 Oct 2006 08:48:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885598#M280675</guid>
      <dc:creator>F Saluba</dc:creator>
      <dc:date>2006-10-24T08:48:36Z</dc:date>
    </item>
    <item>
      <title>Re: ksh return code</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885599#M280676</link>
      <description>Hi,&lt;BR /&gt;afraid you have to debug your script as the return code can be set, by for example "exit 64".&lt;BR /&gt;Include "set -x" near the start of your script to trace.&lt;BR /&gt;&lt;BR /&gt;You may also want to have a look at:&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/helptips.do?#22" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/helptips.do?#22&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Oct 2006 09:00:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885599#M280676</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-10-24T09:00:30Z</dc:date>
    </item>
    <item>
      <title>Re: ksh return code</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885600#M280677</link>
      <description>Some info: &lt;BR /&gt;&lt;BR /&gt;# grep 64 sysexits.h&lt;BR /&gt;# define EX__BASE       64      /* base value for error messages */&lt;BR /&gt;# define EX_USAGE       64      /* command line usage error */&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Try to run sript with -x option to see more details.&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;ivan</description>
      <pubDate>Tue, 24 Oct 2006 09:11:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885600#M280677</guid>
      <dc:creator>Ivan Krastev</dc:creator>
      <dc:date>2006-10-24T09:11:50Z</dc:date>
    </item>
    <item>
      <title>Re: ksh return code</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885601#M280678</link>
      <description>If you did not set the return status (ex. return 64) then the status is coming from the last command executed within the script.  If that is the case, you could try and do a "man" on that command to see if the error code is documented there.</description>
      <pubDate>Tue, 24 Oct 2006 09:13:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885601#M280678</guid>
      <dc:creator>Keith Johnson</dc:creator>
      <dc:date>2006-10-24T09:13:55Z</dc:date>
    </item>
    <item>
      <title>Re: ksh return code</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885602#M280679</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;According to this scripting guide:&lt;BR /&gt;&lt;A href="http://www.aero.jussieu.fr/services/INFO/documentation/mendel/HTML/exitcodes.html" target="_blank"&gt;http://www.aero.jussieu.fr/services/INFO/documentation/mendel/HTML/exitcodes.html&lt;/A&gt;&lt;BR /&gt;the recommended user-defined range for exit codes is 64-113.&lt;BR /&gt;&lt;BR /&gt;PCS</description>
      <pubDate>Tue, 24 Oct 2006 09:40:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885602#M280679</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-10-24T09:40:45Z</dc:date>
    </item>
    <item>
      <title>Re: ksh return code</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885603#M280680</link>
      <description>Shells only have error codes when a problem has occurred within a shell task. That is not the same as running a command and exiting due to an error. Virtually all well written scripts will have error codes defined which you can see. Otherwise, the error was caused by a failed command or a logic problem in the script such as arithmetic on some random or null text. In the problem script, put the line:&lt;BR /&gt; &lt;BR /&gt;set -x&lt;BR /&gt; &lt;BR /&gt;at the top of the script. When the script fails, you'll see what it was trying to do. If the script tried to run a built-in function, you'll need to add the set -x to the function to get the exact failure.</description>
      <pubDate>Tue, 24 Oct 2006 09:46:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885603#M280680</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2006-10-24T09:46:43Z</dc:date>
    </item>
    <item>
      <title>Re: ksh return code</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885604#M280681</link>
      <description>Hi,&lt;BR /&gt;as you have not updated this thread I assume the problem is resolved ?&lt;BR /&gt;&lt;BR /&gt;Please see &lt;A href="http://forums1.itrc.hp.com/service/forums/helptips.do?#22" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/helptips.do?#22&lt;/A&gt; to reward the work the contributors have put into resolving your problem and then close this thread summarising the solution. This will help future problem resolution.&lt;BR /&gt;&lt;BR /&gt;From your profile I see you have not allocated any points to any answers to your post(0 for 10)!</description>
      <pubDate>Thu, 26 Oct 2006 05:35:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ksh-return-code/m-p/3885604#M280681</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-10-26T05:35:07Z</dc:date>
    </item>
  </channel>
</rss>

