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 Functionality already exists
Workspace z/OS
Categories DFSMS DSS
Created by Guest
Created on Feb 29, 2024

Currently there's no check in the COPY command for ADRDSSU to see if the data sets are the RACF databases or not

Hi - 

Sometime ago, there was a problem when the data sets which contains the RACF primary and backup databases were moved using ADRDSSU. The data sets were protected as recommended by the books as well as they were assigned the PSU attribute. However, the operands used in the COPY allowed the program to bypass this condition and the person, who knew they shouldn't be moved that way, had the proper access to. The conclusion is that the data sets were moved from one disk to another, and it wasn't done using the "rvary dance" therefore the RACF was impacted when trying to read/open its databases. 

I would like to suggest evaluating the idea of not allowing the databases to be moved whether by enhancing the COPY operands within a way to check the databases are getting included or their conditions are somehow being bypassed or else from the data set or the RACF perspective. 

Thanks much,

Lucas Rebecca.

Idea priority Medium
  • Guest
    Reply
    |
    May 16, 2024
    Thank you for submitting your idea. As the description identified, The user in this case had the authority and specified the correct combination of keywords to allow the data set to be moved (PSU). If the location was different on the target volume than the source volume, the user had to specify the FORCE keyword. Setting the FORCE keyword is telling DFSMSdss that the caller understands the implications.

    Currently, the user can use a combination of INCLUDE/EXCLUDE criteria to ensure no RACF data sets are processed - as long as the site's naming convention allows for it.

    As far as new support to identify such data sets would be unlikely to be given high enough priority to be placed into the product plan. To do so would likely require non-DFSMSdss support to identify these RACF data sets. If the existing support is not suficient and you feel that this requirement is still needed, please resubmit or create a new updated request.
    1 reply
  • Guest
    Reply
    |
    Mar 1, 2024

    That's a similar issue with datasets in the JES2 procedure concatenation, and NONSMS managed APF libraries that are volume specific. The problem is the dataset names are site specific so there'd need to be a way to identify them and add the extra protection with a common DFDSS keyword or RACF profile.