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 Delivered
Workspace IBM i
Categories BRMS
Created by Guest
Created on Sep 20, 2016

BRMS: Allow Parallel Backup in BRMS when using *ALLUSR

According to
BRMS does not allow a parallel save when using *ALLUSR.
I want to be able to do so.

Use Case:

We spread our saves among four drives in our library.
Objects within a library are currently not scattered among the drives. Is
there a way to get it to do so?

The problem is we have one extremely large library (looking at breaking
that down but that will be difficult at best).
t's still saving for three hours after the other libraries in the *ALLUSR
part are done.
I'm sure that if it would scatter we bust that time by potentially 1/4. If so, this would increase system availability by 2 hours and 15 minutes.

*LINK save scatters.

While I am more concerned about the time, if I was still using physical
tape I would also be concerned about this
Volume ---Temporary Errors--- --------M Bytes--------
ID Read Write Read Written
G00129 0 0 1 1572815
G00130 0 0 1 549684
G00131 0 0 1 873180
G00132 0 0 1 552368
G00133 0 0 1 665417
The big library starts out on G00129. Fills that up and,
instead of using the empty space on 130-132,
it loads up another tape (G00133) and continues the save on from there.
Got this data from PRTERRLOG. I ran it with VOLSTAT(*DLT) right before the save to clear the old data.

Idea priority Medium
  • Guest
    Oct 7, 2016

    .Although we would not recommend doing 7.2 and above....if you create QTEMP/ should work, since we now process the *ALLUSR differently in those releases. IBM I OS does not support *ALLUSR in parallel-parallel format so we have to get a list of libraries on the *ALLUSR.
    So I'll mark this as delivered as that has been there awhile.

  • Guest
    Sep 26, 2016

    This is journal receiver library. Currently we give it a special name, #MXJRN, so that it gets restored before the data libraries. If we pull it out of *ALLUSR and append it so that we can do a parallel-parallel would the BRMS restore document tell us to restore it in the right order?

  • Guest
    Sep 22, 2016

    I marked this as need more information...but wasn't sure the right category. First on your space....since you are using 4 parallel streams in serial....the behavior is correct...once the big library is put on a media set...when it spans to the next tape we need to use a new tape..we can't span to an append tape...this is not BRMS, it is standard label that is normal.
    As to your question about doing parallel-parallel format on an *ALLUSR...that won't be wise as speading every library to 4 resources will do more damage than good. We would recommend that you pull out the big library from the *ALLUSR and just do parallel-parallel format on it...or there is a new control group attribute in 7.2 that sorts the library by size and does the bigger ones first...that might be the best method if you are at 7.2.

  • Guest
    Sep 21, 2016

    Creating a new RFE based on Community RFE #94797 in product IBM i.