topic Re: TCPIPTRACE won't run in Operating System - OpenVMS

TCPIPTRACE won't run

Aaron Sakovich — Wed, 06 Apr 2005 11:01:16 GMT

I try

$ tcpiptrace host /port...
%CLI-W-IVVERB, unrecognized command verb - check validity and spelling
\HOST\

I try

$ mcr tcpip$trace host /port=...
%CLI-F-SYNTAX, error parsing 'address'
-CLI-E-ENTNF, specified entity not found in command tables

I try

$ run sys$system:tcpip$trace
%CLI-F-SYNTAX, error parsing 'address'
-CLI-E-ENTNF, specified entity not found in command tables

I try

$ tcpiptrace
TCPIP>

Why can't I run TCPIPTRACE??? Why does the TCPIP command keep getting in the way? There's no symbol set for either, and setting a foreign command for TCPIPTRACE does no better than the MCR or RUN commands show above.

Bamboozled,
Aaron

Re: TCPIPTRACE won't run

Uwe Zessin — Wed, 06 Apr 2005 11:29:12 GMT

The command verb is "TCPTRACE".

Boom. Falls off chair ;-)

Re: TCPIPTRACE won't run

Dale A. Marcy — Wed, 06 Apr 2005 11:31:43 GMT

I use multinet, so my comment may be way off, but looking at your post, I wonder if the first command should have a space between the tcpip and trace instead of being one word tcpiptrace? I know in multinet, the command is:

$ multinet trace host.x.x.x

Re: TCPIPTRACE won't run

Jeffery D. Urmann — Wed, 06 Apr 2005 11:32:39 GMT

Hey Aaron,

The error is referring to the command argument HOST. TCPIP is a DCL verb that runs the TCPIP utility.

Are you trying to run a traceroute?

try:
MCR TCPIP$TraceRoute

Enjoy,

--Jeff

Re: TCPIPTRACE won't run

Aaron Sakovich — Wed, 06 Apr 2005 11:39:38 GMT

TCPTRACE. *sigh* (picking self up off the floor)

Rhetorical question: why doesn't the documentation document this? Or is this just an undocumented feature -- make you GUESS at what the command really is?

$ HELP TCPIPTRACE

TCPIPTRACE

Starts the UCX$TRACE utility.

Format

/BUFFERS=n
/FULL
TCPIPTRACE host /OUTPUT
/PACKETS=n
/PORT=option
/PROTOCOL=option

Additional information available:

Parameters Qualifiers
/BUFFERS /FULL /OUTPUT /PACKETS /PORT /PROTOCOL
Examples

Thanks!

Re: TCPIPTRACE won't run

Uwe Zessin — Wed, 06 Apr 2005 11:45:32 GMT

I see this help entry on a OpenVMS Alpha V6.2-1H3 with UCX V4.2, but not on a recent V7.3-2 with TCPIP V5.4 system. The later one was a rather fresh install (started as V7.3-1).

You don't say on what version you are running, but it might be a stale HELP entry.

I do have a TCPTRACE help entry on the V7 system.

Re: TCPIPTRACE won't run

Uwe Zessin — Wed, 06 Apr 2005 11:49:56 GMT

Just forgot:
$ HELP TCPIP

has an entry named 'Tracing' that gives a hint to TCPTRACE.

Re: TCPIPTRACE won't run

Aaron Sakovich — Wed, 06 Apr 2005 11:56:14 GMT

OpenVMS v7.3-2, TCP/IP Svcs 5.4 ECO 4. (Almost) latest & greatest, upgraded over the years from OpenVMS 6.2-1H3 FIS.

I see the hint under TCPIP_SERVICES, but no entry for TCPTRACE at the top level, just TCPIP_TRACE.

Re: TCPIPTRACE won't run

Jeffery D. Urmann — Wed, 06 Apr 2005 13:39:47 GMT

Just to further support Uwe`s theory regarding a stale help entry... I get the same help output as Aaron. Our OpenVMS v7.3-1 TCPv5.4eco4 system was an upgrade from OpenVMSv6.x, UCXv4.x as well.

Enjoy,

--Jeff

Re: TCPIPTRACE won't run

Jeffery D. Urmann — Wed, 06 Apr 2005 13:46:31 GMT

More support for Uwe...

I see all four of these help entries:

TCPIPTRACE
TCPIP_Services
TCPTRACE
TCP_IP_Services

Appearently, the upgrade process does not uninstall cleanly. Or I choose not to when/if asked. I do not recall as that was many, many years ago.

old VMS guy,

--Jeff