Skip to Main Content
Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Under review
Created by Guest
Created on Feb 5, 2026

IBM MQ Ansible for z/OS collection

Opening this IDEA for IBM to support native MQ modules as part of ibm_zos collections. 

Ansible collections are already available on distributed platform, but not on z/OS. Ansible is a great tool that would help automate different administrative tasks. 

IBM has provided that we can run MQ commands using the zos_operator module as part of ibm.ibm_zos_core collection, but this requires users to have access for console commands. This also requires custom tasks to read the output to validate if the command was successful or not. This makes the playbook larger, as for every oper command, we have to run an debug/fail task to validate the command output.

Some examples that would be useful modules:

  1. Check status of queue manager
  2. Run MQSC commands - the mqsc commands are provided either through file path / dataset name, or in the task yaml configuration. 
  3. Report correctly on the task states (OK - command ran, CHANGED - alter command ran and MQ object attribute changed, FAILED - for any failed CSQ codes)

 

 

 

 

Idea priority Low