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.
ADRDSSU dump is not possible for DASDs with multiple OS MiniDisks. Our customers have separated some DASDs into many smaller z/VM MiniDisks for use by his z/VSE. But same problem could occur for other products under z/VM, that create OS-Disks. Problem rises if the OS MiniDisk starts on cylinder 0 of the DASD.
- When I use DUMP TRACKS with the CPVOLUME keyword, dss says "UNABLE TO OPEN VOLUME", because the volume is not VM-formatted, it contains an OS- VTOC from VSE.
- When I omit the CPVOLUME keyword, I cannot dump the full volume in one step, because the dump looks into the VTOC and sees only the first cylinders of the first VM-MiniDisk.
On some volumes our customer has created many MiniDisks and I don't know the size and location.
Another ADRDSSU DUMP problem, which could be solved at the same time, is that I need to know which type of disk I have to dump, before I start the dump job, because the usage of the CPVOLUME parameter is depending on the type of the volume. But I don't know if the volume contains CP-volumes or OS-disks, when I put the dump-JCL together. So currently I have to check cylinder 0 of hundreds of disks, before I can choose the correct dump parameters.
Therefore a parameter would be nice to make a full-volume dump disregarding the type of volume, if there's an OS-disk on cylinder 0 or not.
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.
Attachment (Description): ADRDSSU DUMP TRACKS log