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
Created by Guest
Created on Aug 1, 2022

ICKDSF utility to include VVDS creation as part of INIT

Why is it useful: VVDS automatically creating immediately upon INIT causing VVDS created with less size, avoid timing issue and avoid automatic VVDS size creation

Who will benefit: all the customers use ICDSF INIT, VVDS avoid redefine with customized increased size.
How it should work: Provide a VVDS size function in ICKDSF INIT parm, so that the VVDS also gets created along with VTOCIX while the volser is offline and during INIT processing.

Idea priority Urgent
  • Guest
    Reply
    |
    Aug 22, 2022

    Thanks for the information about IGGCATxx setting, we do have set some reasonable size but that is only valid for our least sized MOD1,3,9 volsers as we do not want to code bigger size which is not recommended for small sized volsers.

    Also there are considerations for Non SMS volumes too for IGGCATxx which can be overcome by providing an option in INIT command.

    Atleast if there is an option to set the size based on the Volser size would be beneficial. For example give us a provision in IGGCATxx parmlib to specify the default VVDS size for MOD1, MOD3, MOD9, MOD27, MOD54 volsers.

    If that is not possible then having an VVDS size option on ICKDSF INIT parm will be beneficial.

  • Guest
    Reply
    |
    Aug 4, 2022

    The default size of a VVDS TRK(10,10) can be changed to a value that meet your needs. This can be set in SYS1.PARMLIB(IGGCAT*) or entered as a F CATALOG,VVDSSIZE command. This means that after initialisation of a volume the first allocation of a dataset on the volume will cause the VVDS to be implicitly defined based on your chosen default size. (Note this works slightly differently with SMS and NONSMS volumes) You'd need to choose the default VVDS size to carefully to cater for the various DASD sizes you have and typical number of datasets per volume. IBM recommend not making this default too big as it can have performance implications.
    https://www.ibm.com/docs/en/zos/2.4.0?topic=size-estimating-space-requirements-vvds#vvdsize
    Perhaps you might still do explicit VVDS defines in some cases such as EAV's.