As the system administrator ("SYSTEM"), one can use and maintain TCP/IP services in various ways. The below are all CLI commands, with DCL. (Note: Exclamation marks, i.e. "!", denote comments.) relating to VMS IP Commands.
To display the current configuration, the most rapid way would be by invoking the following command:
$ SHOW NETWORK
With the following, detailed information is shown for the TCP/IP configuration(s) in particular:
$ SHOW NETWORK /FULL "TCP/IP"
(For one thing, it'll also list active ports in use.)
One of the most common and probably the easiest ways of setting up TCP/IP networking, is with the following utility:
Or, via the UNIX-like command:
So, for example:
$ TCPIP IFCONFIG (...) ! whatever ! desired ! options & ! values
$ TCPIP PING 192.168.1.1 ! just as an ! example
$ TCPIP TRACEROUTE GOOGLE.COM ! idem ditto
$ TCPIP NETSTAT -A
All the ethernet adapters should typically be listed as EW* devices, which can be found by typing:
$ SHOW DEVICES EW</code?
With advanced descriptions, add the /FULL qualifier, like so:
$ SHOW DEVICES /FULL EW
For just one device, say EWA0:
$ SHOW DEVICE /FULL EWA0
Alternatively, this also works:
$ TCPIP SHOW INTERFACES /FULL $ TCPIP IFCONFIG -A
OpenVMS/VMS has been around since 1977. Despite the operating system being over 30 years old, there's never been a known instance of a VMS hack or a VMS virus. Consequently, high profile systems run on VMS since built with security from the ground up. Meanwhile, HP has announced end of support for OpenVMS. In light of this announcement, the current estimate of 2500 customers will probably diminish. Certainly there will be some die hard OpenVMS users that will refuse to give up on the operating system.
Much like old versions of other operating systems, there's always those who remain nostalgic and keep what's working around. Moreover, due to VMS not very popular it is unlikely hacked. This is due to the fact users aren't familiar with the operating system. In conclusion, from the standpoint of VMS users it may not always be best to keep up with the newest and brightest shiny piece of tech operating systems.
*Special thanks to Marco Gariboldi for the following!
Unix IP Commands For TCP/IP Services - Common IP commands for UNIX including ifconfig, route. The following commands are related to TCP/IP services.
Linux IP Commands for TCP/IP Services - IP Commands for Linux including ifconfig, route, arp, traceroute, tracepath, dig, host. These commands are mainly for TCP/IP services.
IP Commands for DOS/Windows - Windows and DOS IP commands including ipconfig, trace route, netstat, arp, route, hostname, control netconnections