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 Future consideration
Workspace z/OS
Categories z/OSMF
Created by Guest
Created on Sep 4, 2023

Running REXX containing dialogues should issue an error in case of user interaction when using REST interface

We use the command "zowe zos-tso issue command "exec somerexx"" extensively, to reuse some of our existing REXX on Z.
This causes problems sometimes, when a legacy REXX calls another legacy REXX that calls another ..., and somewhere a panel pops up that require user interaction.
This causes the user session to hang, and can also cause problems with the z/OSMF task.
The effect is that no more "zowe zos-tso issue command "exec" commands can be issued, until the user session is timed out.

We would like z/OSMF to somehow register that a user interaction was initiated, and terminate the call and return an error instead of just hanging.

Some of this could be solved by a timeout, that returns control to the script running the Zowe command, with a timeout message.
But this wont fix the session, that I would assume is still hung.

Idea priority High