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 Not under consideration
Workspace z/OS
Categories BCP_Service Aids
Created by Guest
Created on Oct 12, 2023

Make DAE - ADYSET00 possible to supress SYSUDUMP the same way as SYSMDUMP can be supressed today.

When we get problems in our Environment with a lot of SYSUDUMPs produced and filling up our SPOOL volumes. Then we would like to have the possibility that DAE - ADYSET00 can supress all our SYSUDUMP's. This can avoid that all our spool volumes to became full.
All customers can benefit from this.
We like the implementation to be the same way as SYSMDUMP can be supressed today.  
SYSMDUMP(MATCH,SUPPRESSALL,UPDATE)

Like this:
SYS1.PARMLIB(ADYSET00)
SYSUDUMP(MATCH,SUPPRESSALL,UPDATE)  

Idea priority Medium
  • Guest
    Reply
    |
    Jan 31, 2024
    This item is unlikely to be given high enough priority to be placed into the product plan.
    For immediate relief, IBM recommends using the JES2 support of the compression of SYSOUT data sets via a keyword on the OUTCLASS statement within JES2. An installation can set up a particular SYSOUT class that does compression, and users would change their JCL to use that provided SYSOUT class or change the existing class to support compression. Additional information can be found here: https://www.ibm.com/docs/en/zos/3.1.0?topic=characteristics-format-description-outclassv
    To address the continually increasing diagnostic data volume, IBM recommends using the SYSMDUMP 'interface'. The unformatted data collected by a SYSMDUMP is far smaller (also faster) than the formatted dump outputs. While this must be combined with developing expertise in using IPCS for problem diagnosis; it greatly reduces the volume of data that the system generates at the time of the error.
    A separate option is to convert the JCL used to generate the SYSUDUMP/SYSABEND dumps to use data sets instead of a SYSOUT class. We do appreciate that since the data volume is unknown, pre-allocating the data set with a sufficient size could be problematic. With some system planning, it should be possible for SMS allocations with ACS routines to target volumes where the data is compressed, minimizing the impact to DASD utilization.