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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
There are a number of precautions DBRC takes prior to allowing this situation. An ALLOC record is useless for recovery if there isn't an older IC that can be used for the recovery base. There are warning messages that are put out indicating that there are no ICs for the DBDS. The user also has control over the age of the data that will be cleaned up by the CLEANUP command. With all of this protection if we encounter an ALLOC such as this, it is assumed to be a candidate for deletion. We have seen so many customer RECONs with obsolete records in them and the CLEANUP command is designed to take care of them.
Another alternative is to run CLEANUP on a copy of the RECON first and evaluate the output.
Dear Derek:
Thank you for submitting this IMS enhancement request.
After a comprehensive review, we regret to inform you that we have determined that at this time this request will not be a candidate for inclusion in an upcoming release because it is not consistent with the product purpose. Hence, we have rejected this request.
We appreciate your input to the IMS development team.
Sincerely,
Pat Schroeck