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.

Add a new idea Subscribe
Status Delivered
Workspace CICS Transaction Server for z/OS
Categories Runtime
Created by Guest
Created on Jul 10, 2012

RELATED IDEAS

High CPU in DFHXMAT when the current number of TCLASS'd tasks approaches 99,999.

Each task that is attached is assigned a task number even if it is just queued in a TRANCLASS. CICS uses just 99,999 task numbers. As the current number of attached tasks approaches 99,999, DFHXMAT spends much time on the attach of each task figuring out what task number to assign.
.
.
The customer uses a TRANCLASS to prevent a flood of a certain type of work from affecting the other transactions in this CICS region. But because of the way trannums are allocated, a large flood of work that collects in TRANCLASS does affect other tasks that aren't in the TRANCLASS (since every attach suffers the high CPU cost of allocating a new trannum.)

Idea priority Medium
  • Guest
    Reply
    |     Apr 12, 2024
    The high cpu problem is solved in CICS TS 6.2 which has been announced and will GA June 14th 2024.

    See Announcement letter https://www.ibm.com/docs/en/announcements/AD24-0164
  • Guest
    Reply
    |     Aug 17, 2022
    CICS Development: This is something we would like to address. The Idea is being moved into 'Planned for Future release' status.
    Please note:
    IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion
  • Guest
    Reply
    |     May 5, 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.

    In the longer term the problem of too many tasks in the system is to be addressed by flow control mechanisms the first part of which was implemented in CICS TS 5.3. Stopping too many tasks coming in the system will avoid the problem of thrashing trying to assign a task number.

  • 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
    |     Apr 17, 2015

    We suffer from the same issue. Furthermore, when activating the TCLASS purge mechanism all TCLASS queued transactions get released for AKCC abend simultaneously, thus leading to MAxtask condition. So we getting punished twice for having a high number of tasks TCLASSed. First with the high CPU and then with a maxtask stall stall while all the purged tasks get abended with an AKCC.

    Zalman Einhorn. Broadridge Financial Services.

  • Guest
    Reply
    |     Apr 17, 2015

    We suffer from the same issue. Furthermore, when activating the TCLASS purge mechanism all TCLASS queued transactions get released for AKCC abend simultaneously, thus leading to MAxtask condition. So we getting punished twice for having a high number of tasks TCLASSed. First with the high CPU and then with a maxtask stall stall while all the purged tasks get abended with an AKCC.

    Zalman Einhorn. Broadridge Financial Services.

  • Guest
    Reply
    |     Apr 17, 2015

    We suffer from the same issue. Furthermore, when activating the TCLASS purge mechanism all TCLASS queued transactions get released for AKCC abend simultaneously, thus leading to MAxtask condition. So we getting punished twice for having a high number of tasks TCLASSed. First with the high CPU and then with a maxtask stall stall while all the purged tasks get abended with an AKCC.

    Zalman Einhorn. Broadridge Financial Services.

  • Guest
    Reply
    |     Apr 17, 2015

    We suffer from the same issue. Furthermore, when activating the TCLASS purge mechanism all TCLASS queued transactions get released for AKCC abend simultaneously, thus leading to MAxtask condition. So we getting punished twice for having a high number of tasks TCLASSed. First with the high CPU and then with a maxtask stall stall while all the purged tasks get abended with an AKCC.

    Zalman Einhorn. Broadridge Financial Services.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.