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 Jan 13, 2017

Add *LSTSAVSYS option to PERIOD Beginning date for STRRCYBRM

Current options on STRRCYBRM prevent us from automating printing of recovery reports including using a hub system in Enterprise Services. To get usable reports for a recovery we have to keep track of the last SAVSYS and manually enter that date on reports for every partition. Using the default of *BEGIN includes a large number of tapes from saves that are years old that really aren't needed for recovery. Using *CURRENT causes the reports to exclude the last SAVSYS and print instructions to restore LIC from distribution media.

By providing a start date of the last SAVSYS with an option like *LSTSAVSYS we could easily automate reports. This has also kept us from using automatic reporting from a hub in Enterprise Services because the available options don't allow us to specify options that don't include tapes that aren't really needed.

Use Case:

Including an option to specify recovery reports from the last SAVSYS will allow automating reports and the ability to use Enterprise Services for automatic report generation and more efficient use of staff time. The automatic reporting through Enterprise Services would also allow us to send reports to an email address that would then provide easy access from our recovery site if our main site is inaccessible.

Idea priority High
  • Guest
    Mar 2, 2017

    IBM believes this request has been solved after reviewing the specific backup requirements implemented by the customer. The backup control group entry to save IFS needed to switch to use the *LINK entry instead of an IFS list. Then the PERIOD(*DAYS) parameter on the STRRCYBRM command provided the desired customer behavior.

    Here is the BRMS wiki documentation with the BRMS unique IFS behaviors:!/wiki/IBM%20Backup%2C%20Recovery%20and%20Media%20Services%20%28BRMS%29%20for%20i/page/Backup%20IFS%20lists!/wiki/IBM%20Backup%2C%20Recovery%20and%20Media%20Services%20%28BRMS%29%20for%20i/page/Omit%20IFS%20Directories%20and%20Files%20from%20Link%20Saves

  • Guest
    Jan 14, 2017

    Mr. Hall,
    I think STRRYCBRM already supports this concept...please look at this Recovery Element was meant for what you are requesting...I believe? Do you agree? Thanks.
    David Bhaskaran (
    Recovery element override:
    Recovery element . . . . . . . *ALLSYS *ALLSYS, *SAVSYS, *SECDTA...
    Time period for recovery:
    Start time and date:
    Beginning time . . . . . . . . *AVAIL Time, *AVAIL
    Beginning date . . . . . . . . *BEGIN Date, *CURRENT, *BEGIN
    End time and date:
    Ending time . . . . . . . . . *AVAIL Time, *AVAIL
    Ending date . . . . . . . . . *END Date, *CURRENT, *END
    + for more values