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 Feb 13, 2021

BRMS to ignore some non-critical errors when saving spools

BRMS does stop save procedure in some cases of non-cricital errors like saving QUSRSYS with some spool files damaged. It would be preferrable to have BRMS by default ignore the errors, post more detailed information into DSPLOGBRM and continue save.
BRMS started

Use Case:

We had a customer system doing *SYSTEM save every night. The last 2 saves failed due to some damaged spool files which must be repaired by

The save was cancelled at QUSRSYS and BRMS ended the job so a lot of important user data was not saved to tape.

Idea priority Medium
  • Guest
    Apr 28, 2021

    Hi Rudi,
    thanks - i know how to work around. For resilience reasons, i would like to have the BRMS team to add some parameters (i will create a separate RFE) so we may be able to have at least a daily 95% save instead of a stop at 10%. Thanks.

  • Guest
    Apr 26, 2021

    The BRMS team does not intend to provide a solution to this request, so it is being closed. BRMS has been designed to handle specific operating system errors as critical errors which stop the backup, such as CPF3794 and CPF3795 error messages. This request does not align with the BRMS design. It seems more appropriate to understand and resolve the issue of why objects are being damaged or to have the operating system report a different error if the errors should not be considered critical.

  • Guest
    Mar 17, 2021

    Hello Holger,

    For the time being I think you need a workaround in order to avoid this problem.

    What I suggest is setting the saving of spoolfile data apart from saving the rest of what you want to save.

    Please contact me directly, if you are want to be informed about this workaround.

    Greetings Rudi

  • Guest
    Mar 16, 2021

    The CEAC has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed.

    Background: The COMMON Europe Advisory Council (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

  • Guest
    Mar 15, 2021

    I think this should be moved to Core OS as also the basic SAV* commands show this issue: set a device (tape, savf) to defunct when saving a defective object like save file (resp. outq)