<?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 Juletip #19 – Let your SAS code echo in SAS Community Nordic</title>
    <link>https://communities.sas.com/t5/SAS-Community-Nordic/Juletip-19-Let-your-SAS-code-echo/m-p/954127#M497</link>
    <description>&lt;P&gt;Yule Tip #19 is for all the merry Enterprise Guide users. If you are an EG user and sometimes run flows with multiple data steps or SQLs, you might find this tip useful. Run the code below and you’ll see the SYSECHO messages in the data step code, displayed in EG’s Submission Status panel. Consider a program with several and longer data steps - putting in a few SYSECHOs would give you a much better idea where you are in your flow, comparing to just seeing “Running DATA step…”. Try it out.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data _null_; 
   sysecho "Starting a really big batch job..."; 
   s = sleep(3);  
run;

data AllCars;
   sysecho "Reading data about all sorts of cars";
   set SASHELP.CARS;
   if _N_ = 1 then s = sleep(2);
run;

data SwedishCars;
   sysecho "Reading data about Swedish cars";
   set SASHELP.CARS;
   where Make in ('Saab','Volvo');
   if _N_ = 1 then s = sleep(2);
run;
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;STRONG&gt;Documentation on SYSECHO:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lestmtsglobal/p1h1e01yyff0fon1iyh0mk51maf2.htm" target="_blank"&gt;https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lestmtsglobal/p1h1e01yyff0fon1iyh0mk51maf2.htm&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 19 Dec 2024 06:34:50 GMT</pubDate>
    <dc:creator>DanielRingqvist</dc:creator>
    <dc:date>2024-12-19T06:34:50Z</dc:date>
    <item>
      <title>Juletip #19 – Let your SAS code echo</title>
      <link>https://communities.sas.com/t5/SAS-Community-Nordic/Juletip-19-Let-your-SAS-code-echo/m-p/954127#M497</link>
      <description>&lt;P&gt;Yule Tip #19 is for all the merry Enterprise Guide users. If you are an EG user and sometimes run flows with multiple data steps or SQLs, you might find this tip useful. Run the code below and you’ll see the SYSECHO messages in the data step code, displayed in EG’s Submission Status panel. Consider a program with several and longer data steps - putting in a few SYSECHOs would give you a much better idea where you are in your flow, comparing to just seeing “Running DATA step…”. Try it out.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data _null_; 
   sysecho "Starting a really big batch job..."; 
   s = sleep(3);  
run;

data AllCars;
   sysecho "Reading data about all sorts of cars";
   set SASHELP.CARS;
   if _N_ = 1 then s = sleep(2);
run;

data SwedishCars;
   sysecho "Reading data about Swedish cars";
   set SASHELP.CARS;
   where Make in ('Saab','Volvo');
   if _N_ = 1 then s = sleep(2);
run;
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;STRONG&gt;Documentation on SYSECHO:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lestmtsglobal/p1h1e01yyff0fon1iyh0mk51maf2.htm" target="_blank"&gt;https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lestmtsglobal/p1h1e01yyff0fon1iyh0mk51maf2.htm&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2024 06:34:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Community-Nordic/Juletip-19-Let-your-SAS-code-echo/m-p/954127#M497</guid>
      <dc:creator>DanielRingqvist</dc:creator>
      <dc:date>2024-12-19T06:34:50Z</dc:date>
    </item>
  </channel>
</rss>

