topic Re: problem with multinet re-using port # in Operating System - OpenVMS

problem with multinet re-using port #

juanita_3 — Wed, 05 May 2004 16:16:09 GMT

Hi,

Having a problem with vms/multinet re-using port #.

Port # used is in 6000 range and when port needs to be reused stop/id is done on process using that port but process doesn't release port and the process still shows up as ? Does something else need to be done so another process can have access to that port # soon after the process is killed?

thanks,

Re: problem with multinet re-using port #

Willem Grooters — Wed, 05 May 2004 16:29:24 GMT

What VMS version is used?

If this process is started as a service, disabling and enabling the port might help.
Better solution:

$ TCPIP DISABLE SERVICE /PORT=#
$ STOP/ID=
$ TCPIP ENABLE SERVICE /PORT=#

HTH

Willem

Re: problem with multinet re-using port #

juanita_3 — Wed, 05 May 2004 17:05:29 GMT

vms 7.3-1.
would that work for multinet also?

thank you

Re: problem with multinet re-using port #

Brian Reiter — Thu, 06 May 2004 05:09:48 GMT

Perhaps try using STOP/IMAGE/ID=xxxx

This invokes the $FORCEX system service. Could mean that some tidying up is done on exit.

Re: problem with multinet re-using port #

Cass Witkowski — Fri, 07 May 2004 17:35:26 GMT

If you do a $MU SHOW/CONN=ALL does your port show up in the local side? Is the local address an * or an IP address. If it is an * then there is a listener for that port. It may be a process or it may be multinet. If there an address in the remote column then there is an actual TCPIP connection.

To find out if a process has the port open do the following:

$ Define MU$SDA MULTINET:MULTINET$SDA.EXE
$ SET TERM/WID=132
$ ANALYZE/SYSTEM
$ MU SHOW CONNECTION

Look through output for your port. Then look to right about 3/4 of the way on the line for the device. It should be an INETxxx device or BGxxxx. Do a SHOW DEVICE of this device to see who the owner is

Multinet also has the ability to listen for connection request on a port and then create a detatched process to service that connection. This has advantages that you don't have to write the listener code just the service code. It also reserves the port so some process can use it before your listener server could start. To see if this is the case do:
$ MULTINET CONFIG/SERVER
server-config> SHOW * /FULL

Search the output for your port.

You can disable the service.

server-config> DISABLE xxx
server-config> RESTART