Skip to Main Content

This is an IBM Automation portal for Integration 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Aug 10, 2023

Uniform (preferably JSON) format of MQ command output also on z/OS

MQ command output is used for monitoring, administration and analysis of MQ on different platforms.

It would be useful to have uniform format for different platforms including z/OS. Preferable command output format is JSON.

In that case one can collect, parse and interpret platform independent MQ data in same practical format. 
The same (semi)automated process for data processing can be applied then for MQ on all platforms including z/OS.

Idea priority Medium
  • Admin
    Matthew Leming
    Aug 29, 2023

    The JSON formatted command support in the REST API was designed for those MQSC commands which follow the standard MQSC format with attributes consisting of name-value pairs.

    A number of z/OS commands, such as DIS LOG, DIS SYSTEM, DIS USAGE, DIS THREAD, etc don't follow this pattern which is why we didn't implement support for them. In general they are hard to parse in a consistent way.

    They are however available via the MQSC REST API: so there is still a RESTful way to run those commands. Use of this API is close to the JSON based approach so you should hopefully be able to use it in your existing process.

    We are unlikely to adjust the JSON API to include these commands in the future.