Rexx LOCK command missing timeout for blocking waits

Rexx LOCK command: unspecified wait duration when NOWAIT omitted

0 reputation · 06 Apr 2020, 15:50 UTC

15.1K views0

Background

The Rexx LOCK command can secure an entire file or a specific region. When the NOWAIT option is omitted, the calling program suspends until the lock is granted, which can delay backup or restore operations.

Uncertainty

Documentation does not specify a timeout or retry policy for blocking locks, leaving the duration of suspension ambiguous. Implementations may differ across Rexx versions or platforms, and no standard mechanism exists to configure a maximum wait time.

Questions

What is the expected wait duration when LOCK is issued without NOWAIT?
Should restore scripts rely on NOWAIT to avoid indefinite blocking?
Is there a platform‑specific timeout that can be configured or queried?

2,823 following

Keep exploring this topic

REXX EXIT statement exit‑code propagation inconsistency after schema change rollback

REXX EXIT statement exit‑code propagation varies across interpreters, creating uncertainty for rollback verification after schema changes.

REXX SIGNAL ON ERROR Deployment Log Triage Failure Policy

REXX SIGNAL ON ERROR deployment-log triage: abort on first trapped error or continue for a complete failure summary?

Db2 LUW Upgrade Recovery State Consistency

Confirming Db2 LUW state consistency after an upgrade failure requires verifying pre-upgrade backup integrity against documented recovery prerequisites.

Identity-map reads vs. explicit expire/refresh when verifying externally restored rows in SQLAlchemy ORM

When verifying externally restored rows in SQLAlchemy, should you trust identity-map reads or force expire/refresh? Explore the trade-offs for post-backup data verification.

Rexx LOCK command: unspecified wait duration when NOWAIT omitted

Background

Uncertainty

Questions

0 answers

Your perspective belongs here.

0 question comments