<?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 Results differ when running a program in Enterprise Guide versus runing it as a background job in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Results-differ-when-running-a-program-in-Enterprise-Guide-versus/m-p/954830#M45652</link>
    <description>&lt;P&gt;Submitting a program to run in SAS® should return the same results whether it runs as a background job, runs interactively, or is submitted using&amp;nbsp;SAS® Enterprise Guide® (or SAS® Studio).&amp;nbsp; You might experience a situation where this does not appear to be the case and wonder what is happening.&amp;nbsp; Remember that in each scenario, you are running a SAS session that is configured by its option settings.&amp;nbsp; While the standard configuration options for the SAS session are likely the same, the individual SAS clients might contain specific option settings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These option settings can be affected by pre-code submitted by the SAS client or options settings that are controlled by preferences within the client.&amp;nbsp; Option settings that can affect results are FMTERR/NOFMTERR and VALIDVARNAME=.&amp;nbsp; If you are seeing differences in programs that are submitted using different methods, you might want to issue a PROC OPTIONS statement to compare the settings between the two environments.&amp;nbsp; You can even specify which options you want to see and add the VALUE parameter to display the value as well as how/where the value was set.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;proc options option=fmterr value;

run;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 31 Dec 2024 19:23:53 GMT</pubDate>
    <dc:creator>LynnP_sas</dc:creator>
    <dc:date>2024-12-31T19:23:53Z</dc:date>
    <item>
      <title>Results differ when running a program in Enterprise Guide versus runing it as a background job</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Results-differ-when-running-a-program-in-Enterprise-Guide-versus/m-p/954830#M45652</link>
      <description>&lt;P&gt;Submitting a program to run in SAS® should return the same results whether it runs as a background job, runs interactively, or is submitted using&amp;nbsp;SAS® Enterprise Guide® (or SAS® Studio).&amp;nbsp; You might experience a situation where this does not appear to be the case and wonder what is happening.&amp;nbsp; Remember that in each scenario, you are running a SAS session that is configured by its option settings.&amp;nbsp; While the standard configuration options for the SAS session are likely the same, the individual SAS clients might contain specific option settings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These option settings can be affected by pre-code submitted by the SAS client or options settings that are controlled by preferences within the client.&amp;nbsp; Option settings that can affect results are FMTERR/NOFMTERR and VALIDVARNAME=.&amp;nbsp; If you are seeing differences in programs that are submitted using different methods, you might want to issue a PROC OPTIONS statement to compare the settings between the two environments.&amp;nbsp; You can even specify which options you want to see and add the VALUE parameter to display the value as well as how/where the value was set.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;proc options option=fmterr value;

run;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Dec 2024 19:23:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Results-differ-when-running-a-program-in-Enterprise-Guide-versus/m-p/954830#M45652</guid>
      <dc:creator>LynnP_sas</dc:creator>
      <dc:date>2024-12-31T19:23:53Z</dc:date>
    </item>
    <item>
      <title>Re: Results differ when running a program in Enterprise Guide versus runing it as a background job</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Results-differ-when-running-a-program-in-Enterprise-Guide-versus/m-p/954965#M45653</link>
      <description>&lt;P&gt;An excellent reminder!&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jan 2025 21:24:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Results-differ-when-running-a-program-in-Enterprise-Guide-versus/m-p/954965#M45653</guid>
      <dc:creator>SASJedi</dc:creator>
      <dc:date>2025-01-02T21:24:38Z</dc:date>
    </item>
    <item>
      <title>Re: Results differ when running a program in Enterprise Guide versus runing it as a background job</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Results-differ-when-running-a-program-in-Enterprise-Guide-versus/m-p/954974#M45654</link>
      <description>&lt;P&gt;This is a good argument for applying global system options at the "SASApp" server context level and not separately on batch and workspace servers.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jan 2025 22:02:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Results-differ-when-running-a-program-in-Enterprise-Guide-versus/m-p/954974#M45654</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2025-01-02T22:02:19Z</dc:date>
    </item>
  </channel>
</rss>

