<?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: Help in PROC setinit in SAS Health and Life Sciences</title>
    <link>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Help-in-PROC-setinit/m-p/6909#M754</link>
    <description>SETINIT syntax or output?  I didn't think that PROC SETINIT even had any options.  The SETINIT output can be cryptic because it describes the "packages" that have been licensed, not the individual procedures or products.  The expiration dates are clear.&lt;BR /&gt;
&lt;BR /&gt;
To find out the specific procedures available (or licensed, as they can be different) on a SAS server, you could search comp-soft-sys.sas (in Google groups); it's been discussed there multiple times.  It may also be in a SAS note on support.sas.com.</description>
    <pubDate>Thu, 14 Feb 2008 14:00:17 GMT</pubDate>
    <dc:creator>Doc_Duke</dc:creator>
    <dc:date>2008-02-14T14:00:17Z</dc:date>
    <item>
      <title>Help in PROC setinit</title>
      <link>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Help-in-PROC-setinit/m-p/6906#M751</link>
      <description>I have some difficulty in reading POROC SETINIT syntax. could anyone give me a help? Thank you in advance.</description>
      <pubDate>Tue, 12 Feb 2008 13:35:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Help-in-PROC-setinit/m-p/6906#M751</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-02-12T13:35:06Z</dc:date>
    </item>
    <item>
      <title>Re: Help in PROC setinit</title>
      <link>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Help-in-PROC-setinit/m-p/6907#M752</link>
      <description>The SETINIT Procedure licences the products and the licence period for your software.  The code is written by the product licencing group of SAS Institute.&lt;BR /&gt;
&lt;BR /&gt;
None of the code can be changed without rendering the code unworkable.&lt;BR /&gt;
&lt;BR /&gt;
I don't understand why it is important to you.</description>
      <pubDate>Wed, 13 Feb 2008 08:58:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Help-in-PROC-setinit/m-p/6907#M752</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-02-13T08:58:30Z</dc:date>
    </item>
    <item>
      <title>Re: Help in PROC setinit</title>
      <link>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Help-in-PROC-setinit/m-p/6908#M753</link>
      <description>what syntax have you tried?</description>
      <pubDate>Wed, 13 Feb 2008 09:08:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Help-in-PROC-setinit/m-p/6908#M753</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2008-02-13T09:08:38Z</dc:date>
    </item>
    <item>
      <title>Re: Help in PROC setinit</title>
      <link>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Help-in-PROC-setinit/m-p/6909#M754</link>
      <description>SETINIT syntax or output?  I didn't think that PROC SETINIT even had any options.  The SETINIT output can be cryptic because it describes the "packages" that have been licensed, not the individual procedures or products.  The expiration dates are clear.&lt;BR /&gt;
&lt;BR /&gt;
To find out the specific procedures available (or licensed, as they can be different) on a SAS server, you could search comp-soft-sys.sas (in Google groups); it's been discussed there multiple times.  It may also be in a SAS note on support.sas.com.</description>
      <pubDate>Thu, 14 Feb 2008 14:00:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/Help-in-PROC-setinit/m-p/6909#M754</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2008-02-14T14:00:17Z</dc:date>
    </item>
  </channel>
</rss>

