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.
This RFE is satisfied by CICS TS 5.3 which is generally available from December 11th 2015.
The following new performance class counters have been addedto resolve this RFE:
460 (TYPE-A, 'TSGETSCT', 4 BYTES)
Number of temporary storage GET requests from shared temporary storage issued by the user task.
461 (TYPE-A, 'TSPUTSCT', 4 BYTES)
Number of temporary storage PUT requests to shared temporary storage issued by the user task.
In addition we have also added the following counts to the TS resource class records so users can determine gets and puts by a task to shared TS to individual queues too:
MNR_TSQUEUE_GET_SHR (TYPE-S, 8 BYTES)
The elapsed time that the user task waited for completion of GET requests to shared temporary storage, issued by the user task for this temporary storage queue. The count part of this field (the low-order 24 bits) contains the number of GET requests to shared temporary storage issued against the temporary storage queue. For more information, see Clocks and time stamps and Transaction wait (suspend) times.
MNR_TSQUEUE_PUT_SHR (TYPE-S, 8 BYTES)
The elapsed time that the user task waited for completion of PUT requests to shared temporary storage, issued by the user task for this temporary storage queue. The count part of this field (the low-order 24 bits) contains the number of PUT requests to shared temporary storage issued against the temporary storage queue. For more information, see Clocks and time stamps and Transaction wait (suspend) times.
MNR_TSQUEUE_GET_SHR_ITEML (TYPE-A, 4 BYTES)
The total length of all items obtained from this shared temporary storage queue.
MNR_TSQUEUE_PUT_SHR_ITEML (TYPE-A, 4 BYTES)
The total length of all items written to this shared temporary storage queue.
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
The following new performance class counters have been addedto resolve this RFE:
460 (TYPE-A, 'TSGETSCT', 4 BYTES)
Number of temporary storage GET requests from shared temporary storage issued by the user task.
461 (TYPE-A, 'TSPUTSCT', 4 BYTES)
Number of temporary storage PUT requests to shared temporary storage issued by the user task.
In addition we have also added the following counts to the TS resource class records so users can determine gets and puts by a task to shared TS to individual queues too:
MNR_TSQUEUE_GET_SHR (TYPE-S, 8 BYTES)
The elapsed time that the user task waited for completion of GET requests to shared temporary storage, issued by the user task for this temporary storage queue. The count part of this field (the low-order 24 bits) contains the number of GET requests to shared temporary storage issued against the temporary storage queue. For more information, see Clocks and time stamps and Transaction wait (suspend) times.
MNR_TSQUEUE_PUT_SHR (TYPE-S, 8 BYTES)
The elapsed time that the user task waited for completion of PUT requests to shared temporary storage, issued by the user task for this temporary storage queue. The count part of this field (the low-order 24 bits) contains the number of PUT requests to shared temporary storage issued against the temporary storage queue. For more information, see Clocks and time stamps and Transaction wait (suspend) times.
MNR_TSQUEUE_GET_SHR_ITEML (TYPE-A, 4 BYTES)
The total length of all items obtained from this shared temporary storage queue.
MNR_TSQUEUE_PUT_SHR_ITEML (TYPE-A, 4 BYTES)
The total length of all items written to this shared temporary storage queue.
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 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.