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
Created by Guest
Created on May 4, 2017

Watchesspawning QSCWCHPS jobs

When you create a message queue watch, the OS spawns a QSCWCHPS job whenever the specified message ID is generated. That QSCWCHPS job determines if it's for the specified message queue and, if it is, executes the watch program. This causes a tremendous amount of unnecessary overhead when you only want to monitor a single message queue. The QSCWCHPS job should not be spawned unless the new message was in the correct message queue.

I specified a message queue and *ALL for the message ID. That spawned so many QSCWCHPS jobs that the audit journal consumed 10% of my total DASD in a single day. Not to mention the wasted CPU cycles.

Use Case:

We're using an exit point security package that sends a message to a specified message queue when a violation occurs. We need to immediately handle those messages. I need to create a watch to watch for any new message added to that message queue.

Idea priority Medium
  • Guest
    May 5, 2020

    This is a large effort, and unfortunately we are not able to provide this function at this time.

  • Guest
    Oct 30, 2019

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Work Management and Messaging
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Core OS
    Operating system - IBM i
    Source - None

  • Guest
    Oct 9, 2017

    The WCHMSG(*ALL) option on the STRWCH command was not intended to be used by long running applications. It was designed as a service tool for very targeted debug situations. As you will note, the help text on STRWCH command does warn of the performance impact of using the *ALL option, "*ALL - All messages are to be watched. This includes stored messages and immediate messages. Be aware that watching for all messages may cause performance degradation on your system. Use it cautiously."
    However, we will investigate how much effort it would take to rewrite the current design to improve the performance of the *ALL, and then prioritize your request along with the other requests for new function.