On 12/1/2023 9:26 AM, Scott Ballentine wrote:
(When upgrading, waiting isn't allowed, so we can only upgrade it if we are the only shared holder of the resource, otherwise the request fails.)
I just learned something here, Scott. I always assumed an upgrade would wait just the way an ordinary ENQ does. (Obviously, I never read the fine print... 😳 )
Any idea why this restriction exists? Were the original designers afraid -- because shared ENQ already held -- that it would lead to deadlock?
-- Phoenix Software International Edward E. Jaffe Chief Technology Officer 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ -------------------------------------------------------------------------------- This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
