<?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: Run the same programs twice using ordered lists? in New SAS User</title>
    <link>https://communities.sas.com/t5/New-SAS-User/Run-the-same-programs-twice-using-ordered-lists/m-p/612346#M18300</link>
    <description>&lt;P&gt;Start with code that does it once, for one time period.&lt;/P&gt;
&lt;P&gt;Identify all elements that need to be changed for a different time period (dates, dataset names, ...).&lt;/P&gt;
&lt;P&gt;Replace those elements with macro variables, and set those macro variables in a preceding first code in your ordered list (process flow). If possible, try to reduce manual settings and instead calculate all macro variables out of one source, like&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;%let year=2019;

data _null_;
call symputx('begin',mdy(1,1,&amp;amp;year.);
call symputx('end',mdy(12,31,&amp;amp;year.);
call symputx('indataset',"inlib.indata&amp;amp;year.");
run;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;so you end up with one process flow where a single change controls the whole logic.&lt;/P&gt;</description>
    <pubDate>Tue, 17 Dec 2019 09:45:23 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2019-12-17T09:45:23Z</dc:date>
    <item>
      <title>Run the same programs twice using ordered lists?</title>
      <link>https://communities.sas.com/t5/New-SAS-User/Run-the-same-programs-twice-using-ordered-lists/m-p/612338#M18297</link>
      <description>&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;I still a novice so forgive me if this is stupid. I am attempting to run the set of programs twice in a row for two different time periods. I set variables that go into 2019 tables and put together the tables I want then I reassign the variables to go into 2018 tables and pull the data. I can't bring 2019 and 2018 in together because the tables they pull from are different (there isnt one table with both 2018 and 2019 data) and also sometimes I may only want to pull for one time period.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Why does sas not let me run two ordered lists in a row that have some of the same programs in them?&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2019 09:13:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/Run-the-same-programs-twice-using-ordered-lists/m-p/612338#M18297</guid>
      <dc:creator>MateoAnthony</dc:creator>
      <dc:date>2019-12-17T09:13:26Z</dc:date>
    </item>
    <item>
      <title>Re: Run the same programs twice using ordered lists?</title>
      <link>https://communities.sas.com/t5/New-SAS-User/Run-the-same-programs-twice-using-ordered-lists/m-p/612346#M18300</link>
      <description>&lt;P&gt;Start with code that does it once, for one time period.&lt;/P&gt;
&lt;P&gt;Identify all elements that need to be changed for a different time period (dates, dataset names, ...).&lt;/P&gt;
&lt;P&gt;Replace those elements with macro variables, and set those macro variables in a preceding first code in your ordered list (process flow). If possible, try to reduce manual settings and instead calculate all macro variables out of one source, like&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;%let year=2019;

data _null_;
call symputx('begin',mdy(1,1,&amp;amp;year.);
call symputx('end',mdy(12,31,&amp;amp;year.);
call symputx('indataset',"inlib.indata&amp;amp;year.");
run;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;so you end up with one process flow where a single change controls the whole logic.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2019 09:45:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/Run-the-same-programs-twice-using-ordered-lists/m-p/612346#M18300</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2019-12-17T09:45:23Z</dc:date>
    </item>
    <item>
      <title>Re: Run the same programs twice using ordered lists?</title>
      <link>https://communities.sas.com/t5/New-SAS-User/Run-the-same-programs-twice-using-ordered-lists/m-p/612489#M18304</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/303883"&gt;@MateoAnthony&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;I still a novice so forgive me if this is stupid. I am attempting to run the set of programs twice in a row for two different time periods. I set variables that go into 2019 tables and put together the tables I want then I reassign the variables to go into 2018 tables and pull the data. I can't bring 2019 and 2018 in together because the tables they pull from are different (there isnt one table with both 2018 and 2019 data) and also sometimes I may only want to pull for one time period.&lt;/P&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Why does sas not let me run two ordered lists in a row that have some of the same programs in them?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;You probably should show the code you attempted and preferably include the LOG that shows any messages from the attempt.&lt;/P&gt;
&lt;P&gt;SAS is likely not the issue but the logic of the code you attempted.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You may also need to describe where your "list" resides. The typical data structure called a "list", as far as my experience with SAS goes, involves the SAS/AF and SAS/FSP modules.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2019 18:09:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/Run-the-same-programs-twice-using-ordered-lists/m-p/612489#M18304</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2019-12-17T18:09:50Z</dc:date>
    </item>
  </channel>
</rss>

