Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Many TCPIP$TNSnnn proc. and BG devices, can TCPIP$TELNETSYM_STREAMS be of help?

 
SOLVED
Go to solution
Jan van den Boogaard
Frequent Advisor

Many TCPIP$TNSnnn proc. and BG devices, can TCPIP$TELNETSYM_STREAMS be of help?

Hello all,
We have a 7.3-2 system with tcpip 5.4, 2 node cluster, which has many TCPIP$TNSnn processes and 700 BG devices hanging around. Could the logical TCPIP$TELNETSYM_STREAMS be useful here ? What experience do you have with this particular logical ? Why are all these BG devices staying for mounths and not deleted /disconnected automatically?

Thks, Jan
2 REPLIES
Karl Rohwedder
Honored Contributor

Re: Many TCPIP$TNSnnn proc. and BG devices, can TCPIP$TELNETSYM_STREAMS be of help?

Jan, do you have a corresponding number of queues?
The default of the STREAMS log. is 32, i.e. without it every symbiont process should treat 32 queues.
Have you read the app. chapter about TELNETSYM printing here:
http://h71000.www7.hp.com/doc/83final/6526/BA548_90006.PDF

regards Kalle
Volker Halle
Honored Contributor
Solution

Re: Many TCPIP$TNSnnn proc. and BG devices, can TCPIP$TELNETSYM_STREAMS be of help?

Jan,

you can use SHOW DEV/FULL BGxxx to find out, which process owns these BG devices. UCX SHOW DEV BGnnn shows which remote node is associated with this socket.

By default, TCPIP$TELNETSYM should disconnect the IP session to the printer at the end of the print-job. You can influence this behaviour with the TCPIP$TELNETSYM_IDLE_TIMEOUT logical.

Volker.