<?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: How do we complete a Flow if some jobs are not triggered? in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/How-do-we-complete-a-Flow-if-some-jobs-are-not-triggered/m-p/106535#M1208</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tis type of logic is coming from advanced schedulers (Ctrl-D OPC expect LSF the same).&lt;BR /&gt;The flow(job) is collection of programs to run on a regular scheme.&lt;/P&gt;&lt;P&gt;- Dependicies and events are influencing when each program is allowed to run&lt;/P&gt;&lt;P&gt;- actions as suspending a program (removing from requirements) are possible&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The logic to solve will be:&lt;/P&gt;&lt;P&gt;1- after a planned time and file2 does not exist have job2 suspendend (possible by running a job)&lt;/P&gt;&lt;P&gt;2- When Job2 is allowed to run more than once and is capable running on an empty file&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Have a time event within the flow planned to deliver an empty file&lt;/P&gt;&lt;P&gt;3- This will be an excpetional case. Have your operators being instructed to suspend the job2 as reaction on the alert message (late) of the scheduling environment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All depends how the environment is organized and the options in your tooling.&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 10 Aug 2013 07:38:46 GMT</pubDate>
    <dc:creator>jakarman</dc:creator>
    <dc:date>2013-08-10T07:38:46Z</dc:date>
    <item>
      <title>How do we complete a Flow if some jobs are not triggered?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/How-do-we-complete-a-Flow-if-some-jobs-are-not-triggered/m-p/106533#M1206</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The flow contains two jobs, which are triggered by their File event separately.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;File1 Exists --&amp;gt; Job1&lt;/P&gt;&lt;P&gt;File2 Exists --&amp;gt; Job2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is that when the flow is triggered and only File1 is there, the job2 won't run and it causes the flow never complete with the status of Running.&lt;/P&gt;&lt;P&gt;Any solution without programming for this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Shi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Aug 2013 16:13:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/How-do-we-complete-a-Flow-if-some-jobs-are-not-triggered/m-p/106533#M1206</guid>
      <dc:creator>ASASProgrammer</dc:creator>
      <dc:date>2013-08-09T16:13:20Z</dc:date>
    </item>
    <item>
      <title>Re: How do we complete a Flow if some jobs are not triggered?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/How-do-we-complete-a-Flow-if-some-jobs-are-not-triggered/m-p/106534#M1207</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure but I believe if you set the file trigger event for file 2 to "exist" then it should work.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Aug 2013 03:41:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/How-do-we-complete-a-Flow-if-some-jobs-are-not-triggered/m-p/106534#M1207</guid>
      <dc:creator>Patrick</dc:creator>
      <dc:date>2013-08-10T03:41:21Z</dc:date>
    </item>
    <item>
      <title>Re: How do we complete a Flow if some jobs are not triggered?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/How-do-we-complete-a-Flow-if-some-jobs-are-not-triggered/m-p/106535#M1208</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tis type of logic is coming from advanced schedulers (Ctrl-D OPC expect LSF the same).&lt;BR /&gt;The flow(job) is collection of programs to run on a regular scheme.&lt;/P&gt;&lt;P&gt;- Dependicies and events are influencing when each program is allowed to run&lt;/P&gt;&lt;P&gt;- actions as suspending a program (removing from requirements) are possible&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The logic to solve will be:&lt;/P&gt;&lt;P&gt;1- after a planned time and file2 does not exist have job2 suspendend (possible by running a job)&lt;/P&gt;&lt;P&gt;2- When Job2 is allowed to run more than once and is capable running on an empty file&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Have a time event within the flow planned to deliver an empty file&lt;/P&gt;&lt;P&gt;3- This will be an excpetional case. Have your operators being instructed to suspend the job2 as reaction on the alert message (late) of the scheduling environment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All depends how the environment is organized and the options in your tooling.&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Aug 2013 07:38:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/How-do-we-complete-a-Flow-if-some-jobs-are-not-triggered/m-p/106535#M1208</guid>
      <dc:creator>jakarman</dc:creator>
      <dc:date>2013-08-10T07:38:46Z</dc:date>
    </item>
  </channel>
</rss>

