IBM Z Hardware and Operating Systems Ideas Portal
This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Based on documentation:
RLS and TVS Recovery Guidelines Terri Menendez 02/28/2024
Part 5. Transactional Recovery
A. Retained Locks
Retained locks occur when active locks are held by recoverable subsystems (i.e. CICS or a TVS instance) for recoverable data sets (i.e. LOG(UNDO/ALL)) and one of the following occurs:
Recoverable data set is closed without ending all active transactions (i.e. cancel CICS).
SMSVSAM terminates with active locks.
System failure with active locks.
Backout fails (shunted) for one or more transactions holding active locks.
When a data set has retained locks, record management requests for the same record locks by RLS sharers will fail with RC=8 RPLERRCD=24(x’18’).
To determine which subsystem have retained locks issue:
SHCDS LISTSUBSYS(ALL)
SHCDS LISTSUBSYSDS(subsys)
SHCDS LISTDS(baseclustername)
SHCDS commands work both in batch and in the TSO/E foreground, but the output isn't available in SYSLOG.
Automation around SMSVSAM/RLS issues would be easier if we could drive standard z/os commands such as /D SHCDS xxx and have output go to SYSLOG.
my immediate comment is that you could add automation in your applications for the SHCDS message (IGW6xxx) from the SHCDS commands. However, like you said, "Running a batch job isn't very efficient when trying to automate based on messages." The main problem with SHCDS commands going to operlog is that they are generally voluminous and not suited for the console. Could you tell us what specific SHCDS command outputs you are looking for, so maybe we can come up with a more specific solution.