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 Delivered
Categories Runtime
Created by Guest
Created on Jun 12, 2014

CICS should be aware when a protected DB2 thread is canceled

Customer has an automated process to cancel CICS tasks that exceed 20 CPU seconds. To follow the procedures recommended in CICS manuals, first a DB2 CANCEL THREAD is issued and then the CICS transaction is purged. When the DB2 thread in use is defined as protected, and the transaction ends by itself as soon as this mechanism detects it, the DB2 CANCEL thread works OK, the transaction purge fails (because transaction ended in the meantime), and the next transaction in CICS that uses the same protected thread, abends AD2S.
The request in this RFE is to allow CICS to be aware that the DB2 thread that it's trying to reuse has been canceled in DB2, and so repeat all the thread initial process to allow the next transaction to use it correctely without abending.

Idea priority High
  • Guest
    Reply
    |
    Dec 11, 2015

    This RFE is satisfied by CICS TS 5.3 which is generally available from December 11th 2015.

    CICS is now aware if a DB2 thread that it is trying to reuse has been canceled in DB2, and ensures that a subsequent transaction can use that thread correctly.

  • Guest
    Reply
    |
    Oct 6, 2015

    This RFE is satisfied by CICS TS 5.3 which was announced on October 5th 2015 with a planned general availability date of December 11th 2015.
    For more information see the announcement letter http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS215-363

  • 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
    |
    Jul 16, 2014

    This is something we would like to address. The RFE 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
    |
    Jun 17, 2014

    Yes it is agreed this would be an useful enhancement. It is a candidate for inclusion in a future release.