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 Jan 14, 2019

BRMS: Allow parallel-parallel save and OMITS(*IGNORE/*PROCESS) for library objects

Instead of simply listing *ALLUSR on our control groups we use a list entry which only has one entry, *ALLUSR. The reason we do this is because
we do a parallel-parallel save. Basically that's IBM speak for allowing it to support saving across multiple drives in a library.
The GUI only supports using the omits if you use *ALLUSR and not a list.
Therefore, if you want to do a parallel-parallel save, and handle omits with processing them sometimes and ignoring them others you cannot use the stuff within the GUI for omits. You have to set up two control groups, with two different lists, one with the omits and one without. You do not
get the capability of OMITS(*IGNORE). If you really want to use a single control group then you need to submit a RFE to either:
- Allow non listed plain *ALLUSR support parallel-parallel save
- Allow a list vs just *ALLUSR support the GUI omits.

Use Case:

I am using HA replication software. I do a save on the target system. I want to use four drives in my library to speed up the save. I use the HA vendors technique for this to shutdown all the locks they have on the application software however they leave locks on some *USRIDX and *USRQ objects to continue receiving during the save (or some related process). These abort during the backup with
CPF3771 - 142 objects saved from HA_USR. 12 not saved.
CPF3761 - Cannot use *USRQ HA_USRQ in HA_USR.
CPF3761 - Cannot use *USRIDX HA_IDX in HA_USR.
BRM16A1 - Backup *ALLUSR, type *FULL completed with errors.
BRM14A1 - Save of list ALLUSRLIB completed with errors.
BRM10A1 - Control group TUE_FRI_HA type *BKU completed with errors.

Idea priority Medium
  • Guest
    May 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
    Mar 8, 2019

    The solution of using a list entry to do a parallel-parallel save with the special value *ALLUSR is a BRMS implementation flaw. BRMS did not intend to enable an *ALLUSR to be done using parallel-parallel. Parallel-parallel is not IBM speak for saving to multiple drives in a library, it is related to spreading a single large object across multiple drives. Parallel-serial is a different concept that BRMS already utilizes when *DEFAULT is specified for the Parallel Type for the control group entry for special value backups like an *ALLUSR. This option will spread libraries across multiple drives when running the backup. This is the preferred option and would support your described use case to utilize OMITS(*IGNORE) capabilities by either specifying omits using the WRKPCYBRM *BKU option 2 to specify *ALLUSR omits or using the *ALLUSR GUI omits.

    Recommendation: Remove the *ALLUSR list control group entry that you have implemented and use the *ALLUSR entry in the control group with *DEFAULT for the Parallel Type along with specifying the number of Parallel device resources to use in the Minimum resources and Maximum resources parameters. Additionally, check that you are using the Sort by *SIZE option to order libraries from largest to smallest to improve backup performance. This option can be specified in the control group attributes WRKCTLGBRM option 8 which by default points to *BKUPCY. To change the backup policy value use WRKPCYBRM *BKU option 1.

    Please add a Comment to this RFE to let us know if this recommendation is sufficient for your Use Case. If so, we could consider changing the Headline to better match your Use Case, and consider this to be Delivered. If not, let us know what else might be needed.

    Note also that BRMS plans to close the *ALLUSR flaw in the lists that you have uncovered and will fix this in a future PTF to not allow a list with an *ALLUSR to use the *PARALLEL setting. Running an *ALLUSR in parallel-parallel is not advised because of the slower and more complicated recovery process. For more information on IBM i parallel save and restore reference the BRMS wiki information at!/wiki/IBM%20Backup%2C%20Recovery%20and%20Media%20Services%20(BRMS)%20for%20i/page/IBM%20i%20parallel%20save%20and%20restore

  • Guest
    Feb 18, 2019

    The COMMON Europe Advisory Council (CEAC) has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed.

    Background: The CEAC members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.

    To find out how CEAC help to shape the future of IBM i, see CEAC @ and the article "The Five Hottest IBM i RFEs Of The Quarter" at

    Therese Eaton – CEAC Program Manager, IBM