- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- locked tape device
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
тАО05-09-2008 03:18 AM
тАО05-09-2008 03:18 AM
locked tape device
We stop deviceshare, (incl remove it with install delete) but when we start again, the drive is locked again.
I will attach some screenprints.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-09-2008 03:45 AM
тАО05-09-2008 03:45 AM
Re: locked tape device
Welcome to the Vms forum !
You have not stated the architecture (Vax, Alpha, Itanium), the Vms version (i.e 6.2, 7.3-2, 8.3 ...), the patches applied ($ prod sh prod, prod sh hist, dir/dat/siz sys$help:*.rel*), if you are in a Cluster (is this tape drive owned by a process on another member of the Cluster) ?
Do you have a process in the state Rwast ?
Have you tried to power-cycle the tape ?
What is the value oh the sysgen parameter mvtimeout ?
$ mc sysgen sh mvtimeout
If your process is in Rwast state, have a look at
http://www.pottsoft.com/home/vms/rwast.html
A reboot will solve the problem, but I guess you are trying to avoid it :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-09-2008 04:11 AM
тАО05-09-2008 04:11 AM
Re: locked tape device
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-09-2008 04:16 AM
тАО05-09-2008 04:16 AM
Re: locked tape device
$ set term/wid=132
$ prod sh hist
will show your patches level.
By the way, if you upgrade to 7.3-2, you will be supported, as 7.3 is no longer supported.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-09-2008 04:25 AM
тАО05-09-2008 04:25 AM
Re: locked tape device
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-09-2008 05:23 AM
тАО05-09-2008 05:23 AM
Re: locked tape device
http://www.advsyscon.com/products/deviceshare/
Have you contacted Advanced Systems Concepts, Inc.?
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-09-2008 05:54 AM
тАО05-09-2008 05:54 AM
Re: locked tape device
There's an old CSCPAT tool CSCPAT_0245_USE_WITH_CAUTION_MTDISMOUNT.EXE
See the thread "deleting a non-existent process".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-09-2008 10:40 AM
тАО05-09-2008 10:40 AM
Re: locked tape device
This case was a very common error in older releases, and is rather more rarely seen on current releases.
Rebooting will be the fastest way to clear this.
As for upgrading to V7.3-2, I'd encourage upgrading all the way to V8.3; to the most current release. V7.3-2 is itself getting very old, and it's clear that your site has a history of staying on a particular release for a long time. Accordingly, getting as close to current when your site does upgrade is my recommendation.
As for the usual concerns around upgrading here, for all intents and purposes, the V8.* releases are not a major upgrade on OpenVMS Alpha, as compared to V7.3-2 and prior.
You might have a shot of fixing this case in situ with ECOs, as various releases saw ECOs for related issues.
The other common trigger is the use of SHARE privilege to share a device, and accompanied with an out-of-order device deallocation.
If you do decide to reboot to clear this case, this can be an opportunity to apply the current ECOs for V7.3, too.
The tool I mentioned in that other cited reply basically bombs the device ownership field. It's a work-around for various of the underlying dangling ownership issues in the older releases. That'll take ECOs or an upgrade.