This portal is to open public enhancement requests against IBM Z Software products. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Like others have mentioned, we have had to write message automation rules around this to not trigger a false alarm.
Good idea, we had to write automation rules to deal with this situation, but what we ended up with was a compromise. It would be useful if we could differentiate between a CGPAUSE initiated by LCP and one initiated by something else.
Perhaps a different warning message acknowledging the understanding that an LCP capture is ongoing would be acceptable rather than an error message. Medium priority.
We like the idea in order to avoid false alarm.
Medium priority.
Does not apply to Worldpay
Agree with this to avoid false alarm - medium priority
Agreed. We have had to write complicated automation rules to try and prevent incidents and callouts from being generated when GM is paused for an LCP capture - though there needs to be some timeout or other that doesn't leave the alerting disabled indefinitely if LCP should become 'stuck'.
n/a by us, but we also "auto-ticket" on events, so be careful when implementing/changing something
This is important for American Express as we auto-ticket on events like these. It would avoid churn and false positives.