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.
This requirements has been re-assessed. We have no plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server
Hans/Peter
Thanks for the information you have provided. I need to discuss your requirement with colleagues and will come back to you ASAP. However this may not be for a couple of weeks as I go on vacation tomorrow.
Regards
Andy
Hi Andy,
do you have read the comment from my Collgeue Hans?
best regards
Peter
Hi Andy,
our user transactions are running with a very broad variability. For example it makes a big difference if an end user runs an address selection with very specific data for name, surname and zip code rather than selecting all Muellers in Munich. So the broad variability in internal function comes with a great variability in terms of cpu usage and storage usage. We see the same transaction running with a storage footprint of 120K and at another point in time with 98M. And both of that is ok regarding the variability.
All of the storage upper limits of user transactions today may increase over time. But we are responsible for system stability and we do not want to permanently adapt upper limits to policies. Our aim is to give any transaction in our system the opportunity to use 50 percent of the EUDSA for example. And because our AORs are running with specific EUDSA limits as a result of workload separation a percentile storage policy would solve our challenge much better.
We know that we cannot eliminate SOS conditions with policies but if we discover a transaction causing DFHMP3001 or 3002 messages than we can start a discussion with our application developer and find out whether this behavior is now normal or has to be fixed.
Best regards Hans
Hi Peter
Thanks for your requirement against CICS policy support. However can you please give me a little more information on your requirement so that it can be correctly assessed.
CICS policy allows you to set thresholds on the amount of storage consumed by any one user task before taking some action is taken, e.g. outputting the DFHMP3001 message. In most cases we would expect policy threshold to be set based on the average amount of storage a task normally consumes, e.g. based on CICS monitoring data, and this average used to define policies to take action when rouge tasks run, e.g. define a policy to issue a warning msg when the amount of storage used by a task used greater than 1.5 time average, and another to abend a task which uses twice the average. In the general case the average storage consumed by a task will be independent of any value specified for the DSA limit and so allowing task thresholds to be set based on a percentage of a DSA limit does not sound like a good idea.
Your RFE says you want to set this threshold to 50% of the EDSA so I presume that when this task runs there is not much else running in the system and there is only ever one of these tasks running at any given time ? Or are you assuming that a storage policy monitors the storage consumed by ALL tasks in the system not individual tasks and are looking at using policy to issue an health alert that your system is in danger of going SOS ?
Regards
Andy