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.
Should INGAMS refresh <policy DS Name> have a new "checkOnly" option - that does the check on each system but not the actual activation? --- Yes that was precisely the idea so that the change implementor doesnt go into the change window totally "cold".
Still later (during runtime) the script that is required maybe not available/accessible anymore --- yes that is possible in case something changes in between but at least the change implementor knows that it worked before and that way it will be easy to narrow down what changed that could have led to test failing. The change implementor can also run the "TEST" command again right before the change window to make sure everything is in order.
Hi. Thanks for this suggestion to enhance the policy processing. To clarify - the creation/change and build off a policy is done by the Customization dialog - that can run on any z/OS system and does not even has to be part of the same SAPlex you actually activate the policy with an INGAMS refresh. For this reason - we hardly can check the existence of referred REXX scripts already during editing/building the policy.
It might be possible to do the check by the agents on the systems during activation - and generate an error if REXX is not found. In this case - what should be the status? N of M (n<m) systems have the policy active? This is also not a really desirable situation. Should INGAMS refresh <policy DS Name> have a new "checkOnly" option - that does the check on each system but not the actual activation? Still later (during runtime) the script that is required maybe not available/accessible anymore....