Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Locking Mechanism in VMS
Operating System - OpenVMS
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
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
- Email to a Friend
- 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
- Email to a Friend
- 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
- Email to a Friend
- 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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP