IBM Z Software
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).
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.
I agree, contextual testing in view is a waste of resources.
So long as the script still gets checked for correctness at some point, then we've no problems with removing contextual checking in VIEW mode, but we don't want to find out later when we execute the script, that it's in any way incorrect, as that would then be too late.
It's unnecessary to run a check if VIEW is selected. (Prio: medium)
Perhaps in view mode it could be possible to start validation on demand. The validation now can build up messages in the logging that might not be of interest during the view.
We also agree that viewing a script should not cause execution of contextual checking.
Priority: Medium
I'd need more clarity on what is being requested here. My understanding is that the suggestion is to remove the view option and simply allow clients to go into the script and then exit out if they chose not to execute it. I would still want to be able to view a script without the risk of inadvertently triggering it. Longer-term, the Planned Actions panel will also come under the Role based security as per the Standard Actions panel and I would like the ability for a BAU use to view the script, but not be able to access it. Perhaps this will be solved by Pzon!
I agree too! It's only a waste of time. Confirmation is needed instead in case of execution of the script.
I agree! Viewing scripts does not allow execution, so contextual checking is a waste of time and resource. For example, in aa MGM4SITE configuration where the recovery site is kept at low capacity, this slows the checking process and wastes resources that could be used by more important status maintenance tasks.
While not highest priority, on the border between medium and high.