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 z/TPF
Created by Guest
Created on Feb 21, 2013

STIM items scheduled on same minute boundary

after some research we found this was because of a peak in activity
scheduled from the STIM table.
This bottleneck is caused by the STIM table scheduling too many items
on the same minute boundary, this is most noticable after a long outage
when TPF is in 1052 state for more than one hour. When TPF reaches norm
state again most STIM items are now past date and must be rescheduled
again, this is done at the same time, so all 30, 15, 10, 5, 2 minute
items get scheduled on the same minute boundaries at 0 and 30 minutes.
Here is an example from our STIM table:
001 13:46* SMPL 01 ZDECB STAT ALL INCLUDE-NO PRE-MILS SORT-MILS
002 13:46* SMPL 01 ZSTAT U
003 13:46* SMPL 01 ZSTAT
004 13:46* SMPL 02 zttcp disp stats
005 13:46* SMPL 10 zhttp display
006 13:46* SMPL 10 zfdrs r st set-lprd_hur
007 13:46* SMPL 10 zosae dataflow
013 13:46* SMPL 30 ZMQSC DISP CHS-ALL
017 13:46* SMPL 30 zvfac flush recid e201
.
These 17 items are always on the 16th and 46th minute boundaries, this
PMR request is for a mechanism that avoids these groupings by
scheduling the items on different minute boundaries.
Either allowing the user to specify the boundary i.e. for an item that
is activated every 30 minutes the user can define a number 1-29, for a
60 minute interval 1-59 which identifies the exact minute boundary, or
alternatively the STIM could schedule each 30 minute one minute later
than the preceeding item and do the same for 15 minutes items etc..
This would help to distribute the load and reduce the peaks that we see
in data collection data.

Idea priority Medium
  • Guest
    Reply
    |
    May 22, 2020

    Although IBM believes this is a sound idea we do not intend to implement it in the foreseeable future due to other priorities.

  • Guest
    Reply
    |
    Oct 14, 2015

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

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - z/TPF

  • Guest
    Reply
    |
    Jun 29, 2015

    IBM still intends to implement this (it is an Uncommitted Candidate)

  • Guest
    Reply
    |
    May 20, 2015

    Please review PMR 57837,660,706 which highlights the problem of CREMC shutdowns due to more than 50 items on the Ready list, IBM concluded this was due to peaks in work load scheduled from the ZSTIM table.
    This enhancement is designed to remove those peaks, does IBM have any plans to implement this feature?

  • Guest
    Reply
    |
    May 20, 2015

    Please review PMR 57837,660,706 which highlights the problem of CREMC shutdowns due to more than 50 items on the RTeady list, IBM concluded this was due to peaks in work load scheduled from the ZSTIM table.
    This enhancement is designed to remove those peaks, does IBM have any plans to implement this feature?

  • Guest
    Reply
    |
    Jan 13, 2014

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - z/TPF
    Component - z/TPF

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - z/TPF
    Component - Runtime

  • Guest
    Reply
    |
    Mar 13, 2013

    In addition an option to balance the STIM items across I-streams would also help solve the clustering problem. Many of the enries in our STIM are display entries and can be done on any available I-stream, doing them all on I-stream 1 on the same minute boundary (as described earlier) creates a performance bottleneck and large spikes in the maximum CROSS list size.