<?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: Multi-Threading in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44875#M9205</link>
    <description>I might consider it be called job/task-scheduling.  You can spawn independent SAS tasks in your SAS operating environment.  &lt;BR /&gt;
&lt;BR /&gt;
And without a scheduling subsystem, you can write logic to "sleep" and "awaken" to test for some crumbs/morsels that are left by a predecessor job/process.&lt;BR /&gt;
&lt;BR /&gt;
And, SAS jobs can be executed in sequence using various techniques, such as parent/child process/task execution or sequential threading (A completes, then submits B, C, D, and waits for B and C before submitting E - waits for D and E, then submits F).&lt;BR /&gt;
&lt;BR /&gt;
Sure it's possible.  Recommend reviewing the particular SAS companion guide for your OS, with focus on the OS system interfaces, such as CALL EXECUTE, CALL SYSTEM, and FILENAME &lt;FILEREF&gt; PIPES engine, to start.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.&lt;BR /&gt;
&lt;BR /&gt;
Recommended Google advanced search argument for this topic/post:&lt;BR /&gt;
&lt;BR /&gt;
batch program scheduling site:sas.com&lt;/FILEREF&gt;</description>
    <pubDate>Thu, 21 Jan 2010 23:07:17 GMT</pubDate>
    <dc:creator>sbb</dc:creator>
    <dc:date>2010-01-21T23:07:17Z</dc:date>
    <item>
      <title>Multi-Threading</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44874#M9204</link>
      <description>I have a program that calls a number of other macro programs in sequential order.&lt;BR /&gt;
&lt;BR /&gt;
However some of the programs are not dependent on the previous completing.&lt;BR /&gt;
&lt;BR /&gt;
Let's say macros 1,2,3,4,5 need to run sequentially and are dependent on the previous macro(s) executing to completion.&lt;BR /&gt;
&lt;BR /&gt;
There is also macros A,B,C,D,E that do not have to wait until the previous macros complete.&lt;BR /&gt;
&lt;BR /&gt;
Let's also assume the 1,2,3,4,5 need to complete before A,B,C,D,E are submitted.&lt;BR /&gt;
&lt;BR /&gt;
Does anyone know if or how I could multi-thread and submit A,B,C,D,E to all run at the same time and have them run independently.&lt;BR /&gt;
&lt;BR /&gt;
Thanx.&lt;BR /&gt;
_AW_</description>
      <pubDate>Thu, 21 Jan 2010 22:58:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44874#M9204</guid>
      <dc:creator>_AW_</dc:creator>
      <dc:date>2010-01-21T22:58:19Z</dc:date>
    </item>
    <item>
      <title>Re: Multi-Threading</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44875#M9205</link>
      <description>I might consider it be called job/task-scheduling.  You can spawn independent SAS tasks in your SAS operating environment.  &lt;BR /&gt;
&lt;BR /&gt;
And without a scheduling subsystem, you can write logic to "sleep" and "awaken" to test for some crumbs/morsels that are left by a predecessor job/process.&lt;BR /&gt;
&lt;BR /&gt;
And, SAS jobs can be executed in sequence using various techniques, such as parent/child process/task execution or sequential threading (A completes, then submits B, C, D, and waits for B and C before submitting E - waits for D and E, then submits F).&lt;BR /&gt;
&lt;BR /&gt;
Sure it's possible.  Recommend reviewing the particular SAS companion guide for your OS, with focus on the OS system interfaces, such as CALL EXECUTE, CALL SYSTEM, and FILENAME &lt;FILEREF&gt; PIPES engine, to start.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.&lt;BR /&gt;
&lt;BR /&gt;
Recommended Google advanced search argument for this topic/post:&lt;BR /&gt;
&lt;BR /&gt;
batch program scheduling site:sas.com&lt;/FILEREF&gt;</description>
      <pubDate>Thu, 21 Jan 2010 23:07:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44875#M9205</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2010-01-21T23:07:17Z</dc:date>
    </item>
    <item>
      <title>Re: Multi-Threading</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44876#M9206</link>
      <description>You might also consider the technique called MP CONNECT, see on-line doc for details.&lt;BR /&gt;
&lt;BR /&gt;
/Linus</description>
      <pubDate>Fri, 22 Jan 2010 07:44:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44876#M9206</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2010-01-22T07:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: Multi-Threading</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44877#M9207</link>
      <description>Yep,&lt;BR /&gt;
&lt;BR /&gt;
Either leave it to the system/scheduler&lt;BR /&gt;
or&lt;BR /&gt;
if your site has SAS/CONNECT licensed then MP CONNECT gives you the ability to submit asynchronous remote/local processes.&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://support.sas.com/documentation/cdl/en/connref/61908/HTML/default/a002626619.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/connref/61908/HTML/default/a002626619.htm&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Cheers from Portugal.&lt;BR /&gt;
&lt;BR /&gt;
Daniel Santos @ &lt;A href="http://www.cgd.pt" target="_blank"&gt;www.cgd.pt&lt;/A&gt;</description>
      <pubDate>Fri, 22 Jan 2010 08:59:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44877#M9207</guid>
      <dc:creator>DanielSantos</dc:creator>
      <dc:date>2010-01-22T08:59:32Z</dc:date>
    </item>
    <item>
      <title>Re: Multi-Threading</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44878#M9208</link>
      <description>Thanks to all.&lt;BR /&gt;
&lt;BR /&gt;
_AW_</description>
      <pubDate>Fri, 22 Jan 2010 15:34:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44878#M9208</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2010-01-22T15:34:50Z</dc:date>
    </item>
    <item>
      <title>Re: Multi-Threading</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44879#M9209</link>
      <description>I believe all these features you desire are provided for with the SAS statements SYSTASK and WAITFOR.</description>
      <pubDate>Fri, 22 Jan 2010 16:51:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Multi-Threading/m-p/44879#M9209</guid>
      <dc:creator>data_null__</dc:creator>
      <dc:date>2010-01-22T16:51:19Z</dc:date>
    </item>
  </channel>
</rss>

