Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace IBM i
Categories BRMS
Created by Guest
Created on Jun 17, 2019

BRMS restauration issue

Scenario :
* Sunday FULL backup .
* Monday CUML backup - OBJ1, OBJ2, OBJ3 in LIBA saved
* Tuesday morning delete OBJ1 -
* Tuesday evening CUML Backup - OBJ2, OBJ3 in LIBA saved
* Wednesday scratch system :
- Restore from Full OBJ1, OBJ2, OBJ3 in LIBA restored
- Restore from last CUML Tuesday : OBJ2, OBJ3 in LIBA updated

We don't want to restore the deleted objects .
It's a problem to have the OBJ1 on the system .

How to manage the deleted object ?

Use Case:

2 cases of solutions from IBM:

There is a posibility by applying journal entries at the end of the restores (full + cuml) if the libraries were being journaled at the
time of the save. Journal code D entry type DT - will delete the deleted objects.

BRMS keep track only of deleted libraries and may prevent BRMS to restore them if you OMITLIB(*DELETE) on STRRCYBRM

--> These solutions do not meet our needs

Idea priority High
  • Guest
    Oct 28, 2019

    The BRMS team has previously requested more clarifying information. Because the additional information was not provided within 30 days, the request has been closed.

  • Guest
    Jul 18, 2019

    The BRMS team needs more information to further assess your Request for Enhancement.

    We follow the scenario that was listed, but we don't understand the environment and the resulting problem.
    ??? Can you describe the resulting problem in more detail? Is it an application failure? Does it affect a single application or multiple?
    ??? Are the objects deleted intentionally or unintentionally?
    ??? Are the objects deleted by an individual or application?
    ??? Is this issue specific to an application library or does this happen randomly to several libraries? If this is related to just one library, it might be better to just always do a FULL backup after objects are deleted.
    ??? Are the objects being deleted the same or different names and types or are they random and you don't know the names? If they follow a pattern maybe they could be omitted from the backup.
    ??? Does this scenario happen often, that a scratch recovery is required?
    ??? Is your expectation that BRMS automate the detection and omission of such objects or are you willing to provide the necessary data for such objects when this scenario occurs?

    We ask these questions in order to understand whether this situation is a general issue or specific to your current environment and process.
    BRMS cannot reasonably track when every object comes and goes from the system, nor can we reasonably infer automatically which objects are
    required or not required.