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 SMP/E
Created by Guest
Created on Sep 27, 2021

Change space units for GIMUNZIP new allocation

After installing z/OS V2R5 via z/OSMF ServerPac PSI, the target and distribution non-VSAM data sets (PDS and PDSE) were allocated by "bytes" unit instead of traditional "tracks" or "cylinders", which made it difficult to measure the size of data sets.

For example, ISPF OPT3.4 "Data Set Information" panel displays the following very large values for SYS1.LINKLIB data set.

1st extent bytes . : 233029632
Secondary bytes . . : 854016
Current Allocation
Allocated bytes . . : 246,300,672
Current Utilization
Used bytes . . . . : 197,197,824

The space units used by GIMUNZIP when allocating a new data set should be changed from "bytes" to "tracks" or "cylinders". In other words, the same units as the original data set that was archived by GIMZIP should be used if it's "tracks" or "cylinders".

Idea priority High
  • Guest
    Reply
    |
    Oct 8, 2024

    I believe the allocation of data sets used by zOSMF should still use tracks/cylinders since volumes still use tracks/cylinders when created on DS8xxx disk subsystems.

  • Guest
    Reply
    |
    Oct 8, 2024

    This is something that was not identified previous to the install via z/OSMF, and actually puts you into an issue where if you need to enlarge the datasets (which happens frequently upon maintenance application) using ISPF 3.2, that some datasets are so large that they can't be increased without changing to tracks or cylinders. It's not difficult to fix, but should not have been made bytes, since the installation asks for tracks during hte system install, it should be left as tracks or cylinders.