<?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: signon remote in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/signon-remote/m-p/603774#M174960</link>
    <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/117666"&gt;@rudfaden&lt;/a&gt;&amp;nbsp; - This type of problem should be the responsibility of your SAS administrator so I suggest you should discuss that with him / her.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ideally this can be done by assigning libraries in SAS metadata and aligning metadata permissions with OS folder permissions. Once they align you shouldn't get any allocation failures because you will only get libraries allocated if you have the metadata permission to assign them.&lt;/P&gt;</description>
    <pubDate>Wed, 13 Nov 2019 06:09:00 GMT</pubDate>
    <dc:creator>SASKiwi</dc:creator>
    <dc:date>2019-11-13T06:09:00Z</dc:date>
    <item>
      <title>signon remote</title>
      <link>https://communities.sas.com/t5/SAS-Programming/signon-remote/m-p/603566#M174868</link>
      <description>&lt;P&gt;I am tryning to sigon to SAS grid. When I signon, SAS tries to alllocate all librefs, even some that I do not have acces to, resulting in errors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;%let rc = %sysfunc( grdsvc_enable(_all_, server= SASAppIB));
options autosignon;
*signon grid1 inheritlib=(work=swork format funk) ;
%syslput _ALL_;

rsubmit task1 wait=no;
    %put &amp;amp;periode;
endrsubmit;

signoff grid1;&lt;/CODE&gt;&lt;/PRE&gt;&lt;PRE&gt;NOTE: Libref SD successfully assigned from logical server.
ERROR: Libref MATCHV2 failed to assign from logical server.&lt;/PRE&gt;&lt;P&gt;Is there anyway to determine which libraries that are assigned to the remote session ot should the problem be fixed in the metadata?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2019 13:01:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/signon-remote/m-p/603566#M174868</guid>
      <dc:creator>rudfaden</dc:creator>
      <dc:date>2019-11-12T13:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: signon remote</title>
      <link>https://communities.sas.com/t5/SAS-Programming/signon-remote/m-p/603742#M174940</link>
      <description>&lt;P&gt;I suppose you (or the autoexec file) could always try to&amp;nbsp;&amp;nbsp; &lt;FONT face="courier new,courier"&gt;dopen()&lt;/FONT&gt; &amp;nbsp; a path before trying to assign it.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2019 03:00:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/signon-remote/m-p/603742#M174940</guid>
      <dc:creator>ChrisNZ</dc:creator>
      <dc:date>2019-11-13T03:00:36Z</dc:date>
    </item>
    <item>
      <title>Re: signon remote</title>
      <link>https://communities.sas.com/t5/SAS-Programming/signon-remote/m-p/603774#M174960</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/117666"&gt;@rudfaden&lt;/a&gt;&amp;nbsp; - This type of problem should be the responsibility of your SAS administrator so I suggest you should discuss that with him / her.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ideally this can be done by assigning libraries in SAS metadata and aligning metadata permissions with OS folder permissions. Once they align you shouldn't get any allocation failures because you will only get libraries allocated if you have the metadata permission to assign them.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2019 06:09:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/signon-remote/m-p/603774#M174960</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2019-11-13T06:09:00Z</dc:date>
    </item>
  </channel>
</rss>

