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 Sep 17, 2012

Default behaivor of HLQ when sending from z/OS to distributed

The design of the product when sending files from z/OS to distributed is to lose the first HLQ. Probably they were thinking about this HLQ is the USERID, but in production environments it is not common. The RFE is to change this default behavior to create the file on distributed with the complete dataset name (including the HLQ). Probably the RFE could also be with a parameter in the source z/OS Thanks.

Idea priority High
RFE ID 26579
RFE Product IBM MQ
  • Guest
    Jan 7, 2022

    We recognise that this is a valid requirement. However it doesn't fit with our delivery plans for the next couple of years.

    As a result we are declining this Idea. While declined the Idea can still be voted, and commented, upon.

  • Guest
    Oct 15, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM MQ

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM MQ

  • Guest
    Oct 24, 2012

    I think we could have two approaches:

    A.- Setting an agent parameter HLQ=on/off for all the transfers that the agent transfers.
    B.- Option A + other parameter to specify a list of users that will avoid the default behavior of option A.

    I think it should be the best way of implementing it, but for this customer it should be fine just option A because for production agents on z/OS it is not required the HLQ of the userid. There is not any dataset that contains the HLQ of the userid because all of them are datasets with business data and the naming convention are business oriented.