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.

Add a new idea Subscribe
Status Future consideration
Workspace IMS Database Manager
Categories General DB
Created by Guest
Created on Jul 13, 2021

RELATED IDEAS

DFS3CATQ API with CONTCAT option

This is a curious case with the DFS3CATQ API that exists today when making separate calls to PENDING versus CURRENT IMS directories. I believe this error would not occur if we have the CONCAT option listed below.

In this case we have HIDAM DBD that resides in the STAGE and ACTIVE IMS Directories, but the HIDAM primary index is only present in the ACTIVE IMS Directory. When we load the HIDAM DBD from STAGE, we get a DBD load module format where the HIDAM Primary Index LCHILD name has been replaced with the value $DFS3001, instead of the proper DBD LCHILD name value (see trace records below, 120 traces the output area of the DFS3CATQ call and the 121 trace record is the DBD load module layout the field name in error is at offset x'1E0' ). If we put the primary index in to the STAGE IMS Directory also, then the DFS3CATQ GET call from PENDING then returns an accurate DBD load module block (see second set of trace records)
Attached word doc has the trace.

Idea priority Medium
  • Guest
    Reply
    |     Aug 20, 2021

    Hi Anshul,

    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.

    After reviewing this request for enhancement and assessing its potential value, our decision is to add this item to our backlog. Items in our backlog are expected to be delivered within the next 18 months. We reserve the right to re-prioritize our backlog items as new requests come in. This helps ensure that we are constantly focused on providing the best value to all of our clients.


    Have a great day!
    Deepak Kohli – deepakk@us.ibm.com

  • Guest
    Reply
    |     Jul 13, 2021

    Attachment (Description): Trace details mentioned in description.

    trace.txt
    trace.txt
    Open full size
    trace.txt

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.