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 Submitted
Workspace IBM i
Categories PowerHA
Created by Guest
Created on Jun 28, 2022

Replicate save status and last save information across nodes in PowerHa Cluster.

In a PowerHA cluster, if I perform a save operation (to a tape drive) in a FlashCopy system that information is not spread among other systems in cluster specially production (main) system.

This cause some objects that must be saved before delete cannot be saved in another system different than its own system, for example, Journals Receivers.

It would be interesting if the "Save date/time" attribute and others related attributes of the object where replicated and/or distributed when the object is saved on a flashcopy node within the same cluster.

Use Case #1.

In a PowerHA cluster we use one of the Flashcopy systems to perform tape backups. Some elements that reside in iASP, such as journal receivers, must be properly saved before being removed from production.

When these objects are saved on our flashcopy system there is nothing in production to indicate that they have already been saved. This can be omitted with DLTJRNRCV DLTOPT(*IGNINQMSG), however it is not certain that they were saved completely. This forces having to save these elements directly in production to ensure that they have been properly backed up before they are eliminated.

Use Case #2.

We have store procedures that delete some "temporary" files in production every week, these files reside in libraries which are in iASP and are saved in FlashCopy. It would be very helpful if some system views like QSYS2.OBJECT_STATISTICS included some information that the item was saved on another node in the same cluster.

Idea priority Medium