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 Mar 14, 2013

RELATED IDEAS

CICS ENQ - adjustable delay time for re-checking resource available

For the CICS API command ENQ, create a mechanism for which the delay time could be adjusted when CICS re-checks the resource that is unavailable. Perhaps a new SIT parm value, ENQModel delay value, or the ENQ command. The 200 ms delay at times causes a backlog of tasks. It is our understanding that the global enqueue stack is not processed in the order they are created, causing older tasks to obtain the queue after newer ones.

Idea priority Medium
  • 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
    |     Jun 13, 2014

    This requirement is satisfied by CICS TS 5.2 which is generally available from June 13th 2014.
    Enqueue processing has been changed to use a first retry interval of 10ms and then all subsequent ones the retry interval is 100ms.

  • Guest
    Reply
    |     Apr 14, 2014

    This requirement is satisfied by CICS TS 5.2 which was announced 7th April 2014 with a planned general availability date of June 13th 2014. For more information see the IBM CICS Transaction Server for  z/OS, V5.2 announcement letter

    http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS214-107

    Enqueue processing has been changed to use a first retry interval of 10ms and then all subsequent ones the retry interval is 100ms.

  • Guest
    Reply
    |     Apr 9, 2014

    This requirement is satisfied by CICS TS 5.2 which was announced 7th April 2014 with a planned general availability date of June 13th 2014. For more information see the IBM CICS Tools for  z/OS, V5.2 announcement letter

    http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS214-107

    Enqueue processing has been changed to use a first retry interval of 10ms and then all subsequent ones the retry interval is 100ms.

  • Guest
    Reply
    |     May 23, 2013

    This is something we would like to address. In an attempt to get a suitable compromise the retry interval can easily be made variable, so that retries are more frequent initially and then back off to a longer interval once it's proving harder to get the ENQ. Simplest example of that would be a first retry interval of 10ms and all subsequent ones being 100ms. Thus if there's just two or three tasks contending, and each only holds the ENQ for something in the order of 5ms, the losing tasks will retry in 10ms rather than the 200ms today and likely succeed. If there are more contenders and multiple contenders in one region which is hogging, or the resource is held by each task for considerably more than 5ms, then the losing tasks in other regions will back off to 100ms retries.

    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.

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.