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 Runtime
Created by Guest
Created on Nov 30, 2022

CICS & z/OS Connect Time inconsistent in report

When analyzing through CICS/PA a report of type ZCON we find discrepancies in the times that make it practically useless

On one side, CICS appears in Local Time, but the z/OS Connect show the time in UTC. Could this not be unified?

Also (obviating the time of difference for the reason given above) .... How is it possible that if the report shows that the StopTime of the transation in the SOR is 10 :42:39.273 it is indicated that "ZC Entry : 11:42:40.270499 SOR Sent : 11:42:40.271010" ?

As explain in the case, this is because each product uses a different macro that additionally runs over different processor types (one goes to ZIIP and the other to CP).

It seems incredible that today, that we are able to synchronize the times of all the elements of the network, within the same hardware this is impossible.

Idea priority Medium
  • Guest
    Reply
    |
    Jan 25, 2023

    Hi there,

    This has been looked at in the Salesforce case TS011498865, as it contains analysis and conclusion regarding CICS PA. If this needs addressing, please raise a z/OS Connect idea.

    Many thanks,

    Louisa Seers

  • Guest
    Reply
    |
    Dec 9, 2022

    Hi Jose,

    Thank you so much, the team have been sent the case number - so please feel to reach out if you need anything else!

    Louisa

  • Guest
    Reply
    |
    Dec 9, 2022

    OK Louisa

    I created the new case TS011498865

  • Guest
    Reply
    |
    Dec 9, 2022

    Hi there,

    Given that the case has been opened under z/OS Connect, the CICS PA team aren't able to respond to it and help you with your case - could you please open a case under CICS PA rather than z/OS Connect?

    Hopefully we can get your issue resolved quickly.

  • Guest
    Reply
    |
    Dec 7, 2022

    Hello.

    The case I opened (and in which the lab explains the reason for the discrepancy of the times between the two products) is TS011199515

  • Guest
    Reply
    |
    Dec 6, 2022

    Hi there,

    Thanks for opening an idea, looking into the support ticket and information that you've provided, it looks like there needs to be a support ticket opened with CICS PA to investigate this further. The development team need to verify the actual timestamps in both the z/OS Connect and CICS CMF records against what is being reported and a support ticket will allow you and the team to communicate.

    Hope this helps, and I will change the status to needing more information.

    Feel free to reach out if you have any further questions.