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
For our Ansible-based deployment solution, we use the zos_copy module from the ibm_zos_core collection (version 1.8.0).
We note the absence of ISPF statistics on our PDS and this is particularly penalizing for our PARMLIBs.
The objective of this proposal is to improve the ZOAU dcp utility to continue having the ISPF (Size, Created, Changed, ID) statistics when using the zos_copy module / ibm_zos_core collection.
Idea priority | Medium |
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.
Agree
Agree
Wholeheartedly agree! We also are developing DevOps pipelines and retaining/maintaining member statistics is critical to the acceptance of new DevOps functions.
We are tyring to use DevOps Pipelines and ran into the same issue.
We are using ibm_zos_core collection to copy the components as part of our deployment process. It's really bad that we don't have these ISPF statistics and it's tough for us to track who changed what and when. If this can be fast tracked it will be very useful in our journey.