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 Future consideration
Workspace z/OS
Categories DFSMS HSM
Created by Guest
Created on Dec 11, 2019

Improve the accuracy of FRBACKUP Dump States by not setting initial state to FAILED

Description:
The Fast Replication Dump State value of 'FAILED' can sometime be a false negative. We have encountered circumstances where the dump has not failed,
but the dump state indicates it has failed.


How it works today in the customer environment:

An initiated FR BACKUP DUMP is marked FAILED until the state changes. The state is changed from FAILED when the first volume is successfully dumped.

How its current behavior affects the customer environment.

A FAILED state does not properly describe a Copy pool dump version this has been initiated but not processed. An example of this would be when a dump volume is waiting to be processed in a common dump queue, which is queued behind other volumes.

Idea priority Low
  • Guest
    Reply
    |
    Dec 16, 2019

    The requirement is understood and added to the backlog as an Uncommitted Candidate.
    For client reference, the rationale for setting the initial status to 'Failed' is to handle unexpected error conditions. Should an abend occur immediately after the task starts and HSM is not able to do further processing, the status is guaranteed to show the correct value.
    As soon as the first volume completes successfully, then the state is updated to 'Partial'.
    You are correct that in between the time that HSM initializes the state and the first dump completes successfully that the statue of 'failed' can be misleading.