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 ISPF
Created by Guest
Created on Aug 19, 2016

ISPF Allocation Functions should allow more xBYTE sizes

I have an open RFE to get additional size specifications in JCL and IDCAMS. This is to have ISPF Panels to provide the same size entries

Currently panels like 3.2 DataSet Utility allow for Bytes, KiloBytes and MegaBytes

I would like to see the addition for the following sizes
G or GB for Gigabyte
T or TB for Terabyte
P or PB for Petabyte
E for EB or EX or Exabyte
Z or ZB for Zettabye
Y or YB for Yottabyte

I would also like to see an enhancement to the ISPF HELP Panel on this information. As well as an additional Help Panel on how to determine how much storage is needed for a file. Most shops are using 3390 architecture. So it should be based on that.

In Option 3.4 I would like to see on the dataset list an '*' asterisk next to dataset not allocated in TRKS/CYL. When you use PF11 on the panel to view the summary data, when you get to the last one, you only see TRKS allocated. An '*' would give the user a chance to see that maybe the file was not allocated in TRKs/CYLs and to use I for more information.

The last part for ISPF 3.4 would be to allow the selection of seeing the file allocations in the dataset list in TRKs/CYLs/xB (MB, GB, TB, etc.)

Data set list options
Initial View
1 1. Volume
2. Space
3. Attrib
4. Total

Add a 5th option - Show Allocation In _B Where the user could enter
K M G T P E Y Z
If this option selected and nothing entered in the _B field, default should be Bytes

That way a manual calculation to cyls, or MB, GB, etc. could be avoided

Idea priority Low
  • Guest
    Reply
    |
    Mar 13, 2023

    What is the largest possible Z/OS dataset allocation at the moment? That's not easily answered. But assuming and Extended Format dataset with VOL=(,,,59) and 1TB empty volumes it's a Z/OS hard limit of ~59TB for a dataset. That is a long way from from a PB through to YB! Good to future proof though if feasible.
    It would be useful for ISPF 3.4 to show an option KB, MB, GB etc value as opposed to just Total TRKS though.

  • Guest
    Reply
    |
    Aug 20, 2016

    Creating a new RFE based on Community RFE #93348 in product z/OS.