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 Nov 16, 2011

When a tran abends in a region, CPSM should not route any tran of the same WLM tran group to this target region

Description: FI had observed that following an abend of a transaction in a CICS region, CPSM was still routing transactions with different ids to the CICS region. CPSM currently allows the 'Acceptable level of abend probability' and the 'Acceptable abend load threshold' to be specified on a WLMSPEC or on a TRANGRP definition. However, these values are taken into account on a transaction ID basis. So, if TRAN1 abends in CICS1, the abend compensation logic in CPSM's routing will ensure that another instance of TRANS1 is not routed to CICS1 as defined by the above mentioned probability/threshold values. However, other transactions (eg. TRANS2, TRANS3, etc.) may still be routed to CICS1. If we understand correctly, once a transaction abends in a given CICS region, FI would like to regard the region as unhealthy and route all transactions away from that region until the region becomes healthy again. To address this, we could add a check box to the WLMSPEC and TRANGRP definitions to indicate that once a transaction abends in a region, no transactions should be routed to that region until the region becomes healthy again.
Suggested Solutions: To address this, we could add a check box to the WLMSPEC and TRANGRP definitions to indicate that once a transaction abends in a region, no transactions should be routed to that region until the region becomes healthy again

Idea priority Medium
  • Guest
    Reply
    |
    Apr 26, 2016

    This requirement has been re-evaluated. Looking at current plans, it is not likely that this would be implemented in the next two CICS TS releases, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in twelve months time if you wish it to be considered 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
    |
    Jan 18, 2012

    The plan for the next release is full, but this will be marked as a candidate for future release beyond that.

0 MERGED

When a transaction abends in a region, CPSM should not route any transactions in the same WLM transaction group

Merged
When a transaction abends in a region, CPSM should not route any transactions in the same WLM transaction group to this region until the region is healthy again Customer had observed that following an abend of a transaction in a CICS region, CPSM ...
over 12 years ago in CICS Transaction Server for z/OS / Runtime 2 Not under consideration