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 11, 2014

Pool Directory Cycle Information

TPFUG_Req_Number: D08001S
ORIGIN DATE: March 25th, 2008
REQUIREMENT ABSTRACT

Provide functionality to display pool directory cycling history for any pool section by time and date range per CPU. This information can be used for problem detection, analysis, and trending.

REQUIREMENT DESCRIPTION

• At directory cycle time an item should be logged to a database that contains the directory numbers, the device section, the CPU the cycle was done on, and a timestamp of when the cycle occurred.
• The timestamp logged for the new item not only represents the time the new directories cycled in, but also implies the time the previous last in-core directories on that CPU of the same device section cycled out for any reason (cycle down, forced reorder, etc) and provide the "CYCLE OUT" code as a display parameter.
• Support a user defined retention parameter (maximum of 365 days) for storing the database online with the ability to identify the retention period by each pool section individually.
• Displays of this database information should exist that provide the following:
o Display details for one or more CPU's by section for a particular time range. Default values should exist for the device section, CPU (default to the CPU the entry made on), time range(default to today's date and from midnight to current time).
o Display totals only, the total # of directories that have cycled by pool section on one or more CPU's for the timeframe requested. Default values as described in the 1st display should be used for this display also.
o Given a specific pool file address as input display detail information about the directory it belongs to. This information should include the directory number, the timeframes the directory was in core and the CPU(s) it was in core on.
o Given a specific pool directory ordinal number, display a history of when the directory was used.
o Display the short term directory recycle time, the number of hours/minutes it's taking to cycle through all pool directories for a given section.
o Execution of file pool reallocations and file pool generations will clear pool directory cycling history table(re-initialize).



CRITICAL SUCCESS FACTORS

The time it takes to cycle in pool directories is not increased by any noticeable factor with this requirement implemented.


ALTERNATIVE SOLUTIONS

N/A

SOLUTION CONSIDERATIONS (required)

Idea priority Low
  • 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