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 2, 2023
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit MESNS-I-573 Add a function on the Mainframe MQ MQS application to include display of MQ Parms.

Remove requirement for ZPARMs assembly skills Merged

Convert the MQ ZPARMs from an (assembled) macros (to a (non-assembled) set of options that are contained in a parameter dataset, like other IBM products (for example: RACF and SDSF). 

It is useful because it will increase productivity, eliminate the need for assembler skills, and improve the overall accuracy of settings that are currently coded in assembler. 

The people that would benefit from it include: Product installers and product administrators (changing parameters, etc.).  Other benefits would be providing simpler “risk” control to the parameters in ZPARM. 

It should work like this: 

-        Provide a dataset where ZPARMs reside (that does NOT need assembly)

-        The “dataset” should be opened, read and used by the appropriate MQ task (Queue Manager, Channel Initiator, etc.) when the MQ task starts.

-        (longer term), provide a method to dynamically update the new ZPARMs values (using the “dataset”) without restarting the appropriate MQ tasks.  (perhaps, something like this: REFRESH QMGR TYPE(ZPARMs))

-        Documentation should be added for how to protect the new dataset, so that only MQ tasks and product support has access to update the options.


Examples of other IBM products (that have converted away from assembled parameters) include: 


RACF: (which were previously defined by assembled parts) ICHRDSNT and ICHRRNG 

note: This would eliminate the sample JCL (SCSQPROC(CSQ4ZPRM)) and the steps required to assemble/link edit.

Idea priority Medium