HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

UCX sho communication

 
SOLVED
Go to solution
Lokesh_2
Esteemed Contributor

UCX sho communication

Hi,

The question got raised from latest William thread about TCPIP services. On one of my machine running UCX V4.2 ,I get the following information:
*****************************************

$ ucx sho version

DIGITAL TCP/IP Services for OpenVMS VAX Version V4.2 - ECO 1
on a VAX 6000-540 running OpenVMS V7.1

$ ucx sho comm

Communication Parameters

Local host: BRSIS8 Domain: bro.cpqcorp.net

Cluster timer: 5
Maximum Current Peak
Interfaces 20 3 3
Device_sockets 300 47 95
Routes 65535 3 3
Services 200 11 31
Proxies 20

Type: Ethernet Free Maximum Max Bytes Minimum Min Bytes
Large buffers 20 200 377600 10 18880
Small buffers 150 1000 256000 50 12800
IRPs 20 200
Non UCX buffers 10

Remote Terminal
Large buffers: 10
UCBs: 4
Virtual term: disabled
$

****************************************

Whereas on maching running TCPIP V5.3 , I get the following information:

*****************************************$ ucx sho version

DIGITAL TCP/IP Services for OpenVMS VAX Version V4.2 - ECO 1
on a VAX 6000-540 running OpenVMS V7.1

$ ucx sho comm

Communication Parameters

Local host: BRSIS8 Domain: bro.cpqcorp.net

Cluster timer: 5
Maximum Current Peak
Interfaces 20 3 3
Device_sockets 300 47 95
Routes 65535 3 3
Services 200 11 31
Proxies 20

Type: Ethernet Free Maximum Max Bytes Minimum Min Bytes
Large buffers 20 200 377600 10 18880
Small buffers 150 1000 256000 50 12800
IRPs 20 200
Non UCX buffers 10

Remote Terminal
Large buffers: 10
UCBs: 4
Virtual term: disabled
$
******************************************

So, where is the remaining information (like maximum device sockets..etc ) in newer version ????


Thanks & regards,
Lokesh
What would you do with your life if you knew you could not fail?
6 REPLIES
Lokesh_2
Esteemed Contributor

Re: UCX sho communication

oops, sorry...on newere version, I get the following information...

***************************************

TCPIP> sho version

Compaq TCP/IP Services for OpenVMS Alpha Version V5.3
on a AlphaServer 2100 4/275 running OpenVMS V7.3-1

TCPIP> sho comm

Communication Parameters

Local host: dgsvms Domain: digitalindiasw.net

Maximum Current Peak
Proxies 20


Remote Terminal
Large buffers: 0
UCBs: 0
Virtual term: disabled
TCPIP>

**************************************

Excuse me,
Lokesh
What would you do with your life if you knew you could not fail?
Willem Grooters
Honored Contributor

Re: UCX sho communication

Eaxctly.
The major point: TCPIP has been a port from TRU64 (right?) whereas UCX has been a 'native' VMS set. That could explain the difference - not justify.
As Lokesh pointed out, my customer may run into a maximum - but there seems to be no way to locate this.....Not by TCPIP-tools anyway.
Lokesh: trying to say "Give us our info back!"? I double that!
Willem Grooters
OpenVMS Developer & System Manager
labadie_1
Honored Contributor

Re: UCX sho communication

Hello

>>>So, where is the remaining >>>information (like maximum device >>>sockets..etc ) in newer version ????

$ ana/sys
tcpip sh netcb/stat

Regards

Gerard
labadie_1
Honored Contributor
Solution

Re: UCX sho communication

sorry, there is a typo, you should read

$ ana/sys
tcpip sh inetcb/stat
Antoniov.
Honored Contributor

Re: UCX sho communication

Hi Lokesh,
TCPIP V5 is very different from UCX V4; now the TCP/IP kernel is like unix with a VMS interface; after you type @SYS$MANAGER:TCPIP$DEFINE_COMMANDS
you can type some unix command as ping, netstat, arp, etc.
So you could find same information as UCX V4.
To solve your problem, I think, you could see memory buffer typing
$TCPIP SH COMM/MEM
The configuration & kernel parameter are visible by sysconfig command; for example ypu can type
$sysconfig -q inet
or
$sysconfig -q socket
(both comand after TCPIP$DEFINE_COMMAND)
For furhermore information read TCP/IP documentation at
http://h71000.www7.hp.com/doc/tcpip.html

H.T.H.
Antoniov
Antonio Maria Vigliotti
Mike Naime
Honored Contributor

Re: UCX sho communication


Try :

TCPIP SHO SERVICE TELNET /FULL

Look at the value of LIMIT:

This is a value for TELNET connections only, not for all TCPIP.
VMS SAN mechanic