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.
See this idea on ideas.ibm.com
Hi,
We found that while copying load modules from one PDS to another, IBM uses a standard temporary dataset format which is against our shop SMS rules. We found that there isn't a way to override the second and third nodes to confirm with inhouse SMS standards.
I'm proposing that we get an option to configure the temporary datasets used by IDz so that we can get things to work in accordance to the SMS standards set up already.
Thanks
Prasanna V Balasubramanian
Idea priority | Urgent |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Thank you for taking the time to suggest an enhancement to our product. Many of our product enhancements result from feedback from our customers, so your input is always very important to us.
The development team has a few comments to clarify before we can make a decision for this idea:
The full second qualifier can be customized by a new RSE host env.
The third qualifier can be partially customized using a prefix specified by a new RSE host env. The trailing 0000000<n> is still required for the required test to guarantee they are unique to be used (to avoid naming collision).
To maintain the temp file name uniqueness on the third qualifier, it can be customized either fully with the existing qualifier I000000<n> to be turned into the fourth qualifier, or partially customized as a short prefix with the appendix of <nnnn> equivalently with the existing qualifier of I000000<n>. There will be two temp datasets (for SYSIN and SYSPRINT correspondingly) relevant in this change.
Is this aligned with your original idea suggestion?