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 System
Created by Guest
Created on May 23, 2017

TYPE56FA TLS Transaction Level Statistics Log Record does not show the actual Input Queue Time for PtP switches

The actual Transaction Input Queue Time can not be taken from TYPE56FA Log Records for PtP Messages processing.
Field TPINUTC, that Customer wants to subtract from field TPSTARTU to get the Input Queue Time, is in fact the Timestamp when the first Transaction of a Program-to-Program chain was enqueued.
This means that it is impossible to have the correct transaction input queue time in case of p-t-p switch solely from a TYPE56FA TLS Transaction Level Statistics Log Record.

Other external at a charge Tools like IMS Performance Analizer, that uses a different approach to calculate the transaction Input Queue Time, should be used.

Also a flag is missing in the TYEP56FA Log Record to show the Transaction was generated from a PtP Message switch (TYPE03 Inpout Log Record) rather than it came in from the network (TYPE01 Input Log Record).

Idea priority High
  • Guest
    Reply
    |
    May 21, 2020

    Hi,

    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.

    After reviewing our prioritized backlog, we have decided to reject this RFE as we will not be able to get to this in the near future. We have other higher priority items that we are focused on.

    We appreciate your input to IMS, and we hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of IMS.

    Thank you.

  • Guest
    Reply
    |
    Feb 5, 2018

    Hi,

    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.

    After reviewing this request for enhancement and assessing its potential value, our decision is to add this item to our backlog. Items in our backlog are expected to be delivered within the next 18 months. We reserve the right to re-prioritize our backlog items as new requests come in. This helps ensure that we are constantly focused on providing the best value to all of our clients.


    Have a great day!
    Daphne Isom - dsteele4@us.ibm.com

  • Guest
    Reply
    |
    Dec 5, 2017

    Hi,

    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.

    We are currently reviewing this item for consideration, and we plan to seek additional feedback from other IMS clients. 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 our ability to deliver within the next 18 months and prioritize those.

    You will automatically be notified of ongoing progress associated with this RFE.

    Have a great day!
    Daphne Isom - dsteele4@us.ibm.com