This is an IBM Automation portal for Cloud Platform 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
In order to achieve high availability in z/OS Connect, the product documentation (https://www.ibm.com/docs/en/zos-connect/zosconnect/3.0?topic=availability-sysplex-distributor) recommends use of a DVIPA to distribute workload between multiple LPARs. However, the proposed method using WLM only takes into account LPAR health/weighting and is not aware of the status of the z/OS Connect server and whether it is inoperable/degraded. This behaviour, whilst not ideal, is expected as the DVIPAs placed in front of z/OS Connect use BASEWLM as their distribution method.
Ideally, we would like the option to specify SERVERWLM on these DVIPAs. This would align with what has been implemented for IMS Connect (https://www.ibm.com/docs/en/ims/15.3.0?topic=connect-ims-support-zos-sysplex-distributor). Our understanding that that this would require z/OS Connect to send a numeric “server health status” report to WLM on startup and upon server health changes.
We understand that this feature would likely require customer involvement in testing/validation as calculating the server health will need to use multiple metrics at varying weights. Additionally, these metrics will need to be tolerant to business failures (such as transactions being deliberately stopped in IMS for change control) and lower the health score based on infrastructure failures (to eliminate false positives).
If you require any further detail, please let me know!
Do not place IBM confidential, company confidential, or personal information into any field.