TELNET command not working

[Joewee]

I have installed multinet on my Hobbyist machine and uninstalled it from that time TELNET command is not working. Im not sure where could the problem be.


$ sho sys/noproc
OpenVMS V8.3 on node TEST1 23-JUL-2010 00:18:07.81 Uptime 0 00:14:06
$ sho net

Product: MULTINET Node: Address(es):
Product: DECNET Node: TEST1 Address(es): 1.1
Product: TCP/IP Node: test1.hcl.in Address(es): 192.168.1.34
$ ucx sho services

Service Port Proto Process Address State

FTP 21 TCP TCPIP$FTP 0.0.0.0 Enabled
RLOGIN 513 TCP not defined 0.0.0.0 Disabled
SSH 22 TCP TCPIP$SSH 0.0.0.0 Disabled
TELNET 23 TCP not defined 0.0.0.0 Enabled
$ telnet
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\TELNET\
$

[Steven Schweda]

> I have installed multinet on my Hobbyist
> machine and uninstalled it from that time
> TELNET command is not working. Im not sure
> where could the problem be.

The problem would seem to be that you
uninstalled the only IP software you had, so
that you no longer have a TELNET command.

Have you tried installing something else,
like, say, TCPIP (again)? Knowing nothing,
I'd guess that installing MultiNet inserts a
TELNET verb into the system command tables,
and that uninstalling MultiNet removes that
TELNET verb definition, but doesn't restore
any old one which might have existed before.
Installing TCPIP (again) should put its
TELNET verb (back) into the system command
tables.

[Joewee]

I guessed that and I deleted the latest version of dcltables.exe in SYS$COMMON:[SYSLIB]

now Im getting


$ telnet
%DCL-W-ACTIMAGE, error activating image MULTINET:TELNET
-CLI-E-IMGNAME, image file MULTINET:[SYSEXE]TELNET.EXE;
-RMS-F-DEV, error in device name or inappropriate device type for operation
$


I think doing something wrong..

Installing TCP is the only way?? or is there any workaround?

[Verne Britton]

TCP/IP Services for OpenVMS used to be known as UCX ...

and both are TCP stacks with all the utilities and commands.

Multinet is another TCP stack (from a 3rd party company Process Software), with its own set of utilities and commands ... naturally many of the commands have the same name, like TELNET and FTP, but the underlying actual EXE files are different and are located in different directories.

So in summary, if you want TCPIP from HP, you must install it.

If you want Multinet, you must install it.

And only have one installed at a time ... and it may be a good idea if possible to deinstall one before installing the other ($PRODUCT REMOVE ... for TCPIP/UCX ... don't think Multinet has a REMOVE function).

And you may want to reboot after any install or deinstall to get all the pieces in place for either product to work, as well has having the proper commands in your startup file to start it up.

Verne

[Joewee]

@Steven & verne: Thanks for that. The mistake I did was I have not uninstalled TCP before installing MULTINET. I will install TCP again.


Since this is jus my test machine. I wanted to try something different. I have backup of my old (.vdisk) I will use that also if needed.

Now I just googled and tried something like this. I know this is not the correct solution but still jus need your suggestion on this.

$ ty telnet.cld
DEFINE VERB TELNET
IMAGE "SYS$SYSEXE:TCPIP$TELNET.EXE"
$

$ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE SYS$COMMON:[SYSLIB]TELNET.CLD
$ INSTALL LIST SYS$LIBRARY:DCLTABLES

DISK$ALPHASYS:.EXE
DCLTABLES;83 Open Hdr Shared Lnkbl
$ INSTALL REPLACE SYS$LIBRARY:DCLTABLES/OPEN/HEADER_RESIDENT/SHARED

$ telnet
%DCL-W-ACTIMAGE, error activating image MULTINET:TELNET
-CLI-E-IMGNAME, image file MULTINET:[SYSEXE]TELNET.EXE;
-RMS-F-DEV, error in device name or inappropriate device type for operation

[Jon Pinkley]

Your process still has the old copy of the command verb. Log out and login again.

[Steven Schweda]

> I guessed that and I deleted the latest
> version of dcltables.exe in
> SYS$COMMON:[SYSLIB]

Great. Now you're back to the way it was
when MultiNet _was_ installed (before you
uninstalled it). If you have one more
version in the pile, then the next one back
might be the one from _before_ you installed
MultiNet.

> Installing TCP is the only way??

No, it's not the only way, it's only the easy
way.

> or is there any workaround?

Find the right DCLTABLES.EXE?


> $ ty telnet.cld
> [...]

Around here, that seems to be about 145 lines
of stuff, not two.

[Jon Pinkley]

Steven Schweda is correct. It will be much easier to reinstall TCPIP services than to try to patch things up. Otherwise you continue to discover problems that were not fixed.

When you installed Multinet, it modified many things, and trying to undo them is not going to be easy to do manually.

Do you have a snapshot of the vdisk before you installed Mulitinet? If so I would revert to that if you don't want to have leftover cruft from the multinet installation.

[The Brit]

You might also try

$ show symbol telnet

I know that TCPWARE (another Process Software stack) defines telnet as a symbol, vis

$ show symb telnet
TELNET == "$TCPWARE:TELNET"

This is done in a file called TCPWARE:TCPWARE_COMMANDS.COM

I am not familiar with MULTINET, I just mention this because it may have a similar organisation.

Just a thought.

Dave.