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 Nov 3, 2017

Provide ability to 'smartly' purge transactions performing 'must complete' activity

Customer has a large environment with many thousands of DB2 transactions per minute, and relies upon vendor monitoring software to effectively handle the purging of transactions that exceed criteria (TMON in this case, but this would apply to Omegamon for CICS as well). CICS provides the ability to PURGE transactions, which is utilized by the monitoring software.
.
CICS allows the issuance of DB2 commands through the DSNC transaction, but this can only be run from a terminal and with DB2 privileges.
.
The current Best Pratice for purging transactions that are in DB2, particularly those that are in SYNCPOINT processing, is to first issue the DB2 CANCEL THREAD command, and then to safely purge the transaction within CICS Transaction Server. This is to avoid purging during a "must
complete" activity in DB2. This is a multistep process that the customer feels could be greatly improved by providing all functionality within CICS, such that his monitoring product could make the decision to PURGE, which CICS would handle safely. Leaving that to the monitoring products themselves would require coordination and potential timing issues when a task enters SYNCPOINT.

Idea priority Medium
  • Guest
    Reply
    |
    Dec 14, 2018

    This RFE is also satisfied by CICS Transaction Server for z/OS V5.5 which is GA today 14th December 2018.

  • Guest
    Reply
    |
    Oct 2, 2018

    This RFE is also satisfied by CICS Transaction Server for z/OS V5.5 which is announced today 2nd October 2018 and which has a planned availability date of 14th December 2018.
    For more information see the CICS TS V5.5 announcement letter https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS218-352/index.html&request_locale=en

  • Guest
    Reply
    |
    Jul 30, 2018

    The SET TASK command has been enhanced such that CICS processing of task purge or forcepurge requests will attempt to cancel active Db2 threads used by CICS tasks that are being purged or forcepurged.

    If CICS detects that the task being purged or forcepurged has a thread active in Db2, it will issue a Db2 cancel thread command to cancel the request in Db2 before initiating the purging of the CICS task. This enhancement ensures that the purge does not cause problems for Db2 and that the Db2 updates are safely backed out.

    To cancel the Db2 thread in Db2 used by the task being purged or forcepurged, CICS uses a Db2 IFI command to issue the cancel thread command. This IFI request uses a command thread defined as part of the DB2CONN. The ID passed to Db2 needs to have the relevant authority to issue cancel thread requests; therefore, you should review the COMAUTHTYPE or COMAUTHID settings of the DB2CONN. Processing of the purge or forcepurge request will continue even if the cancel thread request is unsuccessful.

    This capability is made available on CICS TS 5.1 through 5.4 with APAR PI98569. Note: This capability also requires APAR PI92893 on DB2 Version 11 or higher.

  • Guest
    Reply
    |
    Jan 17, 2018

    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
    |
    Nov 27, 2017

    This is a candidate for a future release.