- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- disconnect Decnet Links
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО02-03-2009 07:02 AM
тАО02-03-2009 07:02 AM
disconnect Decnet Links
We have a configuration where one node makes decnet links to other node to upload some data, what happens after sometime the links on the server node gets accumulated and no more links could be made to server
ANALYSIS
=========
on server
$mc ncp sho link XXX chara
State = closed
PID = 000020D8
Remote node = 1.8 (NodeB)
Delay time = 4
Remote link = 8577
Remote user = TAPESYS
Username = TAPESYS
Process name = TAPMGRRQ
then I tried disconnecting this link also but no luck.....
do anyone knows about some method to kill this link forcefully ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2009 07:14 AM
тАО02-03-2009 07:14 AM
Re: disconnect Decnet Links
You could stop this process
Oswald
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2009 08:01 AM
тАО02-03-2009 08:01 AM
Re: disconnect Decnet Links
%SYSTEM-W-NONEXPR, nonexistent process
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2009 08:21 AM
тАО02-03-2009 08:21 AM
Re: disconnect Decnet Links
Where did that PID come from? It's not in your original post.
Are you sure that a process with PID 000020D8 does not exist on node "NodeB". Since that node is not in a cluster you must be logged in to "NodeB" to do the STOP/ID=000020D8 command.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2009 08:33 AM
тАО02-03-2009 08:33 AM
Re: disconnect Decnet Links
There's an old-time link state bug that can arise here if this is a V6.x multiprocessor, and if this is that bug, that bug was fixed via ECO. If you're not current on OpenVMS and DECnet (and TAPESYS?) ECO kits, do get there.
Otherwise, consider contacting whomever is maintaining the (TAPESYS?) code here. It looks like the package is busted. The link is not being closed correctly.
That PID looks to be an internal PID, or bogus. (Most recent PIDs I've seen have bits set in the upper word in recent releases.) See if you have a TAPESYS process around that matches the external PID in the low word or so. If this is V7.1 or later, /pipe show system /full | sear sys$pipe tapesys/ should get you close, or ANALYZE /SYSTEM and then SHOW PROCESS /INDEX=000020D8
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2009 09:07 AM
тАО02-03-2009 09:07 AM
Re: disconnect Decnet Links
Oswald
there are many links around 28 and I tried to $ stop /id= to the different then that I posted in my query
Thanks for replying ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2009 01:14 AM
тАО02-04-2009 01:14 AM
Re: disconnect Decnet Links
"there are many links around 28 and I tried to $ stop /id= to the different then that I posted in my query"
I am not sure what you mean by this. Did you manage to stop the offending process? And did the DECnet link disappear?
Oswald
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2009 05:41 AM
тАО02-04-2009 05:41 AM
Re: disconnect Decnet Links
On little evidence, I'd tend to assume this is a bug that's been resolved in a more recent OpenVMS version or in a DECnet upgrade or (most likely) in an upgrade of or ECO for the TAPESYS? package involved here. This case is involving an ancient OpenVMS Alpha version, and that implies the rest of the configuration is equally old and crufty. And buggy.
The processes that need to be restarted are probably the tape manager client and tape manager server; one or more of the core TAPESYS? pieces. Or reboot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2010 06:36 AM
тАО02-08-2010 06:36 AM
Re: disconnect Decnet Links
Could you please let me know the ECO kit.
VMS Version "OVMS 7.2-1" with "Decnet Phase IV" is being used in my scenrio.