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 1, 2020

RELATED IDEAS

Purge CDBT txn

System: CDBT txn
Actor: Purge CDBT

Ability to "PURGE" CDBT txn.

Situation arises when IMS is failing and several CICS regions simultaneously issue CDBC DIS IMM to "failing" IMS.
IMS appears to only handle a set number DISCONNECTS from CICS. This results in 1 or more CICS regions having a CDBT (DBCTL Terminate) suspended in DLSUSPND state.

The only known ways to remove this state is either:
1) Issuing IMS commands - which there is no point when IMS is failing.
2) Recycle CICS.

Neither option is acceptable when attempting to have/incorporate High Availability (HA) by switching DBCTL CICS from Primary IMS ("failing") to Secondary IMS ("alternate").

To avoid CDBT in DLSUSPND state when executing numerous CDBC DIS IMM commands is to wait for DFS627I (as instructed by IMS/L2). Unfortunately, DFS627I can take anywhere from 25+ seconds depending on machine speed and IMS internal clean-up before switching can commence.

We have through-out this HA project been able to switch to Secondary IMS well before Primary IMS actually ends. In a High-processing environment - this speed could be the difference of having issues with 1 or 2 CICS regions as opposed to multiple CICS in a CICSplex as they wait for DBCTL CICS regions to process "their" txns and free up resources.
Unfortunately, we have had numerous situations where we experience 1 or more CICS with CDBT in DLSUSPND state. Recycling CICS (our only option) causes further delays.
Staggering the switching with 6 CICS regions at a time apppeared to work - but again we have encountered the odd time where we have a CICS region with a CDBT in DLSUSPND and thus this method is "deemed" unreliable.

If "PURGE" was available - we could use DFS3896I as the trigger, proceed with the DISCONNECTion and when a CICS has CDBT in DLSUSPND state - PURGE that task and either continue to re-issue DISCONNECT or switch to Secondary IMS.
The time between DFS3896I (issued immediately after IMS failure detected) and DFS627I is app. 25+ seconds.

Idea priority High
  • Guest
    Reply
    |     Jun 17, 2022
    Support for this is provided in CICS TS 6.1 which is generally available from 17th June 2022.

    For more information see https://www.ibm.com/docs/en/cics-ts/6.1?topic=whats-new
  • Guest
    Reply
    |     Apr 5, 2022
    Support for this is provided in CICS TS 6.1 which is announced today April 5th and will GA June 17th 2022.

    See Announcement letter https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS222-092/index.html&request_locale=en
  • Guest
    Reply
    |     Jul 24, 2020

    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
    |     Jul 8, 2020

    The reason purge and forcepurge of transactions is not allowed if they have active threads in IMS DBCTL is because there is a high likelihood of bringing down IMS DBCTL if you pull the thread out. However in this case, IMS is terminating anyway, so it is worth investigating allowing purge of the shutdown transaction CBDT.
    This is a candidate for a future release

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.