<?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: Fix to SAS/Studio automatic code in SAS Studio</title>
    <link>https://communities.sas.com/t5/SAS-Studio/Fix-to-SAS-Studio-automatic-code/m-p/291105#M951</link>
    <description>&lt;P&gt;Hey Tom!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I've found a couple of these myself, particularly in SAS University Edition. &amp;nbsp;I find that emailing SAS Support directly is the best way to get these added to the list. &amp;nbsp;Alternatively, you can add your idea to &lt;A href="https://communities.sas.com/t5/SASware-Ballot-Ideas/idb-p/sas_ideas" target="_self"&gt;SAS Ballot&lt;/A&gt;; being someone as active as you are here, I'm sure you're already aware of both these options, I just wanted to give you my thoughts based on experience.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good luck and chat soon&lt;/P&gt;
&lt;P&gt;Chris&lt;/P&gt;</description>
    <pubDate>Fri, 12 Aug 2016 00:06:40 GMT</pubDate>
    <dc:creator>DarthPathos</dc:creator>
    <dc:date>2016-08-12T00:06:40Z</dc:date>
    <item>
      <title>Fix to SAS/Studio automatic code</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Fix-to-SAS-Studio-automatic-code/m-p/290959#M946</link>
      <description>&lt;P&gt;How can we get SAS to update the code that SAS/Studio automatically pre-pends to the user code? &amp;nbsp;I am getting annoyed with this note that always appears at the top of my program logs.&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;INFO: Character variables have defaulted to a length of 200 at the places given by: (Line):(Column). Truncation can result.
       22:1     RC&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;It is caused by this bit of code.&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt; RC=TSLVL('GEOCODE','N');
 _ERROR_=0;
 IF (RC^=' ') THEN DO;
CALL SYMPUT("GRAPHINIT","GOPTIONS RESET=ALL GSFNAME=_GSFNAME;");
CALL SYMPUT("GRAPHTERM","GOPTIONS NOACCESSIBLE;");
END;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;They could fix it by adding a LENGTH statement. Or moving the function call into the IF statement since they aren't using the RC variable for anything anyway.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2016 12:55:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Fix-to-SAS-Studio-automatic-code/m-p/290959#M946</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2016-08-11T12:55:32Z</dc:date>
    </item>
    <item>
      <title>Re: Fix to SAS/Studio automatic code</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Fix-to-SAS-Studio-automatic-code/m-p/291105#M951</link>
      <description>&lt;P&gt;Hey Tom!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I've found a couple of these myself, particularly in SAS University Edition. &amp;nbsp;I find that emailing SAS Support directly is the best way to get these added to the list. &amp;nbsp;Alternatively, you can add your idea to &lt;A href="https://communities.sas.com/t5/SASware-Ballot-Ideas/idb-p/sas_ideas" target="_self"&gt;SAS Ballot&lt;/A&gt;; being someone as active as you are here, I'm sure you're already aware of both these options, I just wanted to give you my thoughts based on experience.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good luck and chat soon&lt;/P&gt;
&lt;P&gt;Chris&lt;/P&gt;</description>
      <pubDate>Fri, 12 Aug 2016 00:06:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Fix-to-SAS-Studio-automatic-code/m-p/291105#M951</guid>
      <dc:creator>DarthPathos</dc:creator>
      <dc:date>2016-08-12T00:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: Fix to SAS/Studio automatic code</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Fix-to-SAS-Studio-automatic-code/m-p/291314#M957</link>
      <description>&lt;P&gt;Here is the responce I got from SAS Support.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;Hello Tom,
 
Thanks for reporting the problem with the INFO notes in the SAS log. &lt;BR /&gt;I will enter a defect on this so that it can be addressed. &lt;BR /&gt;Thanks again!
 
SIncerely,
Chevell
&lt;/PRE&gt;</description>
      <pubDate>Tue, 16 Aug 2016 18:17:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Fix-to-SAS-Studio-automatic-code/m-p/291314#M957</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2016-08-16T18:17:50Z</dc:date>
    </item>
    <item>
      <title>Re: Fix to SAS/Studio automatic code</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Fix-to-SAS-Studio-automatic-code/m-p/291327#M958</link>
      <description>&lt;P&gt;Well that's better than nothing &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &amp;nbsp;hope it gets resolved soon. &amp;nbsp;In case you missed it, SAS has enabled us to download fixes just for SAS/Studio, without having to relicense all of SAS - so when the fix comes out, you'll get it right away. &amp;nbsp;I think this is great news.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;have a great weekend!&lt;/P&gt;
&lt;P&gt;Chris&lt;/P&gt;</description>
      <pubDate>Fri, 12 Aug 2016 16:46:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Fix-to-SAS-Studio-automatic-code/m-p/291327#M958</guid>
      <dc:creator>DarthPathos</dc:creator>
      <dc:date>2016-08-12T16:46:48Z</dc:date>
    </item>
  </channel>
</rss>

