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 Not under consideration
Created by Guest
Created on Nov 11, 2021

IBM MQ is preventing WebSphere Application Server (WAS) to be started in reusables ASIDs

In our business operation, we need to take down the WAS servers to make the user application unavailable at night. These stops (and later restarts) of the WAS servers are consuming the ASIDs in the systems they run and demanding frequent IPLs. We tried to start WAS in reusable ASIDs (REUSEASID=YES in the start command), but it ABEND 0D3. We were told by IBM Support that CLIENT (TCP/IP) connections between WAS and MQ, instead of BINDINGS (cross-memory) mode, avoid this situation.

Our request for IBM is that MQ is coded to address the issue below to WebSphere MQ connectors in all versions.

"Bindings mode WebSphere MQ connectors do not work properly in reusable address spaces. If you activate reusable ASIDs on your z/OS operating system, ensure that servers that are running with Message Listener Ports, as opposed to activation specifications, do not have the REUSASID=YES option on the START commands" https://www.ibm.com/docs/en/was-zos/9.0.5?topic=zos-reusable-address-space

With this capability, we are free to recycle WAS without worrying about running out of ASIDs and having to IPL our systems, even if we use BINDINGS mode.

Idea priority Medium
  • Admin
    Matthew Leming
    Jan 18, 2022

    In order to protect address space integrity, z/OS will not allow address spaces to be reusable if they make use of certain types of PCs, or if they connect to other address spaces which make use of those PCs. The MQ address spaces makes of use of these types of PCs as part of its core function so we can't implement this idea I am afraid.

    Some details on why this protection is necessary is here: https://www.ibm.com/docs/en/zos/2.1.0?topic=ra-coding-cross-memory-services-avoid-loss-asids-from-reuse

    As you say one option here is to use client mode connections to connect from WAS to MQ. Another option would be to stop the WAS applications over night but leave the WAS server running.