<?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 other sas-software linked with basesas in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/other-sas-software-linked-with-basesas/m-p/17178#M2468</link>
    <description>how to check in base sas, which are all other sas-softwares example(SAS\STAT ,SAS/ASSIST, SAS/GRAPH) licensed with base sas. is there any command for this to check in base sas.</description>
    <pubDate>Sun, 11 May 2008 08:59:06 GMT</pubDate>
    <dc:creator>deleted_user</dc:creator>
    <dc:date>2008-05-11T08:59:06Z</dc:date>
    <item>
      <title>other sas-software linked with basesas</title>
      <link>https://communities.sas.com/t5/SAS-Programming/other-sas-software-linked-with-basesas/m-p/17178#M2468</link>
      <description>how to check in base sas, which are all other sas-softwares example(SAS\STAT ,SAS/ASSIST, SAS/GRAPH) licensed with base sas. is there any command for this to check in base sas.</description>
      <pubDate>Sun, 11 May 2008 08:59:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/other-sas-software-linked-with-basesas/m-p/17178#M2468</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-05-11T08:59:06Z</dc:date>
    </item>
    <item>
      <title>Re: other sas-software linked with basesas</title>
      <link>https://communities.sas.com/t5/SAS-Programming/other-sas-software-linked-with-basesas/m-p/17179#M2469</link>
      <description>Hi:&lt;BR /&gt;
  PROC SETINIT will tell you what's licensed. If you are running in a client/server environment, then you'd have to submit the proc step on every server. If you are running a single-machine install, then submitting this code shows what is licensed:&lt;BR /&gt;
[pre]&lt;BR /&gt;
proc setinit;&lt;BR /&gt;
run;&lt;BR /&gt;
[/pre]&lt;BR /&gt;
 &lt;BR /&gt;
Information is written to the SAS log -- not to the output window.&lt;BR /&gt;
cynthia</description>
      <pubDate>Sun, 11 May 2008 14:40:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/other-sas-software-linked-with-basesas/m-p/17179#M2469</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2008-05-11T14:40:26Z</dc:date>
    </item>
    <item>
      <title>Re: other sas-software linked with basesas</title>
      <link>https://communities.sas.com/t5/SAS-Programming/other-sas-software-linked-with-basesas/m-p/17180#M2470</link>
      <description>One additional note.  SETINIT tells you what is licensed, it does not tell you what is installed.  Lex Jansen posted this solution to the usenet group comp.soft-sys.sas for determining what is actually installed:&lt;BR /&gt;
&lt;BR /&gt;
"You might want to run the SAS Installation Qualification tool (SAS&lt;BR /&gt;
IQ). This will tell you not only what is installed, but also validates&lt;BR /&gt;
the installation to check for misplaced or corrupted software files.&lt;BR /&gt;
I have been using this extensively in the past to validate client&lt;BR /&gt;
installations.&lt;BR /&gt;
I had it setup in such a way that this would run automatically&lt;BR /&gt;
(through a central AUTOEXEC.SAS) when users would run SAS the first&lt;BR /&gt;
time.&lt;BR /&gt;
It compares MD5 checksums of files with SAS supplied checksums and&lt;BR /&gt;
tell you exactly which components are installed.&lt;BR /&gt;
The output is in XML (and also PDF) and can be easily processed if&lt;BR /&gt;
needed.&lt;BR /&gt;
&lt;BR /&gt;
See: &lt;A href="http://support.sas.com/rnd/migration/planning/validation/sasiq.html" target="_blank"&gt;http://support.sas.com/rnd/migration/planning/validation/sasiq.html&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Lex Jansen "&lt;BR /&gt;
&lt;BR /&gt;
There is also a program referenced in this SAS note to do it:&lt;BR /&gt;
&lt;A href="http://support.sas.com/kb/7/640.html" target="_blank"&gt;http://support.sas.com/kb/7/640.html&lt;/A&gt; &lt;BR /&gt;
&lt;BR /&gt;
Doc Muhlbaier&lt;BR /&gt;
Duke</description>
      <pubDate>Mon, 12 May 2008 12:26:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/other-sas-software-linked-with-basesas/m-p/17180#M2470</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2008-05-12T12:26:54Z</dc:date>
    </item>
    <item>
      <title>Re: other sas-software linked with basesas</title>
      <link>https://communities.sas.com/t5/SAS-Programming/other-sas-software-linked-with-basesas/m-p/17181#M2471</link>
      <description>I just reviewed this program&lt;BR /&gt;
&lt;A href="http://support.sas.com/kb/7/640.html" target="_blank"&gt;http://support.sas.com/kb/7/640.html&lt;/A&gt; &lt;BR /&gt;
and it is only current to SAS 9.0 and EGuide 2.0, so the SAS Installation Qualification tool is the better approach.&lt;BR /&gt;
&lt;BR /&gt;
Doc</description>
      <pubDate>Mon, 12 May 2008 13:01:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/other-sas-software-linked-with-basesas/m-p/17181#M2471</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2008-05-12T13:01:09Z</dc:date>
    </item>
  </channel>
</rss>

