Skip to Main Content
IBM Power 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:

Post your ideas

Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas and add comments to ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Specific link you will want to bookmark for future use

IBM Unified Ideas Portal - - Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.

Status Future consideration
Workspace IBM i
Categories BRMS
Created by Guest
Created on May 26, 2022

Multiple/Parrallel BRMS save jobs with the same media policy would result in BRM148A

When multiple BRMS save jobs with the same media policy are run concurrently at the same time, BRMS might not be able to handle it well. At times, it will throw out false exception like BRM148A.
Idea priority Urgent
  • Guest
    Jun 3, 2022
    The BRMS team will use this request as input to planning but no commitment is made or implied. The request will be updated in the future if the request is implemented. The BRMS team will use votes and comments from others in the community to help prioritize this request.
  • Guest
    Jun 3, 2022


    Our expectation for the concurrent save jobs using the same media policy with append(*YES) would be for the save to go to different volume. We do not expect the save job to always go to the same volume, we would want the save job to use any available volumes with same media class that it can append to and if there isn't an append volume available, it will picked a expired volume.

  • Guest
    Jun 2, 2022
    The BRMS team needs more information to further assess your Request for Enhancement. After reviewing the case numbers provided, it appears that the same volume was being used by the concurrent save jobs. Is the expectation that the concurrent jobs append to the same volume, or just that they use the same media policy and it is ok for each of the individual jobs to write to different volumes?