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.
I just realized that this is not under consideration.
if there is a difficulty in validation what would work to avoid activation of lnklst dsn alias after IPL...
currently, if no changes to this validation. LNKLST activation failures might occur during IPLs.
Thanks,
Ed
Hi, I might need more time on how to transfer this RFE to z/OS.
I will need your help to do this transfer as I have never transferred ideas of this sort.
Thanks,
Ed
Thank you for submitting this RFE. We have reviewed your request and determined that it is a request for the z/OS team. Please resubmit your request to their queue. In the meantime, here is a link that may assist you: https://www.ibm.com/docs/en/zos/2.5.0?topic=lpa-using-lnklst-statement
Actual incident scenario:
After the alias DSN failed during IPL, sysprog/s will attempt to correct this with a dynamic setprog activation using the same alias which will work then but the problem will re-occur on the next IPL.
The purpose is to avoid re-occurrence of the problem by failing "ALIAS DSN" on any activation (dynamic or at IPL). A smooth IPL & automated startups of subsystems would be ideal to reduce downtimes & manual interventions.