- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Many TCPIP$TNSnnn proc. and BG devices, can TC...
Operating System - OpenVMS
1752590
Members
3767
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-11-2006 08:27 PM
тАО11-11-2006 08:27 PM
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
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
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-11-2006 09:41 PM
тАО11-11-2006 09:41 PM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2006 02:26 AM
тАО11-12-2006 02:26 AM
Solution
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP