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

My ideas: DFSMS Disk Storage SW Support

Showing 10

IBM GTZ for EAV support should provide the dataset name when a module is found as being in error

Hello, When the tracker identify a program not EAV compliant for example for reason SMS-E:1 DADSM OBTAIN, the tracker should provide on which dataset name the problem was found This could allow to migrate one storage group to EAV if we found that ...
3 months ago in z/OS / DFSMS Disk Storage SW Support 1 Under review

Increase logical paths limit of 512 for Control Unit (HCD message CBDG085I)

We reached the limit of 512 paths for Control Units when disks are shared between multiple sysplexes. DASD volumes are being forced to be accessed by 3 and even 2 channel paths.
6 months ago in z/OS / DFSMS Disk Storage SW Support 3 Future consideration

In the LSPACE macro given the option switch off SVCDUMPs for VTOC errors

Change LSPACE to allow the option to suppress SVCDUMPs for VTOC errors
over 3 years ago in z/OS / DFSMS Disk Storage SW Support 3 Future consideration

Test Submission Disregard

Submitted By: SHARE-z/OS Systems Programming Submitted Date: 07/24/2024 Submitter Name: Slayte Admin USER Submitter Email: admin@slayte.com Description: Test Submission Disregard
5 months ago in z/OS / DFSMS Disk Storage SW Support 1 Not under consideration

Improve error reporting/LOGREC records associated with OBTAIN failure

We recently experienced an issue that involved VTOC corruption which required a ZAP to fix the VTOC. When the error occurred and was reported, there were messages and a LOGREC record that identified the volume involved, but there was no way to kno...
6 months ago in z/OS / DFSMS Disk Storage SW Support 0 Future consideration

ICKDSF utility to include VVDS creation as part of INIT

Why is it useful: VVDS automatically creating immediately upon INIT causing VVDS created with less size, avoid timing issue and avoid automatic VVDS size creation Who will benefit: all the customers use ICDSF INIT, VVDS avoid redefine with customi...
over 2 years ago in z/OS / DFSMS Disk Storage SW Support 2 Future consideration

LISTDATA VOLSPACE from PPRC Secondaries

The command LISTDATA VOLSPACE is not working for PPRC Secondaries located in Subchannel Set 1.We need to query SGCB information from PPRC Secondaries. This is not working:LISTDATA VOLSPACE DEVICE UNITNUMBER(7EA5) SUBCHSET(1) The parameter SUBCHSET...
about 3 years ago in z/OS / DFSMS Disk Storage SW Support 2 Future consideration

Fail allocation of DASD datasets with BLKSIZE/CISIZE > 32760

Allocation of disk dataset with a blocksize or VSAM CISIZE greater than 32760 should fail at allocation time, rather than at OPEN time.
over 7 years ago in z/OS / DFSMS Disk Storage SW Support 1 Future consideration

Additional information about the status of Cache Fast Write

Currently there is no easy way to be sure, that Cache Fast Write(CFW) is not used on your system. But in the event of an hyperswap CFW can be a problem. Therefore every customer should know their configuration. The problem is that the "DEVSERV P" ...
almost 2 years ago in z/OS / DFSMS Disk Storage SW Support 1 Future consideration

SDB not working as advertised

SDB not working as advertised as below from ISMF: HELP-------------------- SYSTEM DETERMINED BLOCKSIZE -------------------HELPCOMMAND ===> Use the SYSTEM DETERMINED BLOCKSIZE (SDB) field to specify that the system determined blocksize should be...
almost 6 years ago in z/OS / DFSMS Disk Storage SW Support 2 Future consideration

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.