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).
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 item is not in our plans but is being kept in our backlog.
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 - USS
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 - General
Operating system - IBM z/OS
Source - None
Excellent idea. We have a separate PARMLIB data set where we put the BPXPRMxx members to be checked, but it is still a PARMLIB data set (ie, in the active PARMLIB concatenation). This causes audit, tracking and logistical control issues because we have to report on all PARMLIB changes... and when we have to iteratively do that just to syntax check a PARMLIB member, it's a discouragement to use the function. It's great that the function exists at all, but it would really be nice if one could specify a DSN= parameter on the command so that we could put the BPXPRMxx member(s) in a data set that is not part of the active (production!) PARMLIB concatenation.