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 Utilities
Created by Guest
Created on May 17, 2018

Misc reporting issues with dataset compression and encryption

This RFE is submitted to request corrective actions for the following dataset compression and encryption capabilities in z/OS 2.2 and above.
Misc issues:
a) There is no documentation for SMS.IND field in IEHLIST LISTVTOC output that describes a value of ‘N' means a dataset is encrypted (learned this from crypto council presentations). IBM will include in the z/OS 2.4 documentation when published.
b) SMS.IND cannot tell whether the compression method is zEDC or Generic, only the catalog interface can show this via ACT-DIC-TOKEN. The token value of x'6001….' Is only documented in presentations and the zEDC redbook.
c) When a VSAM dataset is created using a dataclass that specifies COMPACTION(ZP), our understanding is that we are requesting zEDC compression is preferred if the dataset is eligible. Since VSAM is not eligible we would prefer that the dataset not be compressed at all however AMS will use generic compression when the dataset is opened (ACT-DIC-TOKEN x'4000…'). We do not want software compression if COMPACTION=ZP and the file is VSAM.
d) DCOLLECT versus LISTCAT – in running a DCOLLECT we see cases where a compressed dataset has a field value for DCDCMTYP that indicates the dataset is not compressed whereas LISTCAT indicates (correctly) that it is. IBM indicates DCOLLECT is not reporting correctly and we should trust LISTCAT.

Idea priority High
  • Guest
    Reply
    |
    May 22, 2018

    p.s. the question on using listcat for reports was retorical if one should ask..

  • Guest
    Reply
    |
    May 22, 2018

    Issues with reporting on compression have turned up too many times. What should we do, use listcat on all datasets to report the total of compression we have gained?

    Small note: missing the exact description of the enhancement, but I get the idea..