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 Not under consideration
Categories General ES
Created by Guest
Created on Aug 11, 2016

Support for Session ID caching in IMS Transaction Manager Resource Adaptor

We need IMS TM Resource Adapter to add support for TLS/SSL session reuse in order to reduce CPU consumption related to large numbers of full TLS/SSL handshakes.

When the IMS TM RA uses TLS/SSL to protect its connections to IMS on z/OS, it appears to not reuse previously established TLS/SSL sessions, even though the IMS server on z/OS supports session reuse through AT-TLS. Per the TLS protocol, it is the responsibility of the TLS client (IMS TM RA, in this case) to trigger session reuse by specifying the session ID of a cached TLS session on the ClientHello message. Since we have a large number of short-lived connections, every connection causes a full TLS/SSL handshake, which is computationally expensive. TLS session reuse would allow the majority of those connections to use abbreviated TLS handshakes, which will significantly reduce our CPU consumption.

The client is the one who should initiate session caching according to TLS V1.1 & TLS V1.2 RFCs, which are available here:
http://www.ietf.org/rfc/rfc4346.txt
Search for CACHE and you will find this explained on page 32 & 39
http://www.ietf.org/rfc/rfc5246.txt
Search for CACHE and you will find this explained on page 35 & 42. You may want to include these RFC numbers in the RFE.

Idea priority Urgent
  • Guest
    Reply
    |
    Oct 9, 2018

    Thank you for your interest in keeping IMS a vital and successful product. Software development has continuously evolved during IMS's lifetime, and so has IMS itself. We have kept pace with, adopted, and implemented many industry standard best practices within our organization, including Continuous Delivery, Design Thinking, and Agile.

    When choosing new features to add from the list of requirements in our backlog, we assess which will bring the most value to as many clients as possible and prioritize those.

    At this time, after reviewing this request for enhancement and assessing its potential value, we have decided to reject it. The reason we are rejecting RFE ID 92908 because the original issue has been addressed with connection pooling such that the number of SSL handshaking is significantly smaller when the connection is being reused.

    If you have any further questions, please let us know.

    Thank you for your continue support with IMS.
    Haley Fung - hfung@us.ibm.com