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 Not under consideration
Categories General DB
Created by Guest
Created on Nov 13, 2019

New option to generate DBD without metadata

We would like to have a new DBDGEN option that enables users to generate a DBD without an extended fields table for metadata.
For example, we propose adding a new macro like below, which precedes other DBDGEN macros and allows users to specify not to include metadata in DBDs:
DBDOPT METADATA=NO ... new macro (optional)
DBD NAME=HDO6,ACCESS=(HDAM,OSAM),RMNAME=(DFSHDC40,5,5), +
ENCODING=CP1047,REMARKS='DBD WITH META DATA'
:
DBDGEN
FINISH
END
We need this kind of DBDGEN option in order to support databases that have large metadata in batch utilities like Unload, Reload, and so on.
These utilities load DBDs during the processing, but since DBDs are required to be RMODE=24, they can easily run out of storage below 16MB line when DBDs have several megabytes of metadata. These utilities do not access metadata at all, so they can process these databases when DBDs without an extended fields table are provided.
One customer already reported this issue. As a workaround, we provided a modified DBDGEN macro that does not generate an extended field table and asked them to use it for creating the DBDLIB for batch utilities.
The modification we made on DBDGEN macro were in two lines, as follows:
1. Replace "DC A(EXOPRTAB)" at line number 08650000 with "DC A(0)"
2. Comment out the DFSFTAB call at line number 19050000
The customer accepted it as a temporary solution, but they requested a permanent solution to be integrated into the official DBDGEN macros with a new keyword like METADATA=NO, because they do not want to check on every IMS maintenance if the modified DBDGEN macro still works. That is the background of this RFE.
In order for the batch utilities to detect that the extended fields table has been eliminated, we would want the new DBDGEN process to indicate it in the DBD.

Idea priority High
  • Guest
    Reply
    |
    Sep 29, 2020

    Hi Rocket software,

    Thank you for your interest in keeping IMS a vital and successful product. Software development has continuously evolved during IMS's lifetime, and so has IMS itself. We have kept pace with, adopted, and implemented many industry standard best practices within our organization, including Continuous Delivery, Design Thinking, and Agile.

    When choosing new features to add from the list of requirements in our backlog, we assess which will bring the most value to as many clients as possible and prioritize those.

    At this time, after reviewing this request for enhancement and assessing its potential value, we have decided to reject it. The reason we are rejecting RFE 138156 is we will address this via APAR PH29782.

    We appreciate your input to IMS, and we hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of IMS.

    Sincerely,
    Deepak Kohli (deepakk@us.ibm.com)