GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- configuring TCP/IP for one node from another node
Operating System - OpenVMS
1845519
Members
3980
Online
110244
Solutions
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
Forums
Categories
This widget could not be displayed.
Company
This widget could not be displayed.
Local Language
This widget could not be displayed.
back
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
back
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
Blogs
Information
This widget could not be displayed.
This widget could not be displayed.
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2009 08:41 AM
04-15-2009 08:41 AM
Is there any trick that can be used to configure TCP/IP services for another node?
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.
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.
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.
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.
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.
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.
I have one, but it's personal.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2009 08:52 AM
04-15-2009 08:52 AM
Re: configuring TCP/IP for one node from another node
Not that I'd try this with a production box, but....
http://groups.google.com/group/comp.os.vms/browse_thread/thread/46d885717190a361
http://groups.google.com/group/comp.os.vms/browse_thread/thread/46d885717190a361
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2009 10:26 AM
04-15-2009 10:26 AM
Solution
Jess,
I have to run out for a meeting, so I do not have time to root around for the precise qualifier, however:
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.
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).
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).
- Bob Gezelter, http://www.rlgsc.com
I have to run out for a meeting, so I do not have time to root around for the precise qualifier, however:
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.
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).
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).
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2009 12:25 PM
04-15-2009 12:25 PM
Re: configuring TCP/IP for one node from another node
Found it! The very useful but undocumented qualifier is /ON=node, which apparently works for all SHOW CONFIG and SET CONFIG commands.
$ TCPIP SHOW CONFIG INTERFACE /ON=ADAM
$ TCPIP SET CONFIG INTERFACE /ON=ADAM WE0 ...
$ TCPIP SHOW CONFIG ENABLE SERVICE /ON=BETA
$ TCPIP SET CONFIG ENABLE SERVICE FTP /ON=BETA
Thanks Robert!
$ TCPIP SHOW CONFIG INTERFACE /ON=ADAM
$ TCPIP SET CONFIG INTERFACE /ON=ADAM WE0 ...
$ TCPIP SHOW CONFIG ENABLE SERVICE /ON=BETA
$ TCPIP SET CONFIG ENABLE SERVICE FTP /ON=BETA
Thanks Robert!
I have one, but it's personal.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP