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 Not under consideration
Workspace IBM HourGlass for z/OS
Created by Guest
Created on Feb 11, 2015

RELATED IDEAS

Avoidance of repettive HourGlass ACES scans in AGGELIG

This is a dramatic CPU-time reduction request.

HourGlass processing is controlled by an "ACES", a table in ECSA strorage. The table contains information on whether and how to change the local time during a TIME service call.

This is done by running through code in CSECT AGGELIG that scans in a loop through the whole ACES for every time call, i.e. eventually millions of times for the same TCB even though the result is always the same and even if no HourGlass time change is requested.

Suggested improvement:
Avoid repetitive scans of the ACES by storing the scan result somewhere and reuse it on subsequent calls for the affected TCB until the TCB ends or the ACES is refeshed.

Idea priority High
  • Guest
    Reply
    |     Dec 17, 2020

    Based on our current plans and priorities it is not likely that this will be implemented in the next 12 months and so it is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

  • Guest
    Reply
    |     Mar 1, 2018

    I recently sent the following suggestion about this RFE to Virgil Hein via mail and also want to have it documented here:

    I still believe that it might be worth to cache HourGlass changed time values on a TCB base.
    Your first objection was that you would need to have the ability to use a pointer in a TCB-related control block and the z/OS guys wouldn't want to donate one to you.
    However each TCB-instance can uniquely be identified by the TCB-Token. This is a token that is unique throughout the life of an IPL, i.e. if a TCB-address is reused in an ASID after a DETACH and ATTACH it would have a token different from all previous ones with the same TCB-address. The "TcbToken" service can be used to obtain the TCB-Token for a given TCB in a given address space. The TCB-Token is a 16-byte value and the last word consists of the TCB address! The TCB-Token is also stored in the STCB control block in the 16-byte field STCBTTKN.

    So if you cached for each ASID and TCB your changed time value along the TCB-Token, you could quickly do a TCB comparison, and if you found a TCB-match, a comparison of the current TCB-Token with the stored TCB-Token will immediately show you if you can use the cached value. You probably would want to use 64-bit common storage for this cache. The address of such a 64-bit cache could e.g. be stored in your in-storage ACES.
    If you calculated with 4000 ASID's, 100 TCB's per ASID, and 32 bytes per TCB it would cost us about 12MB that we happily would be willing to provide to save CPU-time.

  • Guest
    Reply
    |     Nov 19, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Enterprise Tooling
    Product - IBM HourGlass

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Tooling
    Product - IBM HourGlass

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.