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 Not under consideration
Created by Guest
Created on Jan 16, 2017

STP ETS scheduled syncronization feature request

To keep multiple STP networks (at different geographical locations) synchronized in parallel to any adjustments in time from the ETS (External Time Server) we need to be able to specify the occurrences that the PTS quarries the ETS.

o This can either be specified by the customer in the Sysplex Time panels on the SE or built into the microcode.

o An example would be “Every hour at **:30 (30 mins past the hour) query the ETS & begin any steering required.

o The issue is not the fact that STP steers the 1 second offset in time over a period of roughly 7 hours; the issue is more with our STP networks starting to steer time at different points in an hour since they all had the CTN configured at different times.

o With active-active applications increasing in our environment that reach across SysPlex boundaries at multiple sites (so multiple STP networks), the requirement to keep time steering uniform is critical.

Idea priority Medium
  • Guest
    Reply
    |
    Sep 21, 2017

    Meeting was held with JPMC on 9/18. Due to new regulations we reached agreement for JPMC to instantaneously change a leap second change for both CTNs.

  • Guest
    Reply
    |
    Jun 19, 2017

    Thank you for your input. This request is a candidate for a future release.