- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Locking Mechanism in VMS
Operating System - OpenVMS
1752794
Members
6580
Online
108789
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
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-23-2007 07:46 PM
тАО11-23-2007 07:46 PM
Re: Locking Mechanism in VMS
Attached is a log of three processes using resource XYZ, and the effects of the EXPEDITE and QUECVT flags. This was done using Ken Coar's LOCK utility.
Forcing all waiting to occur in the conversion queue by converting NL locks to more restrictive modes, and using the QUEQVT flag to force FIFO processing of the locks being converted achieves the behavior that ajaydec specified that he wants.
Hoff, I am interested in your comment that a $DEQ may not always be synchronous. Can you be more specific about the cause, and what conditions must be present for this to occur?
I have never heard of this problem before.
I can understand that it may be "cleaner" to always convert to NL before the $DEQ, but I am trying to figure out how the $ENQ CVT to NL before the $DEQ avoids the "nasty race condition".
Forcing all waiting to occur in the conversion queue by converting NL locks to more restrictive modes, and using the QUEQVT flag to force FIFO processing of the locks being converted achieves the behavior that ajaydec specified that he wants.
Hoff, I am interested in your comment that a $DEQ may not always be synchronous. Can you be more specific about the cause, and what conditions must be present for this to occur?
I have never heard of this problem before.
I can understand that it may be "cleaner" to always convert to NL before the $DEQ, but I am trying to figure out how the $ENQ CVT to NL before the $DEQ avoids the "nasty race condition".
it depends
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2007 09:59 AM
тАО11-24-2007 09:59 AM
Re: Locking Mechanism in VMS
>>> Hoff, I am interested in your comment that a $DEQ may not always be synchronous. Can you be more specific about the cause, and what conditions must be present for this to occur?<<<
$deq is effectively asynchronous due to how the underlying locking protocol is implemented. The $deq kicks off the processing, but there's no acknowledgment sequence for the completion of the $deq. If a $deq operation in a cluster is started and is followed by an $enq for the same resource, there might well be a collision with the $deq.
$enq down to NL is synch; there's an ack. Then the $deq doesn't matter, beyond releasing the resource if and as required.
I've posted an intro and some related details (including this wrinkle) at the web site:
http://64.223.189.234/node/492
$deq is effectively asynchronous due to how the underlying locking protocol is implemented. The $deq kicks off the processing, but there's no acknowledgment sequence for the completion of the $deq. If a $deq operation in a cluster is started and is followed by an $enq for the same resource, there might well be a collision with the $deq.
$enq down to NL is synch; there's an ack. Then the $deq doesn't matter, beyond releasing the resource if and as required.
I've posted an intro and some related details (including this wrinkle) at the web site:
http://64.223.189.234/node/492
Not applicable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-05-2008 11:40 PM
тАО02-05-2008 11:40 PM
Re: Locking Mechanism in VMS
regards,
ajaydec
ajaydec
- « Previous
-
- 1
- 2
- Next »
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