<?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: SAS Connect Related in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/SAS-Connect-Related/m-p/335538#M272342</link>
    <description>&lt;P&gt;If you don't get a ping response, then the server can't be reached at all.&lt;/P&gt;
&lt;P&gt;Which response do you get from the ping?&lt;/P&gt;
&lt;P&gt;"ping: unknown host &lt;EM&gt;servername&lt;/EM&gt;" or "PING &lt;EM&gt;servername&lt;/EM&gt; (&lt;EM&gt;IP address&lt;/EM&gt;) 56(84) bytes of data."?&lt;/P&gt;
&lt;P&gt;If the first, check if the servername you received is correct. It may be that the definition is missing on your DNS server.&lt;/P&gt;
&lt;P&gt;If the second, talk to the network administrator(s). A firewall might be misconfigured.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once you can ping the mainframe (or you have been told that the mainframe is configured to not respond to pings - unlikely), use telnet to connect to it. It should give you responses according to what is expected in the tcptso.scr file.&lt;/P&gt;
&lt;P&gt;The tcptso.scr is a text file that can be opened with any text editor, its syntax is quite straightforward.&lt;/P&gt;</description>
    <pubDate>Fri, 24 Feb 2017 09:52:05 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2017-02-24T09:52:05Z</dc:date>
    <item>
      <title>SAS Connect Related</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Connect-Related/m-p/335535#M272341</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm using SAS/CONNECT to connect to a Mainframe server from&amp;nbsp;a Linux sevrer. This is what I wrote.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;OPTIONS REMOTE=XXXX.XXX.XXX.XXXXX.COM COMAMID=TCP AUTOSIGNON=YES;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;FILENAME RLINK "/XXX/XXX/XXX/TCPTSO.SCR";&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SIGNON;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It has thrown an error "a communication subsystem partner link setup request failure has occurred".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1) What coudl be the reason for this error and possibel resolution for the same?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2) Is it&amp;nbsp;a pre requisite that the two servers ( Linux and Mainframe ) need to eb inter connected in network? Because , when i issues the command "ping mainframe server name" &amp;nbsp;in my Linux machine, it didn't give any response to the ping.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Vijayanand.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Feb 2017 09:24:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Connect-Related/m-p/335535#M272341</guid>
      <dc:creator>vijayanand</dc:creator>
      <dc:date>2017-02-24T09:24:08Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Connect Related</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Connect-Related/m-p/335538#M272342</link>
      <description>&lt;P&gt;If you don't get a ping response, then the server can't be reached at all.&lt;/P&gt;
&lt;P&gt;Which response do you get from the ping?&lt;/P&gt;
&lt;P&gt;"ping: unknown host &lt;EM&gt;servername&lt;/EM&gt;" or "PING &lt;EM&gt;servername&lt;/EM&gt; (&lt;EM&gt;IP address&lt;/EM&gt;) 56(84) bytes of data."?&lt;/P&gt;
&lt;P&gt;If the first, check if the servername you received is correct. It may be that the definition is missing on your DNS server.&lt;/P&gt;
&lt;P&gt;If the second, talk to the network administrator(s). A firewall might be misconfigured.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Once you can ping the mainframe (or you have been told that the mainframe is configured to not respond to pings - unlikely), use telnet to connect to it. It should give you responses according to what is expected in the tcptso.scr file.&lt;/P&gt;
&lt;P&gt;The tcptso.scr is a text file that can be opened with any text editor, its syntax is quite straightforward.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Feb 2017 09:52:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Connect-Related/m-p/335538#M272342</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-02-24T09:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Connect Related</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Connect-Related/m-p/335620#M272343</link>
      <description>I just want to add that there are dubug statements in the scr file that you can uncomment for easier auditing the connection process.</description>
      <pubDate>Fri, 24 Feb 2017 15:37:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Connect-Related/m-p/335620#M272343</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2017-02-24T15:37:45Z</dc:date>
    </item>
  </channel>
</rss>

