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
Workspace IBM Z NetView
Created by Guest
Created on Apr 8, 2022

Delay processing of missed messages when NetView address space is recycled

We use the MVSPARM.Msg.Automation.MaxAge = 600 function, so NV will catch up on messages following a recycle of the address space. However, we recently missed automating a message following a recycle as it was coded in SA’s INGMSG02 table and this was loaded after CNMCSSIR had replayed the missed messages.

The automation that was missed does not use SA features and would have worked had it been coded in our own table. It is simply coded in the SA policy to take advantages of Easy Message Management. So, one option is to move the code out of SA policy and put it into our own MAT, but this does feel like a backward step.


We would like the ability to delay processing of any missed messages until SA has initialised and INGMSG02 is active.

Idea priority High
  • Guest
    Reply
    |
    Jul 7, 2022

    maybe even a feature that permits both tables.


    As we have an initial table that will trap things as well. If we were to wait and only run the missed messages once SA initializes would mean we would have to duplicate the messages from the MSG00 member as well.