<?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 SNA to TCP/Ip conversion in Systems/Software Engineering</title>
    <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/SNA-to-TCP-Ip-conversion/m-p/328758#M3922</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anyone had to convert from SNA to TCP/IP?&lt;/P&gt;&lt;P&gt;Trying to find documentation to accomplish this task.&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Feb 2015 18:27:53 GMT</pubDate>
    <dc:creator>jhuntoon</dc:creator>
    <dc:date>2015-02-17T18:27:53Z</dc:date>
    <item>
      <title>SNA to TCP/Ip conversion</title>
      <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/SNA-to-TCP-Ip-conversion/m-p/328758#M3922</link>
      <description>Has anyone had to convert from SNA to TCP/IP?Trying to find documentation to accomplish this task.John</description>
      <pubDate>Tue, 17 Feb 2015 18:27:53 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/SNA-to-TCP-Ip-conversion/m-p/328758#M3922</guid>
      <dc:creator>jhuntoon</dc:creator>
      <dc:date>2015-02-17T18:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: SNA to TCP/Ip conversion</title>
      <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/SNA-to-TCP-Ip-conversion/m-p/328759#M3923</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm guessing you are specifically asking about &lt;STRONG&gt;Implementer&lt;/STRONG&gt;, since &lt;STRONG&gt;Integrity Lifecycle Manager&lt;/STRONG&gt; does not run over SNA. Is that correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Feb 2015 20:16:35 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/SNA-to-TCP-Ip-conversion/m-p/328759#M3923</guid>
      <dc:creator>KaelLizak</dc:creator>
      <dc:date>2015-02-17T20:16:35Z</dc:date>
    </item>
    <item>
      <title>Re: SNA to TCP/Ip conversion</title>
      <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/SNA-to-TCP-Ip-conversion/m-p/328760#M3924</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;John:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry for the late reply to this ... but a transition from SNA to TCP should be pretty easy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Configure your remote host system with the necessary hostname/IP &amp;amp; port information on panel 4 of the network configuration. &lt;/LI&gt;&lt;LI&gt;Change the remote environment to use TCP/IP-FTP as the distribution method on panel 3 of the environment config.&lt;/LI&gt;&lt;LI&gt;On the remote system, start the remote communication daemon process using the ICOMCTL command with the same port you specified on the remote system network configuration.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make sure any firewalls between the host &amp;amp; remote systems allows FTP traffic and the specified port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At this point, promotions to the remote environment will go over TCP/IP instead of SNA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Obviously, you can contact Implementer support if you run into any problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2015 19:17:14 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/SNA-to-TCP-Ip-conversion/m-p/328760#M3924</guid>
      <dc:creator>David_G</dc:creator>
      <dc:date>2015-04-09T19:17:14Z</dc:date>
    </item>
  </channel>
</rss>

