Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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
Categories Runtime
Created by Guest
Created on Dec 23, 2014

Routing algorithm should be able to be customized

In BOC, they have 16 AOR regions. However, due to DB2 timeout, 14 AOR regions got transaction dump, and no new workloads are routed to those AOR regions. Most of the transactions are routed to the 2 AOR regions, and quickly the 2 AOR regions are in MXT condition. From customer's perspective, transaction dump don't have much bad effect to their system. If possible, they would like to exclude the transaction dumping from the unhealthy factors, so that the 2 AOR regions won't get MXT.

Idea priority Medium
  • Guest
    Reply
    |
    Dec 14, 2016

    We have assessed this requirement. We have no current plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

  • Guest
    Reply
    |
    Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server

  • Guest
    Reply
    |
    Mar 31, 2015

    This is a candidate for inclusion in a future release, ie to change the weightings so that transaction dumps are weighted separately from system dumps so the regions become undesirable but it is still very possible for their weighting to be surpassed by a heavily loaded region before it gets to MXT.

    As a workaround for this today, the customer could consider decreasing their READRS, gradually maybe even down to 10ms (or whatever response time can be tolerated - this could be worked out by looking at their peak TPS rate vs MXT). We would suggest they do this incrementally and keep an eye on the CF load as they do this so they don't overwhelm the CF with reads.

  • Guest
    Reply
    |
    Jan 20, 2015

    Please see my input below:
    Q: Could we find out a little more about the system configuration please?
    A: BOC has 4 LPARs, 8 TORs and 16 AORs. They used DB2 as well.
    Q: Are you running Sysplex Optimised WLM and/or WLM abend compensation?
    A: Yes. BOC is running Sysplex Optimised WLM, but no WLM abend compensation.
    Q: How are the regions split between CMAS and LPAR?
    A: BOC has 4 LPARs. One CMAS region, 2 TOR regions and 4 AOR regions are running on each LPAR.
    Q: Did work route back into the other AORs after the 2 AORs hit the MXT limit?
    Was work in the 14 AORs continuing to abend?
    A: After the 2 AORs hit the MXT limit, CPSM continue routing work to these 2 AORs, since TOR haven't got the latest information of the 2 AORs (READRS=200ms). Because the abend is caused by the purge operation performed by system admin, so no more abend after the transaction dump.

  • Guest
    Reply
    |
    Jan 14, 2015

    We have some questions. Please could you add a comment with answers to the following questions:
    Could we find out a little more about the system configuration please?
    Are you running Sysplex Optimised WLM and/or WLM abend compensation?
    How are the regions split between CMAS and LPAR?
    Did work route back into the other AORs after the 2 AORs hit the MXT limit?
    Was work in the 14 AORs continuing to abend?