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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
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.