Skip to Main Content
IBM Z Software
Hide about this portal


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 Under review
Categories Open Access TM
Created by Guest
Created on Feb 26, 2025

Show end wait time for synchronous callouts in the /DISPLAY ACTIVE command output

See this idea on ideas.ibm.com

IMS shows an end wait time for synchronous program switches in the /DISPLAY ACTIVE command output. This is very helpful in some kinds of error situations. Although for synchronous callouts the same DL/I call is being used, the /DISPLAY ACTIVE command output currently doesn't show an end wait time for synchronous callouts. Please add it. This would help to understand how long the wait could be, when the distributed application doesn't respond - which may not be easy to determine for an IMS sysprog or operator since the timeout value may be set by the application instead of by a global setting for a specific TPIPE configured with an OMTA descriptor. It may also help to understand whether an IMS application waits all the time for a response on a single callout or whether it is doing multiple callouts and waits again and again. At least some of the available IMS monitors also don't show this without having a call-level trace active. 

Idea priority Medium