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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
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
This requirement is satisfied by CICS TS 5.2 which is generally available from June 13th 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
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
The ability of allowing an expiry interval in minutes, but not seconds, is something we would like to address. It would not go as granular as one minute, but CICS would round up to a multiple of minutes. Ten minutes may be an acceptable minimum without putiing undue overhead on the system.
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.
IBM is reopening this requirement
This requirement is being rejected as we do not believe that an expiry interval of seconds is sensible. Bad applications should be fixed to cleanup TS queues. We will however consider RFE 28051 which is requesting a minimum interval of less than an hour. Perhaps a minimum of 30 minutes may be possible although there is still a concern about performance.
Hi Mauricio,
Please can you give more information. Is this a rogue application that is putting a large number of items to a queue, or a small number of very large items ? The EXPIRYINT is really there to cleanup stale data rather than police rogue applications.
Thanks a lot for your update. Customer agree with your explanation, including about the handle concerns that a well application program code should have. However, despite the TS queues are now above the bar, they already have had problems with TSMAINLIMIT storage. The approach is in order to give more control to the CICS support team to administrate this resource, to prevent bad usage of TS queues that, unfortunately, can happen. Actually, besides the granularity of EXPRYINT, he also asked if it is feasible some new "limit configuration fields" like a expiration time to TS queues that are "currently in use" and a "maximum number of items". Best regards.
I would be interested to know why the customer wants to specify this cleanup interval on a granularity of minutes and seconds. No other cleanup interval in CICS can be specified to this level. The idea of the TS queue cleanup task is to ensure that TS queues are not left unused in the system for long periods. Now that the TS queues are above the bar, storage for them should not be a problem and a 1 hour minimum cleanup scan should be adequate. The cleanup task is a "back stop" to clean up queues if badly written application programs do not clean up queues properly. Ideally, application programs will be well written and will handle their TS queues properly so the cleanup task should never need to delete any queues at all.
Please can you explain the scenario of interest to the customer in more detail?