<?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: SAS LSF job re-run if failed in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-LSF-job-re-run-if-failed/m-p/930130#M28563</link>
    <description>&lt;P&gt;Does the job exit with an error or a warning?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it's an error i'll agree with the other suggestions to fix the error by its source.&lt;/P&gt;&lt;P&gt;If it' a warning, and you want to allow your batch-flows to complete with a warning, then you can edit the sasbatch.bat file.&lt;/P&gt;&lt;P&gt;\SAS\Config\Lev1\SASApp\BatchServer\sasbatch.bat&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just remove the REM in the last four lines as stated in the comments in the file.&lt;/P&gt;&lt;P&gt;This is on a windows platform but I assume that you can do something similar if it's another platform.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 29 May 2024 13:08:26 GMT</pubDate>
    <dc:creator>CHandberg</dc:creator>
    <dc:date>2024-05-29T13:08:26Z</dc:date>
    <item>
      <title>SAS LSF job re-run if failed</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-LSF-job-re-run-if-failed/m-p/929980#M28554</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a deployed SAS job runs in flow which always fails during the first run and after we re -run manually it will get succeeded. The issue is due to sql server stored procedure which we call in it in the SAS job.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So we thought of adding exception handling in the schedule manager for that job. We have defined that 'if the job fails with exit code greater than zero, we asked it to re-run automatically', But its not working. Is there any other way to remove the manual process of re run ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 May 2024 15:35:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-LSF-job-re-run-if-failed/m-p/929980#M28554</guid>
      <dc:creator>freshstarter</dc:creator>
      <dc:date>2024-05-28T15:35:34Z</dc:date>
    </item>
    <item>
      <title>Re: SAS LSF job re-run if failed</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-LSF-job-re-run-if-failed/m-p/929989#M28556</link>
      <description>Your solution of running the job again if it fails sounds valid. Do you have any details on how it isn't working?&lt;BR /&gt;Could you modify your code to retry a failed call to the stored procedure?</description>
      <pubDate>Tue, 28 May 2024 18:15:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-LSF-job-re-run-if-failed/m-p/929989#M28556</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2024-05-28T18:15:37Z</dc:date>
    </item>
    <item>
      <title>Re: SAS LSF job re-run if failed</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-LSF-job-re-run-if-failed/m-p/929991#M28557</link>
      <description>&lt;P&gt;I suggest you talk with your SQL Server database administrator to see if you can get the stored procedure fixed. It's always better to cure the disease rather than treat the symptoms.&lt;/P&gt;</description>
      <pubDate>Tue, 28 May 2024 20:00:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-LSF-job-re-run-if-failed/m-p/929991#M28557</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2024-05-28T20:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: SAS LSF job re-run if failed</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-LSF-job-re-run-if-failed/m-p/930002#M28558</link>
      <description>&lt;P&gt;What sort of problem does SAS report with the stored procedure?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the procedure is taking too long to respond to data request from SAS perhaps you just need to add a bit of code to have SAS wait for the procedure.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Or maybe your connection options between SAS and SQL Server need to be tweeked a bit.&lt;/P&gt;</description>
      <pubDate>Tue, 28 May 2024 22:24:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-LSF-job-re-run-if-failed/m-p/930002#M28558</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2024-05-28T22:24:30Z</dc:date>
    </item>
    <item>
      <title>Re: SAS LSF job re-run if failed</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-LSF-job-re-run-if-failed/m-p/930130#M28563</link>
      <description>&lt;P&gt;Does the job exit with an error or a warning?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it's an error i'll agree with the other suggestions to fix the error by its source.&lt;/P&gt;&lt;P&gt;If it' a warning, and you want to allow your batch-flows to complete with a warning, then you can edit the sasbatch.bat file.&lt;/P&gt;&lt;P&gt;\SAS\Config\Lev1\SASApp\BatchServer\sasbatch.bat&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just remove the REM in the last four lines as stated in the comments in the file.&lt;/P&gt;&lt;P&gt;This is on a windows platform but I assume that you can do something similar if it's another platform.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 13:08:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-LSF-job-re-run-if-failed/m-p/930130#M28563</guid>
      <dc:creator>CHandberg</dc:creator>
      <dc:date>2024-05-29T13:08:26Z</dc:date>
    </item>
  </channel>
</rss>

