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 DFSMS SDM
Created by Guest
Created on Apr 7, 2023

Allow Virtual Concurrent Copy (VCC) to dynamically allocate Working-Space Data Set(s)

Virtual Concurrent Copy currently requires each installation to pre-define/allocate the Working-Space Data Set necessary to contain the PIT track images.  There is no easy way for the installation to know what the appropriate size for these data sets should be and it is necessary to just "guess" or use SMF data to determine what is appropriate.  But if the installation defines the data set too small, the concurrent copy can fail.  VCC should be able to dynamically determine the necessary size (or at least use some default size) and allocate these data sets as necessary instead of forcing each installation to pre-define them.  This could work similar to the way that the SVC Dump process can dynamically define the SVC Dump data set when an SVC dump is being generated.  If necessary, a new ANTMIN00 parameter could be used to allow/disallow this new function as well as manage the size of the data set--to set a maximum size, for example.

Idea priority Low