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 DFSMS SMS
Created by Guest
Created on Apr 6, 2021

DFSMS ACS &MAXSIZE for Extended Format datasets

The value for the variable &MAXSIZE in DFSMSdfp Automatic Class Selection for NON-VSAM datasets is always calculated as 1 x Primary + 15 x Secondary, + Directory if applicable.

In the case of &DSNTYPE being EXC, EXR or LIBRARY this value should be calculated based on 1 x Primary + 122 x Secondary to properly reflect their potential maximum values as already happens with VSAM. Extended Format has been around for a long time.

Also, the &NVOL value should ideally be used as part of the calculation as happens with VSAM. And the DYNVOL count in DATACLAS should be passed as an &NVOL value if not overridden in the JCL, TSO or IDCAMS statements.

Both &DSNTYPE and &NVOL can have a dramatic effect on &MAXSIZE, up to 8 x for Secondary space per volume, and that number multiplied by the volume count. So even for a 1,1TRK dataset that is a potential 51MB vs 388MB or ~87% difference.

This limits the ability to accurately decide how to manage NONVSAM datasets based on size without getting in to some convoluted and non future proofed type coding in the ACS routines using &DSNTYPE, &SECOND_QTY, &SPACE_TYPE and/or possibly &DATACLAS, if their names indicate size and dsntype.

Idea priority Medium
  • Guest
    Reply
    |
    Apr 7, 2021

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - DFSMS SMS
    Operating system - IBM z/OS
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - DFSMS CVAF/DADSM
    Operating system - IBM z/OS
    Source - None