Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Mar 11, 2024

Reduce the about of CPU/MIPS used during zRTEMS startup

In environments with large numbers of nodes (8000+), when a z/OS RTEMS is started the RTEMS is measure to use 300-500 MIPS while establishing a HTEMS connection. During an IPL this is not an issue thanks to IPL BOOST, but when the zRTEMS needs restarting outside of an IPL, this high MIPS use is causing delays in production work loads and is some causes causes XCF stall messages!  

While is recent zRTEMS releases it is now possible to limit CPU/MIPS resources and still allow the zRTEMS to successfully to start via the KDS_EIB_TIMEOUT_DURATION option, the issue is that as long as the zRTEMS is starting the system is running un-monitored!

 Using FTO also does not help here, because the switch to a different HTEMS always causes high CPU/MIPS use!

Establishing the zRTEMS <-> HTEMS connection needs to be optimized/changes(trottled?) to prevent these high CPU/MIPS spikes!

Idea priority High