Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. 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 Future consideration
Workspace ITM/IBM APM
Created by Guest
Created on Aug 16, 2023

RTEMS IBInterface doStageTwoProcess messages to be sent to the MSG2 log

Currently the Stage 2 messages are sent to the RTEMS RAS log, which roll and are overwritten the frequency and speed of which is determined by the amount of tracing that is enabled.

These messages :

 (64D867A4.0008-7:ko4crtsq.cpp,6936,"IBInterface::doStageTwoProcess") Begin stage 2 processing. Database and IB Cache synchronization with the hub

(64D867A4.000A-7:ko4crtsq.cpp,7151,"IBInterface::doStageTwoProcess") End stage 2 processing. Database and IB Cache synchronization with the hub with return code: 0

 Are crucial in understanding and diagnosing issues and the current state of the environment.

There are times where connectivity drops between the RTEMS and the HUB and this triggers the Stage2 re-sync this can happen repeatedly and the only way to determine if this is happening and when the environment is stable and in the correct state is via these messages.

Also during Infrastructure activity it is important to make sure all FTO and stage 2 activity has completed as well as agent failover before we restart or failover any Hubs or RTEMS and it is difficult to determine if the RAS logs have rolled.

 Having these messages sent to the MSG2 log will mean that they are persisted and can be used to reference the current and historical state of the RTEMS “Readiness” to manage the TEMA’s attached.

This would also bring the RTEMS inline with the HUB FTO that currently writes FTO states to the MSG2 log eg: KQM0009

Idea priority Low