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 Submitted
Created by Guest
Created on May 27, 2026

Change the PDB dialog for MRT entries to explicitly define a 'DISPLAY YES' when one codes 'No' for 'Suppress from Console'

MRT overrides MPF, which one expects and is good.

In the SA PDB disalog, the MRT fields default to 'No entry built'  if the field is left blank.  This is good.
When you explicitly define a value, you expect the MRT entry to be built.   This is good.

BUT.....

In the case of specifying 'NO' for the 'Suppress from Console', then No REVISE statement is built for DISPLAY.  This, IMHO, is BAD, requiring the user to code manual overrides to ensure the messages is displayed, when the dialog should already do this.  Coding NO, should NOT be the same as leaving the field blank.

This behavior is BAD!

Examples:

#1 Proper behavior
------------------------------------------------------
 Automate . . . . . . . . . YES          (YES NO)     
Suppress from console  . . YES          (YES NO)     

REVISE('Y' AUTOMATE)     
REVISE('N' DISPLAY)      <=== Correct - builds both REVISE statements
------------------------------------------------------
 

#2 Proper behavior
------------------------------------------------------
 Automate . . . . . . . . . YES          (YES NO)     
Suppress from console  . .              (YES NO)     

REVISE('Y' AUTOMATE)     <=== Correct - Suppress... field left blank so no REVISE for DISPLAY 
------------------------------------------------------

#3 BAD behavior!!!
------------------------------------------------------
 Automate . . . . . . . . . YES          (YES NO)     
Suppress from console  . . NO          (YES NO)     

REVISE('Y' AUTOMATE)     <=== BAD!!! - No REVISE for DISPLAY, even though user coded 'NO' 
------------------------------------------------------

One should NOT need to specify an MRT override, when the dialog can do so!
This is annoying, causes extra work, and causes mistakes when one expects the MRT to override MPF.
This behavior should never have been permitted and is long overdue to be fixed.  
If specify NO for 'Suppress from console' then I should get the appropriate REVISE statement created

Example:

Automate . . . . . . . . . YES          (YES NO)     
Suppress from console  . . NO          (YES NO)     

REVISE('Y' AUTOMATE) 
REVISE('Y' DISPLAY) 

 

Idea priority High