Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 Not under consideration
Workspace z/OS
Created by Guest
Created on May 6, 2021

Add SNMP manager usage of MIBS.DATA for processing alert traps

We are running OSNMP in a started task to receive messages over port 162 from outboard hardware. Previous to z/OS 2.3 the messages come across as EBCDIC and we could use automation to create alerts for warning and critical messages. Now under z/OS 2.3, the messages come across as an ASCII string and are unreadable. This change in behavior was caused by FIN APAR PI66903, preventing the automatic conversion of Octet Strings as if they are ASCII strings, generating the HEX dump of the buffer instead. As stated in the support case: It appears that the underlying issue is that the MIBS.DATA input is not used when decoding the packet, it is only used when creating a GET type request.

Idea priority Medium
  • Guest
    Reply
    |
    May 19, 2023
    This item is unlikely to be given high enough priority to be placed into product plan.