<?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 Forcing all sas queries to execute remotely in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11481#M2700</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try this...Hope this helps..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;signon outtsk2 sascmd="C:\Program Files\SAS\SASFoundation\9.2\sas.exe -nosyntaxcheck";&lt;/P&gt;&lt;P&gt;rsubmit outtsk2 wait=no;&lt;/P&gt;&lt;P&gt;libname tt 'F:\SASALM';&lt;/P&gt;&lt;P&gt;data tt.want;&lt;/P&gt;&lt;P&gt;input name $ no;&lt;/P&gt;&lt;P&gt;cards;&lt;/P&gt;&lt;P&gt;test 12&lt;/P&gt;&lt;P&gt;want 23&lt;/P&gt;&lt;P&gt;ravi 44&lt;/P&gt;&lt;P&gt;;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;endrsubmit;&lt;/P&gt;&lt;P&gt;signoff outtsk2;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Shiva&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Feb 2012 15:25:08 GMT</pubDate>
    <dc:creator>shivas</dc:creator>
    <dc:date>2012-02-24T15:25:08Z</dc:date>
    <item>
      <title>Forcing all sas queries to execute remotely</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11473#M2692</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to setup Enterprise Guide so all code will be executed remotely by using the Custom Code in the options to wrap everything with rsubmit.&lt;/P&gt;&lt;P&gt;However, I'm running into problems with signing on.&lt;/P&gt;&lt;P&gt;I am using Enterprise Guide on a client pc, and am trying to submit to SAS on an AIX server XXXXXXXX port 8561. So I have used the following in my custom code but with no success:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;signon XXXXXXXX.8561;&lt;/P&gt;&lt;P&gt;rsubmit;&lt;/P&gt;&lt;P&gt;*************************************&lt;/P&gt;&lt;P&gt;%let serv = XXXXXXXX 8561;&lt;/P&gt;&lt;P&gt;signon serv;&lt;/P&gt;&lt;P&gt;rsubmit;&lt;/P&gt;&lt;P&gt;*************************************&lt;/P&gt;&lt;P&gt;%let serv = XXXXXXXX 8561;&lt;/P&gt;&lt;P&gt;options comamid=TCP remote=serv;&lt;/P&gt;&lt;P&gt;rsubmit;&lt;/P&gt;&lt;P&gt;*************************************&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, I keep getting repeated errors, stating either 'a tcp link needs to be established' or 'a link must be established by executing the SIGNON command'.&lt;/P&gt;&lt;P&gt;Going round in circles on that SAS website with different options and recommendations, but nothing has worked. Any suggestions?&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000; font-size: 10pt; font-family: Courier New;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Feb 2012 16:27:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11473#M2692</guid>
      <dc:creator>hardej2</dc:creator>
      <dc:date>2012-02-23T16:27:58Z</dc:date>
    </item>
    <item>
      <title>Forcing all sas queries to execute remotely</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11474#M2693</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why don't you just choose the SAS Server that you want to use from within EGuide?&amp;nbsp;&amp;nbsp; That seems a much more direct approach.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Feb 2012 16:44:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11474#M2693</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2012-02-23T16:44:28Z</dc:date>
    </item>
    <item>
      <title>Forcing all sas queries to execute remotely</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11475#M2694</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; I don't want to submit the query locally on my client machine, I want to submit it remotely to the server.&lt;/P&gt;&lt;P&gt;When i select the SAS server within EG and submit, it performs the query in place. I want to force all code submitted to remote submit to a server.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Feb 2012 16:47:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11475#M2694</guid>
      <dc:creator>hardej2</dc:creator>
      <dc:date>2012-02-23T16:47:41Z</dc:date>
    </item>
    <item>
      <title>Forcing all sas queries to execute remotely</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11476#M2695</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sounds like you might be using the wrong profile.&amp;nbsp; You can check (and create) profiles in tools --&amp;gt; options --&amp;gt; administration --&amp;gt; connection profiles and set up a default (remote) server there.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Feb 2012 19:45:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11476#M2695</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2012-02-23T19:45:19Z</dc:date>
    </item>
    <item>
      <title>Forcing all sas queries to execute remotely</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11477#M2696</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;EG always submits code to a Server.&amp;nbsp; Are you saying you do not want to use your local machine as the server?&amp;nbsp; Can't you just connect to a different server?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Feb 2012 20:48:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11477#M2696</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2012-02-23T20:48:04Z</dc:date>
    </item>
    <item>
      <title>Forcing all sas queries to execute remotely</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11478#M2697</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am under the impression that while code or a query runs in EG, the majority of the processing runs in the foreground. A job needs to explicitly call rsubmit to submit it as a batch job&lt;/P&gt;&lt;P&gt;to a server and execute there, freeing up the eg session. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this is not the case then, it looks like i don't have a problem. N.B. I am an infrastructure admin concerned with using EG to replace a similar remote submite function.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Feb 2012 20:58:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11478#M2697</guid>
      <dc:creator>hardej2</dc:creator>
      <dc:date>2012-02-23T20:58:29Z</dc:date>
    </item>
    <item>
      <title>Forcing all sas queries to execute remotely</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11479#M2698</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just to reinforce Tom's comment, EG is a thin-client interface to SAS, so all code submitted by EG runs on a SAS server. That server might be the same PC as EG if it has a complete SAS install. If it hasn't then there is no option but to run the code on a remote server, in your case AIX Unix server. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you start EG it usually automatically signs on to the remote server(s) so signon and rsubmit statements become redundant.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Feb 2012 03:42:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11479#M2698</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2012-02-24T03:42:32Z</dc:date>
    </item>
    <item>
      <title>Forcing all sas queries to execute remotely</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11480#M2699</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Tom &amp;amp; SASKiwi, thank you.&lt;/P&gt;&lt;P&gt;I am a relative newcomer to SAS and was getting a bit muddled when trying to convert functionality from existing applications to other applications.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Feb 2012 13:29:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11480#M2699</guid>
      <dc:creator>hardej2</dc:creator>
      <dc:date>2012-02-24T13:29:40Z</dc:date>
    </item>
    <item>
      <title>Forcing all sas queries to execute remotely</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11481#M2700</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try this...Hope this helps..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;signon outtsk2 sascmd="C:\Program Files\SAS\SASFoundation\9.2\sas.exe -nosyntaxcheck";&lt;/P&gt;&lt;P&gt;rsubmit outtsk2 wait=no;&lt;/P&gt;&lt;P&gt;libname tt 'F:\SASALM';&lt;/P&gt;&lt;P&gt;data tt.want;&lt;/P&gt;&lt;P&gt;input name $ no;&lt;/P&gt;&lt;P&gt;cards;&lt;/P&gt;&lt;P&gt;test 12&lt;/P&gt;&lt;P&gt;want 23&lt;/P&gt;&lt;P&gt;ravi 44&lt;/P&gt;&lt;P&gt;;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;endrsubmit;&lt;/P&gt;&lt;P&gt;signoff outtsk2;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Shiva&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Feb 2012 15:25:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11481#M2700</guid>
      <dc:creator>shivas</dc:creator>
      <dc:date>2012-02-24T15:25:08Z</dc:date>
    </item>
    <item>
      <title>Forcing all sas queries to execute remotely</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11482#M2701</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;UL&gt;&lt;LI&gt;You can create a profile in SAS EG by clicking on "&lt;STRONG&gt;No profile selected&lt;/STRONG&gt;" on the bottom right hand side corner of the tool. &lt;/LI&gt;&lt;LI&gt;A window pops up. Click on Add.&lt;/LI&gt;&lt;LI&gt;Another window pops up and will ask you for details like Name, Description,&amp;nbsp; Machine, port, User, Password and authentication domain.&lt;/LI&gt;&lt;LI&gt;Enter all those details and click on Save.&lt;/LI&gt;&lt;LI&gt;Click on Set active.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This connects you to the server. Once connected successfully. Run the code begininning with the line RSUBMIT &amp;lt;SERVERNAME&amp;gt;; and end the code with ENDRSUBMIT;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Feb 2012 15:33:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Forcing-all-sas-queries-to-execute-remotely/m-p/11482#M2701</guid>
      <dc:creator>Hima</dc:creator>
      <dc:date>2012-02-24T15:33:45Z</dc:date>
    </item>
  </channel>
</rss>

