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 is available with zTPF APAR PJ46362.
It would be helpful to the TPF lab if you could follow this template when creating new RFEs. If possible, would you please add some of this information to this RFE before it is hardened in the system within the next 24 hours? Thank you.
Description:
1) Describe the problem that needs to be solved in extensive detail as this is the most important aspect of any RFE (not the proposed solution). Who is the user affected and how? What are the use cases, systems, components affected and how? What are the circumstances or context around this situation? Consider including a user story statement to help convey the problem and value: A can , so that .
For example,
An application developer can measure and analyze resource usage of application changes so that we can minimize the system resource usage as the application changes over time.
Our application developers largely modify existing applications. Over time, applications use more and more system resources which can have a variety of impacts such as a requiring additional hardware, impacting system performance, etc. Our developers are unable to see the impacts of their code changes as they are making their updates during development. Often large impacts are found by QA during performance testing. This is very late in the process and is much more expensive and time consuming to rework the code. Ideally, we want to have developers perform ongoing tests and comparisons to baselines so that they understand and can mitigate the impacts of their changes as appropriate. This will reduce rework time by finding the problem sooner rather than catching the resource usage problems in performance tests run by QA.
2) Describe acceptance criteria for any given solution such as: the expected inputs, outputs, behavior, etc. What are the critical behaviors for any solution to be acceptable? Consider using Behavior Driven Design GIVEN, WHEN, THEN type statements to describe the desired behavior.
For example,
GIVEN that an application developer makes a code update to an existing application
WHEN they test the updated application's resource usage
THEN they can compare the resources used by the application to baseline (prior to their code changes)
AND see changes in the CPU usage, ECB Existence time, FINDs, and FILEs for the application.
3) If you have ideas for a solution, provide them last.
For example, re-invent the performance analyzer in TPF Toolkit with comparison tables and such.
Use Case:
Describe the features the user, system, etc would interact with any acceptable solution.
For example,
Facilitate collection of baseline and modified application runs.
Comparisons between the runs.
Analysis of the most heavily used functions by time, FINDs, FILEs, and number of calls.
Business justification:
Describe why the problem should be solved such as the value or benefit to your business, customers, staff, etc.
Also describe any hard deadlines and the driver of those deadlines such as legal requirements, security audits, etc business mandates. Please clarify the dates required for the deliverable, betas for testing, etc.
For example, by leveraging a performance analyzer during application development we can minimize the system resource usage as the application changes over time and save time/money by finding performance issues earlier in the development process.
We have a mandate from our business that this form of measurement must be in place by EOY 2020. As such, we need start beta testing in August 2020 with delivery by the end of November 2020 to meet our mandate.