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 Oct 13, 2015

Protect HSM expiration functions in IPL date error situation

We had a recent experience where one of our systems was IPL'ed to a future date. Unfortunately, RMM and HSM recycle processing ran during this time resulting in data being deleted prior to the true expiration date. We are able to change the RMM IPLDATE parameter that will allow us some protection from this happening again to RMM. However, that same protection is not available in HSM. We would like HSM to implement something very similar to RMM's IPLDATE parameter. This would allow some level of protection against HSM expiring a large number of datasets should this happen in the future. We are considering implementing some minimal protection by making HSM's start dependent on RMM. But, that control has the potential to slow down initialization of HSM in all normal IPL situations.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 14, 2015

    Creating a new RFE based on Community RFE #78295 in product z/OS.