Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 Future consideration
Workspace z/OS
Created by Guest
Created on Oct 31, 2022

Add SMF119AP_TTStatus to SMF119 Subtype 1 Connection Init

Add the field SMF119AP_TTStatus to the SMF 119 Subtype 1 Connection Initialization record. This field was already added to the subtype 2 - termination record, but should also exist in the init record. This information is known to the system at connection setup so should be technically possible.


Our use case is for realtime investigation using SMF data spooled to a Splunk instance. When there is a connection spike we consult this dashboard to find out where the connection spike occurred and investigate if this is abnormal usage. We filter the alerts on active vs passive (client vs server) connections and we are unable to do this filtering for init records as the data for this field is missing. This forces us to evaluate connection initiation spikes based on termination data that may not be present if the connections in question haven't ended. The init records would provide more accurate data for this investigation.

Idea priority Medium