<?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: sid_files vs. SASHOME/licenses in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/sid-files-vs-SASHOME-licenses/m-p/195125#M2596</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok even that part of applying a license is becoming a tremendous confusing complexity of all issue.&amp;nbsp; That is the truth.&lt;/P&gt;&lt;P&gt;1/ Running a SAS-base (foundation) there is a setinit being applied that is ( one of the many) license protections.&lt;/P&gt;&lt;P&gt;To view and update that information you can use "proc setitnit".&amp;nbsp; When you get the SID you can recognize that as some part of it.&lt;/P&gt;&lt;P&gt;2/ The SID is coming in for the installation with usage of that special "software depot" to be able to use that you to update that one.&lt;/P&gt;&lt;P&gt;3/ With some/several Solutions there is the license being registered in the SAS-metadata. The midtier solutions of SAS can check that one.&lt;/P&gt;&lt;P&gt;4/ Additional tools like LSF and SPD (server) have their own license with a connection by the sid in the same way.&lt;/P&gt;&lt;P&gt;5/ Yep it can be copied&amp;nbsp; to some SASHOME\... location so an additional check can be made is possible,&lt;/P&gt;&lt;P&gt;Someone claiming the deployment of SAS (see gartner BI/Analytic reports feb 2015) would be easy is not knowing the real situation&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the product/version you have and use those instructions guidelines until you know all of the SAS products how they are related.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 14 Apr 2015 10:10:44 GMT</pubDate>
    <dc:creator>jakarman</dc:creator>
    <dc:date>2015-04-14T10:10:44Z</dc:date>
    <item>
      <title>sid_files vs. SASHOME/licenses</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/sid-files-vs-SASHOME-licenses/m-p/195124#M2595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;one document says on thing, one the other, what is the truth?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAS®9.4 Foundation&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.sas.com/documentation/installcenter/en/ikwinbasicri/66608/PDF"&gt;http://support.sas.com/documentation/installcenter/en/ikwinbasicri/66608/PDF&lt;/A&gt;/default/setinit_basic.pdf&lt;/P&gt;&lt;P&gt;"You should add the SAS installation data file to the sid_files directory of the SAS Software Depot ,rather than replacing the SID file that was delivered with the original order. "&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.sas.com/kb/46/207.html"&gt;http://support.sas.com/kb/46/207.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Beginning with SAS 9.3, all SAS license files are located in the SASHOME/licenses directory."&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Apr 2015 09:26:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/sid-files-vs-SASHOME-licenses/m-p/195124#M2595</guid>
      <dc:creator>metallon</dc:creator>
      <dc:date>2015-04-14T09:26:16Z</dc:date>
    </item>
    <item>
      <title>Re: sid_files vs. SASHOME/licenses</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/sid-files-vs-SASHOME-licenses/m-p/195125#M2596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok even that part of applying a license is becoming a tremendous confusing complexity of all issue.&amp;nbsp; That is the truth.&lt;/P&gt;&lt;P&gt;1/ Running a SAS-base (foundation) there is a setinit being applied that is ( one of the many) license protections.&lt;/P&gt;&lt;P&gt;To view and update that information you can use "proc setitnit".&amp;nbsp; When you get the SID you can recognize that as some part of it.&lt;/P&gt;&lt;P&gt;2/ The SID is coming in for the installation with usage of that special "software depot" to be able to use that you to update that one.&lt;/P&gt;&lt;P&gt;3/ With some/several Solutions there is the license being registered in the SAS-metadata. The midtier solutions of SAS can check that one.&lt;/P&gt;&lt;P&gt;4/ Additional tools like LSF and SPD (server) have their own license with a connection by the sid in the same way.&lt;/P&gt;&lt;P&gt;5/ Yep it can be copied&amp;nbsp; to some SASHOME\... location so an additional check can be made is possible,&lt;/P&gt;&lt;P&gt;Someone claiming the deployment of SAS (see gartner BI/Analytic reports feb 2015) would be easy is not knowing the real situation&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the product/version you have and use those instructions guidelines until you know all of the SAS products how they are related.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Apr 2015 10:10:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/sid-files-vs-SASHOME-licenses/m-p/195125#M2596</guid>
      <dc:creator>jakarman</dc:creator>
      <dc:date>2015-04-14T10:10:44Z</dc:date>
    </item>
  </channel>
</rss>

