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 System
Created by Guest
Created on Oct 23, 2013

IMS Catalog size estimate-COPYBOOKs are not currently included in estimate

The IMS Catalog database size estimating process only includes the PSB & DBD info.    Those are tiny compared to my COPYBOOK members.    They are HUGH.    I have sent examples to developers in the past during other IMS Catalog & IMS Explorer discussions.    Not including the of Copybooks in the Catalog Populate Utility estimate will definitely skew our results. Our COPYBOOKs are very large, defining numerous fields and have redefines on our redefines. We need to Catalog Populate Utility estimate to include Copybooks so we get a better estimate to better size the Catalog DB. The current estimation size results will be way too small.

Idea priority Medium
  • Guest
    Reply
    |
    Feb 27, 2019

    Hi Ann,
    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. We think it’s a great idea but we are rejecting RFE 40763 because we have not had many clients buy into this enhancement. There doesn’t seem to be much interest from other clients. We would rather invest in high priority items that bring the most value to many clients.

    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.
    Thank you.
    Sincerely,
    Deepak Kohli - deepakk@us.ibm.com

  • Guest
    Reply
    |
    Mar 24, 2014

    How about just letting me tell you in a parm how big in tracks my COPYBOOK library is? The program uses the data from the DBDS & PSBs & the tracks to estimate how big the IMS Catalog database needs to be. The estimate does not need to exact. Bigger than currently required is okay. I know IBM has plans to use the IMS Catalog database for more features in the future. Thanks!
    Ann

  • Guest
    Reply
    |
    Feb 20, 2014

    Hi Jeff,
    I want to estimate size BEFORE the info is added to the PSBs & DBDs. I'm building the original IMS Catalog. I'd like to build all 12 so they're good for a couple years usage WITHOUT having to redo partitioning & size. Actually - 24 of them - we have copies of all IMS regions in sandbox. I'm trying to be proactive. We average about 5000 members in our test acblibs & 3000 in our production. The segment definitions in the DBDs is VERY little. Our Copybooks are HORRIBLY UGLY & huge. We have redefines on redefines of redefines. If you want to see some, check with Geoff Nicholls. I gave them to him.
    Ann

  • Guest
    Reply
    |
    Jan 9, 2014

    I want to get estimates BEFORE we start to make sure I have enough DASD.
    It would be more productive to allow the catalog populate utility estimate function run as a pre-migration/set up jcl – before any changes/installs are made.
    It should be able to be run like the HALDB Migration Aid utility (DFSMAID0). I feed it the PSBLIBs, DBDLIBs, ACBLIBs, COPYBOOK libs and a percent of planned growth and the program should tell me how many partitions & what size they should be.
    Depending upon the # of partitions & size & the number of regions, I may need to request more DASD. Sometime that goes quickly; sometimes that can take months!
    Ann

  • Guest
    Reply
    |
    Oct 28, 2013

    We have just started using ODBM. We have 3 POCs going. Ther eare only a few DBs involved. The metadata/sql files are currently stored on their servers. In 1st Q of 2014, I will be creating the IMS Catalog database for FUTURE projects. I can not regen hundreds of DBDs and/or PSBs with extended attributes until they are going to be used. How do I project for the future and size the Catalog HALB correctly? The tool needs to handle projections as well as current use.
    Ann

  • Guest
    Reply
    |
    Oct 24, 2013

    Hi Ann,

    Thank you for your enhancement request. I have a request for additional information on this RFE.

    The catalog populate utility provides estimates based on the information in the ACBLIB used to build the catalog. To get the correct estimation from the catalog populate utility you would need to add the metadata from the COPYBOOKs to the DBD and PSB source with the IMS Explorer or another method. After you have added the COPYBOOK information to the DBDs and PSBs then go through the DBDGEN / PSBGEN / ACBGEN process. That process will store the additional metadata into the ACBLIB. When the ACBLIB contains the metadata information the catalog populate utility should build the correct estimated sizes.

    Have taken these steps to get the COPYBOOK information into the ACBLIB for the populate utility? If you have and the populate utility did not reflect the correct estimates then you should open a PMR to follow-up with our technical support team to determine why the populate utility did not build the correct estimates.

    Best Regards,
    Jeff Fontaine