Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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
Categories z/TPFDF
Created by Guest
Created on Mar 13, 2026

ZUDFM INIT database initialization functionality to run concurrently with application workload

Problem: Visa recently initialized a new 4 billion database allocation, this was done during a 4-hour outage window because the existing ZUDFM INIT throttling doesn't give enough control to run it in Norm state with application traffic. Even in 1052 state the ZUDFM INIT could not utilize the disks to the maximum potential due to a flash copy that runs in the background during every maintenance window and caused the ZUDFM INIT to throttle on the IBMBATCH limit for IOB usage.   

Requirement: A different approach is requested were-by these large databases are initialized as a background task which doesn't take system resources away from the transactional workload, these jobs might take days to complete and would need the ability to abort and restart again with minimal operational maintenance.

Visa already has frameworks that manages utility function so the ask here is for a C++ api call that will initialize a specific fixed ordinal and chains, so the parameters include a file address and run option similar to those of ZUDFM INIT such as HOLD NOHOLD and RELEASE.

Idea priority Medium
  • Guest
    Apr 10, 2026
    Thank you for the additional information, the z/TPF lab will continue with the evaluation of this idea.
  • Guest
    Apr 2, 2026
    In order to help the z/TPF lab evaluate this idea, please respond to the following questions:

    (1) "Visa recently initialized a new 4 billion database allocation."
    Was this initialization done with the NOHOLD parameter?

    (2) Do you only use ZUDFM INIT for new databases? How often do you use ZUDFM INIT for simple re-initializations of databases with existing data or as a tool to migrate to new formats?

    (3) And to confirm, you would want the new API to be able to handle initializations of new databases, initializations of existing databases, and initializations to migrate the format of existing records?

    (4) "the existing ZUDFM INIT throttling doesn't give enough control to run it in Norm state with application traffic"
    What kind of control do you need to run the utility in Norm state with application traffic?

    (5) "the ZUDFM INIT could not utilize the disks to the maximum potential due to a flash copy that runs in the background during every maintenance window and caused the ZUDFM INIT to throttle on the IBMBATCH limit for IOB usage"
    If an API were provided, what would the Visa utility function framework in conjunction with the API do differently than can be done with the ZUDFM INIT utility today?

    (6) "Even in 1052 state the ZUDFM INIT could not utilize the disks to the maximum potential"
    Is the pain point here that the initialization cannot complete in the 4-hour outage window? How long did it take to initialize 4 billion records?

    (7) "Visa usually deactivates logging for the duration of a ZUDFM INIT to avoid logging tape overload, this would also be a desirable parameter for the new api call."
    To clarify, you would want an API parameter to optionally not log that specific file activity?