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.

Add a new idea Subscribe
Status Delivered
Workspace IBM OMEGAMON for IMS on z/OS
Categories Product functionality
Created by Guest
Created on Sep 25, 2019

RELATED IDEAS

OMEGAMON/IMS REQUIRES API MONITORING

IMS, when combined with z/OS Connect, has the capability to support IMS trxs calling an API. The API request goes thru z/OS Connect to where ever the API is to execute. In the meantime the IMS trx goes into a wait, waiting for the API response. Omegamon/IMS has no knowledge of the API so it shows the trx waiting in application code in the region. Omegamon/IMS MUST recognize API calls and show them in the trx status display. Same for the ATF trace, it can trace DLI and SQL and MQ calls, APIs do not show up. We have APIs going off into the cloud with a 5 second timeout. Omegamon/IMS shows us nothing about API processing. Please correct this deficiency and Omegamon/JVM is not the answer. Omegamon/JVM should have a 2 way link with Omegamon/IMS so the user can switch Omegamon products while tracking a problem.

Idea priority Urgent
  • Admin
    Ashok Mahay
    Mar 13, 2026

    Hello, thank you for opening this product enhancement request. I am pleased to announce this enhancement has been delivered with APAR OA68060. Please reach out if you have any further questions. Regards IBM OMEGAMON Product Management.

    Reply
  • Guest
    Oct 19, 2022

    As for showing zCEE call in-flight on transaction status displays, this will be delivered in a separate PTF.

    Reply
  • Guest
    Oct 19, 2022

    For the ATF zCEE reporting, please refer to the updated document: https://www.ibm.com/docs/en/om-ims/5.5.0?topic=v550-new-in-ptf-uj09389-october-2022

    Reply
  • Guest
    Oct 19, 2022

    The ATF enhancement to report z/OS Connect outbound API calls is now available: https://www.ibm.com/support/pages/apar/OA63793

    As for the 2-way link to Omegamon/JVM, this is being considered.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.