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 Future consideration
Workspace App Connect
Created by Guest
Created on Mar 19, 2015

Unifying of date, time and dateTime output of all mqsi* commands

Good morning, I would like to ask You to unify date, time and dateTime output from all mqsi commands. One command outputs dateTime based on Java Locale SHORT, another some universal LONG... This is a mismatch. And it is hard to parse SHORT ones, where are missing leading zeros etc. Of course, the output of all mqsi commands to XML using some --format:xml and respecting XML Schema data type formatting would be great - see my RFE 40438. Thank You, Stepan

Idea priority Low
RFE ID 68256
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Nov 26, 2020

    RFE Review. Apologies for the length of time this RFE has remained in Uncommitted Candidate status. Unfortunately it has not gathered sufficient votes / community interest through this time to have yet been prioritized for attention. The use case has again been discussed by our leadership team and we wish to keep the RFE open for now. We note that for a variety of reasons our commands are coded in a mix of language implementations (C, Java, shell script, JavaScript etc) and this can accidentally lead to differences in style of reported timestamps. It would be helpful for any commenters to highlight specific commands they feel are the highest priority for attention. Noting the comment about mqsilist, we also note that this command's behaviour with timestamps has altered in the interim due to the way that BAR file usage is now reported, so this particular case may no longer be a problem. For now the status of the RFE is maintained as Uncommitted Candidate.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Jun 2, 2015

    Thank you for raising this RFE. This sounds like a sensible usability improvement for the product. Status of the RFE is updated to Uncommitted Candidate.