Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Locks on DASDs and external DASD utilities: relax read access locking. #355

Closed
marcoxa opened this issue Jan 2, 2021 · 2 comments
Closed
Assignees
Labels
BUG The issue describes likely incorrect product functionality that likely needs corrected.

Comments

@marcoxa
Copy link

marcoxa commented Jan 2, 2021

Hi

Hercules locks the DASDs listed in its configuration file with both a write and a read lock. The write lock is justified. The read lock could (I am arguing "should") be relaxed.

In this way, some of the external utilities could still work while Hercules is running (e.g., DASDLS).

Thanks

Marco

@mcisho
Copy link
Contributor

mcisho commented Jan 2, 2021

This is a Windows problem, dasdls works fine while Hercules is running on Fedora Linux.

Ian

Fish-Git added a commit that referenced this issue Jan 3, 2021
Resolves GitHub Issue #355.

NOTE: commit also includes a fix to prevent a new shadow file from being erroneously created when the batch utility is only requesting read-only access to existing shadow files.
@Fish-Git
Copy link
Member

Fish-Git commented Jan 3, 2021

Fixed by commit cee323b.

Closing.

@Fish-Git Fish-Git closed this as completed Jan 3, 2021
@Fish-Git Fish-Git added the BUG The issue describes likely incorrect product functionality that likely needs corrected. label Jan 3, 2021
@Fish-Git Fish-Git self-assigned this Jan 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG The issue describes likely incorrect product functionality that likely needs corrected.
Projects
None yet
Development

No branches or pull requests

3 participants