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 Feb 28, 2022

JAVA and .NET MQ API should return this same correct output.

If MQ queue manager exists on iSeries platform and programmer done some query on pcfResponse object getStringParameterValue() function in JAVA returns good ASCII translated output and this same implementation in .NET returns bad output incorret decodded from EBCDIC. Problem is in differences in implementation PCFMessageAgent class on Java versus .Net.

Idea priority Medium
  • Guest
    Mar 9, 2022

    Does IBM MQ Explorer use the REST API? I do not think so. REST is lame.

  • Admin
    Mark Taylor
    Mar 8, 2022

    The .Net PCF classes were never a formally documented or supported interface. While we know that a number of people used them, this was never a product recommendation. Instead, we suggest that people use the REST admin interface as a fully-supported cross-language mechanism.