topic Re: DCL script "unrecognized command verb" in Operating System - OpenVMS

DCL script "unrecognized command verb"

Attila Fekete_1 — Wed, 18 May 2005 09:14:27 GMT

Hi,

I tried to create a command file to check some parameters on node. There is a line where I try to ping the a node. When it runs first time it works, but second time I get the message - using the "set verify":
$ tcpip ping Duna2
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\V5\

The node name – Duna2 in this case – is read from a text file. The command line is that:
$ TCPIP ping 'node'
But the text file should be OK, because I tried in a similar script, but without checking other parameters, and it works. So no other caracters are in the variable, just the node name.
Any id

Re: DCL script "unrecognized command verb"

Kris Clippeleyr — Wed, 18 May 2005 09:22:15 GMT

Hi,

Any chance that the command procedure defines a global symbol TCPIP (equated to V5) ?

Kris (aka Qkcl)

Re: DCL script "unrecognized command verb"

Attila Fekete_1 — Wed, 18 May 2005 09:33:16 GMT

Yes, that was it. One of the scipts defined the TCPIP version in the variable "tcpip".

Thanks,
Attila

Re: DCL script "unrecognized command verb"

Daniel Fernandez Illan — Thu, 19 May 2005 03:28:37 GMT

Attila
Why are you defined symbol tcpip using version?
You doesn't need define tcpip symbol to use tcpip.
If you define a symbol similar as:
tcpip="tcpip V5"
On produces the error message.
I think that you must no define symbol tcpip
Saludos.
Daniel.

Re: DCL script "unrecognized command verb"

Attila Fekete_1 — Thu, 19 May 2005 04:24:54 GMT

The script using a variable "TCPIP" is not written by me, but I just copied from another script.

Re: DCL script "unrecognized command verb"

Lawrence Czlapinski — Thu, 19 May 2005 09:58:16 GMT

Attila,
As previously said, your command file is defining a tcpip symbol which is called the 2nd time instead of the tcpip commnad. It's usually not a good practice to define symbols which interfere with command names. It would be better to use a symbol like tcpipv with no shorter alias, or some other name like s_tcpip (for symbol tcpip to distinguish the symbol from the command). I would also recommend changing that tcpip.com file to a different name. This custom tcpip.com file also interferes with normal TCPIP commands since it is getting used at least sometimes instead of the TCPIP executable.
Lawrence
Lawrence

Re: DCL script "unrecognized command verb"

Jan van den Ende — Thu, 19 May 2005 12:10:53 GMT

Attila,

Ofcourse the others are right about the symbol with the same name as a command.

However,
_IF_ you have a command replaced by a symbol, where it is troublesome to correct that,
_OR_
if you deliberately redefine a command (eg, to give it some default parameters, $ del*ete == "delete/confirm/log" comes to mind easily), and, for some reason, you now need to execute the _COMMAND_ instead of the value specified by the symbol,
_THEN_
you invoke the command by extending the command longer than the unique (usually 4) characters, using as extend chars something that makes it different from the (possibly abbreviated) symbol name.
Previous example: DELETEE bypasses the symbol, and executes the command.
(my personal favorite char for this = "\", the backslash).
In your case, _I_ would have used
$ TCPIP\ PING Duna2

Mind, however, that this trick ONLY works for command _SYMBOLS_, _NOT_ for commands redefined with $ SET COMMAND

HTH,

Proost.

Have one on me.

jpe