Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Future consideration
Workspace z/OS
Categories DFSMS DSS
Created by Guest
Created on Apr 12, 2017

PRESERVE OWNERid during COPY/DUMP/RESTORE DFDSS

If a dataset is logically copied/dumped or restored by DFDSS the OWNERID field in the Catalog is reset to NULL. The Customer wants to preserve the previous content of the OWNERID field during DFDSS Copy/Restore because customer uses a function in Z/OS that needs this information.

Idea priority High
  • Guest
    Reply
    |
    May 9, 2018

    I would like to ask what you think if DFSMSdss behaved in the following way: If the ADMIN keyword is specified then preserve the owner ID. If the ADMIN keyword is not specified, but the data set is not being renamed then we would also preserve the owner ID, otherwise either NULL it out or take the userID that submitted the job. The reason for the extra condition is because typically we think of a COPY or RESTORE to a new name as an introduction of a new data set into the system and we might want to handle that case differently. Please let me know what you think. Thank you!