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.

Add a new idea Subscribe
Status Delivered
Workspace z/OS Connect
Created by Guest
Created on Mar 20, 2019

RELATED IDEAS

z/OS Connect API -> Transaction Tracing

Objective
To be able to identify performance degradation at a single API/transaction level in both CICS and IMS

Description
The business has an operational requirement to track every z/OS Connect API call which hits CICS / IMS DC (currently offered by the SMF123 data cut by z/OS Connect). However, they also need to correlate specific z/OS Connect API calls with the transaction/program that ran in CICS/IMS. This is for real-time monitoring and diagnostic purposes.

Technical Requirements
1) Generate a z/OS Connect API Correlation Token (unique to that specific API call)
2) Add that Correlation Token to SMF123 record
3) Flow Correlation Token to subsequent transaction systems (CICS & IMS Connect)
4) Add that Correlation Token to SMF110 record (CICS) and IMS Connect Log records

Idea priority High
  • Guest
    Reply
    |     Mar 27, 2020

    This requirement is addressed by z/OS Connect Enterprise Edition V3.0.30 / APAR PH19977:
    https://www.ibm.com/support/pages/node/3810447

    We have created a version 2 of the SMF 123 subtype 1 records to give you more detailed information about your API provider requests. These include details about the service provider and the System of Record (SOR), and also any request and response headers used.

    For further details see:
    https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/monitoring/smf_provider_v2.html

0 MERGED

Correlation between API calls and CICS transactions

Merged
Idem to RFFE ID 131148 (z/OS Connect API -> Transaction Tracing)
about 5 years ago in z/OS Connect 1 Delivered

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.