<?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: proc metalib? in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/proc-metalib/m-p/74156#M21480</link>
    <description>SAS support site - Google advanced search argument  below generates several matching documents for review/consideration:&lt;BR /&gt;
&lt;BR /&gt;
"proc metalib" site:sas.com&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
    <pubDate>Fri, 02 Oct 2009 14:19:19 GMT</pubDate>
    <dc:creator>sbb</dc:creator>
    <dc:date>2009-10-02T14:19:19Z</dc:date>
    <item>
      <title>proc metalib?</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/proc-metalib/m-p/74155#M21479</link>
      <description>Can anyone help me use this procedure?&lt;BR /&gt;
&lt;BR /&gt;
I am trying to replace a dataset on a metdata library with a dataset currently in the work directory.  They have the same fields but will have slightly different number of rows.&lt;BR /&gt;
&lt;BR /&gt;
Sounds simple but I can't do it using a simple datastep, it says I don't have permission and I should use a proc metalib.

Message was edited by: cstanyer</description>
      <pubDate>Fri, 02 Oct 2009 13:41:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/proc-metalib/m-p/74155#M21479</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-10-02T13:41:15Z</dc:date>
    </item>
    <item>
      <title>Re: proc metalib?</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/proc-metalib/m-p/74156#M21480</link>
      <description>SAS support site - Google advanced search argument  below generates several matching documents for review/consideration:&lt;BR /&gt;
&lt;BR /&gt;
"proc metalib" site:sas.com&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
      <pubDate>Fri, 02 Oct 2009 14:19:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/proc-metalib/m-p/74156#M21480</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2009-10-02T14:19:19Z</dc:date>
    </item>
    <item>
      <title>Re: proc metalib?</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/proc-metalib/m-p/74157#M21481</link>
      <description>From what you describe I don't think Proc Metalib is what you're aiming for.&lt;BR /&gt;
&lt;BR /&gt;
Proc Metalib synchronises physical SAS tables with Metadata definitions for SAS tables.&lt;BR /&gt;
&lt;BR /&gt;
Metadata contains only data about data - in the case of a SAS table the metadata would be things like: In what library is the table, what variables with what formats, informats,... are in it, etc.&lt;BR /&gt;
&lt;BR /&gt;
Therefore something like a "dataset on a metadata library" can't be; there is only a metadata table definition pointing to a physical SAS table.&lt;BR /&gt;
&lt;BR /&gt;
As long as you can access the physical SAS table directly (libname myds 'path where target SAS table is stored';) you can ignore the metadata at all for what you want to do.&lt;BR /&gt;
&lt;BR /&gt;
HTH&lt;BR /&gt;
Patrick</description>
      <pubDate>Sat, 03 Oct 2009 08:33:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/proc-metalib/m-p/74157#M21481</guid>
      <dc:creator>Patrick</dc:creator>
      <dc:date>2009-10-03T08:33:58Z</dc:date>
    </item>
  </channel>
</rss>

