<?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: configuring TCP/IP for one node from another node in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/configuring-tcp-ip-for-one-node-from-another-node/m-p/4401488#M94223</link>
    <description>&lt;!--!*#--&gt;Found it!  The very useful but undocumented qualifier is /ON=node, which apparently works for all SHOW CONFIG and SET CONFIG commands.&lt;BR /&gt;&lt;BR /&gt;$ TCPIP SHOW CONFIG INTERFACE /ON=ADAM&lt;BR /&gt;$ TCPIP SET CONFIG INTERFACE /ON=ADAM WE0 ...&lt;BR /&gt;$ TCPIP SHOW CONFIG ENABLE SERVICE /ON=BETA&lt;BR /&gt;$ TCPIP SET CONFIG ENABLE SERVICE FTP /ON=BETA&lt;BR /&gt;&lt;BR /&gt;Thanks Robert!</description>
    <pubDate>Wed, 15 Apr 2009 19:25:23 GMT</pubDate>
    <dc:creator>Jess Goodman</dc:creator>
    <dc:date>2009-04-15T19:25:23Z</dc:date>
    <item>
      <title>configuring TCP/IP for one node from another node</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/configuring-tcp-ip-for-one-node-from-another-node/m-p/4401485#M94220</link>
      <description>&lt;!--!*#--&gt;Is there any trick that can be used to configure TCP/IP services for another node?&lt;BR /&gt;&lt;BR /&gt;When you run @TCPIP$CONFIG or execute TCPIP SET CONFIG commands it creates or updates records in TCPIP$CONFIGURATION.DAT.  Those records contain the node name of the current node.&lt;BR /&gt;&lt;BR /&gt;I would like to be able to create or update the records for a node not currently booted.  This would save me a step, since I now have to boot that node into the cluster without any applications or batch jobs that require TCP/IP running on it before I can (re)configure TCP/IP.&lt;BR /&gt;&lt;BR /&gt;I also like to reboot a node after TCP/IP is (re)configured to be sure there is no problem with the configuration or its startup, so I now I have to boot a node twice to (re)configure it.</description>
      <pubDate>Wed, 15 Apr 2009 15:41:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/configuring-tcp-ip-for-one-node-from-another-node/m-p/4401485#M94220</guid>
      <dc:creator>Jess Goodman</dc:creator>
      <dc:date>2009-04-15T15:41:27Z</dc:date>
    </item>
    <item>
      <title>Re: configuring TCP/IP for one node from another node</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/configuring-tcp-ip-for-one-node-from-another-node/m-p/4401486#M94221</link>
      <description>Not that I'd try this with a production box, but....&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://groups.google.com/group/comp.os.vms/browse_thread/thread/46d885717190a361" target="_blank"&gt;http://groups.google.com/group/comp.os.vms/browse_thread/thread/46d885717190a361&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Apr 2009 15:52:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/configuring-tcp-ip-for-one-node-from-another-node/m-p/4401486#M94221</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-04-15T15:52:15Z</dc:date>
    </item>
    <item>
      <title>Re: configuring TCP/IP for one node from another node</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/configuring-tcp-ip-for-one-node-from-another-node/m-p/4401487#M94222</link>
      <description>Jess,&lt;BR /&gt;&lt;BR /&gt;I have to run out for a meeting, so I do not have time to root around for the precise qualifier, however:&lt;BR /&gt;&lt;BR /&gt;My recollection is that there is an undocumented qualifier within TCPIP that will allow the information relating to a node other than the one that is presently running.&lt;BR /&gt;&lt;BR /&gt;If my recollection is correct, this would be the way to do what is described. Modifying the files directly is probably a poor idea (and yes, I have been one of the people quietly lobbying for it to be supported).&lt;BR /&gt;&lt;BR /&gt;Alternatively, one could insert a command file into the startup sequence at a phase prior to when SYSTARTUP_VMS.COM is invoked to issue the needed commands to configure TCPIP (at which point the TCPIP startup will work as advertised).&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Wed, 15 Apr 2009 17:26:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/configuring-tcp-ip-for-one-node-from-another-node/m-p/4401487#M94222</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2009-04-15T17:26:57Z</dc:date>
    </item>
    <item>
      <title>Re: configuring TCP/IP for one node from another node</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/configuring-tcp-ip-for-one-node-from-another-node/m-p/4401488#M94223</link>
      <description>&lt;!--!*#--&gt;Found it!  The very useful but undocumented qualifier is /ON=node, which apparently works for all SHOW CONFIG and SET CONFIG commands.&lt;BR /&gt;&lt;BR /&gt;$ TCPIP SHOW CONFIG INTERFACE /ON=ADAM&lt;BR /&gt;$ TCPIP SET CONFIG INTERFACE /ON=ADAM WE0 ...&lt;BR /&gt;$ TCPIP SHOW CONFIG ENABLE SERVICE /ON=BETA&lt;BR /&gt;$ TCPIP SET CONFIG ENABLE SERVICE FTP /ON=BETA&lt;BR /&gt;&lt;BR /&gt;Thanks Robert!</description>
      <pubDate>Wed, 15 Apr 2009 19:25:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/configuring-tcp-ip-for-one-node-from-another-node/m-p/4401488#M94223</guid>
      <dc:creator>Jess Goodman</dc:creator>
      <dc:date>2009-04-15T19:25:23Z</dc:date>
    </item>
  </channel>
</rss>

