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 Jun 17, 2014

Allow DBRC=N for Restoring HALDB

DBRC=Y is good only when you need to perform Disaster Recovery to production region whereby it will ensure the integrity of the HALDB image copies being restored.

However, most of the time DBA is performing restoration from their past HALDB backup for fault investigation, report generation, volume testing using production data.

With DBRC=Y has prolonged and complicated the HALDB restoration process. DBAs need to specify lots of DBRC information related to the image copy and perform NOTIFY.IC into the RECON in order to perform any HALDB restoration.

The worst is to obtain the IC RUNTIME info if the past image copy details are not longer exist in RECON data sets.
DBAs have to read the first header in the image copy data set for each HALDB partition in order to obtain the IC RUNTIME information to reconstruct the NOTIFY.IC .

There is no reason the FULL functional Database can be restored with DBRC=N but not HALDB.

Idea priority High
  • Guest
    Reply
    |
    Jan 28, 2019

    Hi Jin Chee,
    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 54954 is this item is not strategic to our roadmap.

    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