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.

Add a new idea Subscribe
Status Future consideration
Workspace z/OS
Categories DFSMS RMM
Created by Guest
Created on Mar 16, 2021

RELATED IDEAS

DFSMSrmm does not use UNIT specified in ISPF's ISPF Configuration Utility, but uses SYSALLDA specified in CLIST.

When I try to use the DFSMSrmm "G (Report Generation)" feature, SYS1.SEDGEXE1 (EDGRGREP) runs and userid.REPORT.LIB / userid.REPORT.JCL is allocated.
The allocation parameter in SYS1.SEDGEXE1 (EDGRGREP) specifies UNIT (SYSALLDA), so it will try to allocate to all storage volumes.


At that time, if a device group is defined in an Ethoteric environment, RMM may ignore the definition and access all device numbers everywhere.
My customers are in trouble because they may access volumes that the system does not want to use.

I think the problem with the system is that there is no place where SYSALLDA can be changed depending on the environment.

Normally, when a non-temporary dataset with a non-specific request is allocated on ISPF, user can change the "PDF_DEFAULT_UNIT" parameter from SYSALLDA (default) to UNITNAME in the ISPF configuration table to not use the intended VOLUME.

However, RMM does not use the PDF_DEFAULT_UNIT specified in this ISPF configuration table.

Could you please RMM be modified to use this ISPF configuration table setting as well?

Or could you make a place where you can modify the UNIT value used by rmm?

My customer has temporarily modified the UNIT specification in CLIST to work around this issue.
If it's ok to change the UNIT of CLIST, could you please state that in the manual?

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.