Skip to Main Content
Integration

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to ideasibm@us.ibm.com for resolution. For more information about IBM's Ideas program visit ibm.com/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.