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 Under review
Workspace z/OS
Created by Guest
Created on Jul 23, 2024

Describe the catalog mapping information for capacity estimation

When we migrated the sequential data sets to SMS environment, the user catalog ran out of space, and many batch jobs were ABEND.

This was due to an increase in the size of catalog entries due to the use of a maximum of 59 for the Volume Count of the SMS Data Class.

If we had known in advance that SMS would increase the size of catalog entries, we could have prevented ABEND.

We think that it is necessary to describe the catalog mapping information for capacity estimation and the increase in the size of catalog entries due to the Volume Count of the SMS Data Class in the manual.

It should also be described in the manual that it is not recommended to specify a large value for the Volume Count of the SMS Data Class.

Applicable Manuals

・z/OS DFSMS Managing Catalogs

・z/OS DFSMSdfp Storage Administration

Idea priority High
  • Guest
    Reply
    |
    Aug 1, 2024

    The manual does describe the record sizes but it doesn't specify if those sizes include the SMS STORCLAS,MGMTCLAS and DATACLAS information. The table should show the NONSMS and SMS record sizes so it's clear there's a potential increase in catalog size (and VVDS size), if moving datasets under SMS management. And perhaps another field to show the bytes per volume required with a notation to indicate that this is affected by DYNVOL COUNT.

    DATACLAS DYNVOL COUNT can affect both SMS and NONSMS datasets. It also has an effect on the TIOT size so TIOT or XTIOT can be easily exceeded causing a failure if a job has a lot of DD's referring to multi-volume datasets or ones with a large candidate volume count. Each extra volume uses ~4k bytes of TIOT.