<?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: Controlling ODS output in ODS and Base Reporting</title>
    <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Controlling-ODS-output/m-p/922913#M26533</link>
    <description>&lt;P&gt;In my autoexec, at the very beginning, I added these lines:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;/* set "current path" to WORK */
%put %sysfunc(DLGCDIR(%sysfunc(pathname(WORK)))); /* DLGCDIR changes current directory */
filename _ ".";
filename _ list;
filename _ clear;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;they set my session current path to my session's work directory (last 3 are just to verify) so, whenever I have:&lt;/P&gt;
&lt;P&gt;&lt;CODE class=" language-sas"&gt;ods html;
ods listing;&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;in my code the result is pushed to the work location.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could add something similar to SAS server's autoexec.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Bart&lt;/P&gt;</description>
    <pubDate>Thu, 04 Apr 2024 09:04:08 GMT</pubDate>
    <dc:creator>yabwon</dc:creator>
    <dc:date>2024-04-04T09:04:08Z</dc:date>
    <item>
      <title>Controlling ODS output</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Controlling-ODS-output/m-p/922859#M26532</link>
      <description>&lt;P&gt;Hello,&amp;nbsp; I am using WIN X64 (2022 std) 9.4 M8.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there a universal manner of controlling where the ODS default out would go to (from SAS doc it is supposed to be temp space) but we have seen output (non stored process) writing Excel or png type output to c:\SAS\Config\Lev1\SASApp folder for different users.&amp;nbsp; If permissions are restricted then their jobs fail.&amp;nbsp; Is there an easier solution to control ODS based output and if universally? (sas options, etc.)?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2024 21:31:47 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Controlling-ODS-output/m-p/922859#M26532</guid>
      <dc:creator>shoin</dc:creator>
      <dc:date>2024-04-03T21:31:47Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling ODS output</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/Controlling-ODS-output/m-p/922913#M26533</link>
      <description>&lt;P&gt;In my autoexec, at the very beginning, I added these lines:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;/* set "current path" to WORK */
%put %sysfunc(DLGCDIR(%sysfunc(pathname(WORK)))); /* DLGCDIR changes current directory */
filename _ ".";
filename _ list;
filename _ clear;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;they set my session current path to my session's work directory (last 3 are just to verify) so, whenever I have:&lt;/P&gt;
&lt;P&gt;&lt;CODE class=" language-sas"&gt;ods html;
ods listing;&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;in my code the result is pushed to the work location.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could add something similar to SAS server's autoexec.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Bart&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2024 09:04:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/Controlling-ODS-output/m-p/922913#M26533</guid>
      <dc:creator>yabwon</dc:creator>
      <dc:date>2024-04-04T09:04:08Z</dc:date>
    </item>
  </channel>
</rss>

