<?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: DI studio pre assigned library in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/DI-studio-pre-assigned-library/m-p/417976#M12748</link>
    <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/59634"&gt;@89sankar&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;If a library is defined as pre-assigned in SAS Metadata then the library definition gets executed during SAS invocation.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For pre-assigned libraries via SAS Medatada SAS DIS won't generate a Libname statement in the deployed code.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If using pre-assigned libraries pointing to databases then I'm normally also using libname option &lt;EM&gt;defer=yes&lt;/EM&gt; so that the actual connection to the database only gets established once you actually use a table from&amp;nbsp;that database in your DIS job.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In case your server is locked-down then using pre-assigned libraries allows you to use paths to folders which are otherwise not accessible. That opens up quite a few opportunities when it comes to securing an environment and controlling which users can access what using SAS.&lt;/P&gt;
&lt;P&gt;&lt;A href="http://documentation.sas.com/?docsetId=bisecag&amp;amp;docsetTarget=p0eo05w7u850lgn1n1i5vquf07vg.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en&amp;nbsp;" target="_blank"&gt;http://documentation.sas.com/?docsetId=bisecag&amp;amp;docsetTarget=p0eo05w7u850lgn1n1i5vquf07vg.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 02 Dec 2017 23:34:21 GMT</pubDate>
    <dc:creator>Patrick</dc:creator>
    <dc:date>2017-12-02T23:34:21Z</dc:date>
    <item>
      <title>DI studio pre assigned library</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/DI-studio-pre-assigned-library/m-p/417944#M12746</link>
      <description>&lt;P&gt;In DI studio new library wizard, what is preassigned library and generic library type?&lt;/P&gt;</description>
      <pubDate>Sat, 02 Dec 2017 14:31:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/DI-studio-pre-assigned-library/m-p/417944#M12746</guid>
      <dc:creator>89sankar</dc:creator>
      <dc:date>2017-12-02T14:31:10Z</dc:date>
    </item>
    <item>
      <title>Re: DI studio pre assigned library</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/DI-studio-pre-assigned-library/m-p/417975#M12747</link>
      <description>Pre-assigned is when the DI Studio job early on that the library is assigned by central configuration. Either by an autoexec or via the metadataibrary registration.</description>
      <pubDate>Sat, 02 Dec 2017 23:11:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/DI-studio-pre-assigned-library/m-p/417975#M12747</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2017-12-02T23:11:46Z</dc:date>
    </item>
    <item>
      <title>Re: DI studio pre assigned library</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/DI-studio-pre-assigned-library/m-p/417976#M12748</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/59634"&gt;@89sankar&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;If a library is defined as pre-assigned in SAS Metadata then the library definition gets executed during SAS invocation.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For pre-assigned libraries via SAS Medatada SAS DIS won't generate a Libname statement in the deployed code.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If using pre-assigned libraries pointing to databases then I'm normally also using libname option &lt;EM&gt;defer=yes&lt;/EM&gt; so that the actual connection to the database only gets established once you actually use a table from&amp;nbsp;that database in your DIS job.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In case your server is locked-down then using pre-assigned libraries allows you to use paths to folders which are otherwise not accessible. That opens up quite a few opportunities when it comes to securing an environment and controlling which users can access what using SAS.&lt;/P&gt;
&lt;P&gt;&lt;A href="http://documentation.sas.com/?docsetId=bisecag&amp;amp;docsetTarget=p0eo05w7u850lgn1n1i5vquf07vg.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en&amp;nbsp;" target="_blank"&gt;http://documentation.sas.com/?docsetId=bisecag&amp;amp;docsetTarget=p0eo05w7u850lgn1n1i5vquf07vg.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 02 Dec 2017 23:34:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/DI-studio-pre-assigned-library/m-p/417976#M12748</guid>
      <dc:creator>Patrick</dc:creator>
      <dc:date>2017-12-02T23:34:21Z</dc:date>
    </item>
  </channel>
</rss>

