<?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: using wait command on completed jobs in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/using-wait-command-on-completed-jobs/m-p/2508506#M892623</link>
    <description>That should read echo $?</description>
    <pubDate>Thu, 22 Mar 2001 13:25:40 GMT</pubDate>
    <dc:creator>unixdaddy</dc:creator>
    <dc:date>2001-03-22T13:25:40Z</dc:date>
    <item>
      <title>using wait command on completed jobs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-wait-command-on-completed-jobs/m-p/2508504#M892620</link>
      <description>If the wait command is issued on a process ID, where the process ID relates to a job that has completed, and hence the process ID is no longer in existance, is it safe to assume that the returncode from the wait command would be 127?</description>
      <pubDate>Thu, 22 Mar 2001 13:15:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-wait-command-on-completed-jobs/m-p/2508504#M892620</guid>
      <dc:creator>Chris Baugh</dc:creator>
      <dc:date>2001-03-22T13:15:32Z</dc:date>
    </item>
    <item>
      <title>Re: using wait command on completed jobs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-wait-command-on-completed-jobs/m-p/2508505#M892622</link>
      <description>I would say yes.  Try it by issuing a wait against a non-existent pid and then issue the $? straight afterwards it should return 127.</description>
      <pubDate>Thu, 22 Mar 2001 13:23:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-wait-command-on-completed-jobs/m-p/2508505#M892622</guid>
      <dc:creator>unixdaddy</dc:creator>
      <dc:date>2001-03-22T13:23:49Z</dc:date>
    </item>
    <item>
      <title>Re: using wait command on completed jobs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-wait-command-on-completed-jobs/m-p/2508506#M892623</link>
      <description>That should read echo $?</description>
      <pubDate>Thu, 22 Mar 2001 13:25:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-wait-command-on-completed-jobs/m-p/2508506#M892623</guid>
      <dc:creator>unixdaddy</dc:creator>
      <dc:date>2001-03-22T13:25:40Z</dc:date>
    </item>
    <item>
      <title>Re: using wait command on completed jobs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-wait-command-on-completed-jobs/m-p/2508507#M892624</link>
      <description>From some experiments on both HP-UX 11.00 and 10.20, it appears that two waits of the form:&lt;BR /&gt;wait &lt;PROCESS id=""&gt;&lt;BR /&gt;will successfully return the return code from &lt;PROCESS id=""&gt;&lt;BR /&gt;A third wait returns 127.&lt;BR /&gt;Note this is when &lt;PROCESS id=""&gt; has been issued by the shell with &lt;COMMAND&gt; &amp;amp;&lt;BR /&gt;Thus it is only safe to assume a response of 127 on the third (and subsequent calls to wait).&lt;BR /&gt;&lt;BR /&gt;However if you use the format &lt;BR /&gt;wait &lt;JOBID&gt;&lt;BR /&gt;where &lt;JOBID&gt; is %1 for instance (or %% for the last job issued) then only the first wait returns the valid return code for the job. All subsequent waits of this form return 1.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;John&lt;/JOBID&gt;&lt;/JOBID&gt;&lt;/COMMAND&gt;&lt;/PROCESS&gt;&lt;/PROCESS&gt;&lt;/PROCESS&gt;</description>
      <pubDate>Thu, 22 Mar 2001 14:03:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-wait-command-on-completed-jobs/m-p/2508507#M892624</guid>
      <dc:creator>John Palmer</dc:creator>
      <dc:date>2001-03-22T14:03:51Z</dc:date>
    </item>
  </channel>
</rss>

