IBM Z Hardware and Operating Systems Ideas Portal
This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.
ICBC have a big pain point that they open a PMR to IBM, IBM L2 always ask different diagnostic data for the PMR. They are required to recreate the problem, collect different diagnostic data and send them to IBM again and again. It is really time consuming and energy-consuming. For example, DB2 PMR need DB2 trace, SMF data, accounting report and so on. z/OS RMF PMR need RMF report and so on. ICBC expects each z/OS product and component can have some FFDC (First Failure Data Collection) guideline for what data are needed for which type of problem.
The guideline should be something like this, for example:
For DB2 problem type 1, diagnostic data requires: dump, DB2 trace, OperLog…
For DB2 problem type 2, diagnostic data requires: dump, SMF data, DB2 trace…
This kind of guideline is what the "Standardizing diagnostic data collection process" means.
ICBC expect most z/OS important components and products can have above guide for what diagnostic data needed be collected for which type of problem. And then, make the guideline automated, so that the diagnostic data can be collected automatically when problem happens.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS
Component - z/OSMF
Operating system - IBM z/OS
Source - None
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS
Component - BCP_Service Aids
Operating system - IBM z/OS
Source - None
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS
Component - BCP_Service Aids
Operating system - IBM z/OS
Source - None
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS
Component - BCP_General
Operating system - IBM z/OS
Source - None