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 Jul 31, 2018

Enhance the looping catastrophic monitor

The looping catastrophic monitor aborts restart after recovery log processing in restart. This is before tape restart and IPC restart. Although it's likely that a looping catastrophic is the same dump, aborting before tape restarts means the last dump may not have been written to the tape yet from the DBA. It also makes swapping out tapes to post process the dumps more operationally unusual (ZTOFF vs ZTPSW). Aborting before IPC restart may cause unnecessary issues for LC systems.

If possible, looping catastrophic detection should alllow tape restart and, for LC systems, IPC restart to complete before aborting restart. Clearly if the looping catastrophic occurs before then, this is not possible and restart must be aborted as early as it is now.

For non LC customers, forcing dumps in looping catastrophic situations to write to tape instead of the DBA might also ensure that if the catastrophic was not the same dump each time, that the last dump was written out to tape before restart is aborted. This doesn't solve any problems for LC customers though.

Idea priority Medium
  • Guest
    Reply
    |
    Feb 2, 2022

    Based on the results of the TPFUG ballot, priorities and resources, IBM does not intend to implement this in the foreseeable future.