<?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 Remote access commands in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Remote-access-commands/m-p/342441#M63318</link>
    <description>&lt;P&gt;Hi&lt;BR /&gt;In a code i recently inharited there 2 pieces of code for remote access/connections&lt;BR /&gt;1.options remote=abc comamid=tcp;&lt;BR /&gt; Signon abc;&lt;BR /&gt;2.options remote=xyz ;&lt;BR /&gt; Filename rlink '\\xxx\yyy\xx.....\tcpunix.scr';&lt;BR /&gt; Signon script=rlink;&lt;BR /&gt;&lt;BR /&gt;1) has the comamid=tcp but not the script and 2) the other way arround. Are comamid=tcp and the script pretty much the sime and if not in which cases we can omit the script or tcp command?&lt;BR /&gt;&lt;BR /&gt;Thx&lt;/P&gt;</description>
    <pubDate>Mon, 20 Mar 2017 02:28:21 GMT</pubDate>
    <dc:creator>Tal</dc:creator>
    <dc:date>2017-03-20T02:28:21Z</dc:date>
    <item>
      <title>Remote access commands</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Remote-access-commands/m-p/342441#M63318</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt;In a code i recently inharited there 2 pieces of code for remote access/connections&lt;BR /&gt;1.options remote=abc comamid=tcp;&lt;BR /&gt; Signon abc;&lt;BR /&gt;2.options remote=xyz ;&lt;BR /&gt; Filename rlink '\\xxx\yyy\xx.....\tcpunix.scr';&lt;BR /&gt; Signon script=rlink;&lt;BR /&gt;&lt;BR /&gt;1) has the comamid=tcp but not the script and 2) the other way arround. Are comamid=tcp and the script pretty much the sime and if not in which cases we can omit the script or tcp command?&lt;BR /&gt;&lt;BR /&gt;Thx&lt;/P&gt;</description>
      <pubDate>Mon, 20 Mar 2017 02:28:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Remote-access-commands/m-p/342441#M63318</guid>
      <dc:creator>Tal</dc:creator>
      <dc:date>2017-03-20T02:28:21Z</dc:date>
    </item>
    <item>
      <title>Re: Remote access commands</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Remote-access-commands/m-p/342452#M63321</link>
      <description>&lt;P&gt;Most SAS/CONNECT sites use scriptless SIGNONs these days in my experience. You need to have the SAS/CONNECT spawner running as a service on your remote SAS server for this to work. If it is running then just remove the SCRIPT= option from your SIGNON and see if it works.&lt;/P&gt;</description>
      <pubDate>Mon, 20 Mar 2017 03:13:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Remote-access-commands/m-p/342452#M63321</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2017-03-20T03:13:26Z</dc:date>
    </item>
    <item>
      <title>Re: Remote access commands</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Remote-access-commands/m-p/344446#M63484</link>
      <description>&lt;P&gt;thx SASKiwi&lt;/P&gt;
&lt;P&gt;it&amp;nbsp; does run&lt;/P&gt;</description>
      <pubDate>Sun, 26 Mar 2017 20:07:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Remote-access-commands/m-p/344446#M63484</guid>
      <dc:creator>Tal</dc:creator>
      <dc:date>2017-03-26T20:07:39Z</dc:date>
    </item>
  </channel>
</rss>

