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).
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.
Hi
Last time I installed z/OS 2.5 all datasets was defined with an Alias but not this time with install of z/OS 3.1.
the answer I got from case TS014843200 was:
Its working as designed. Data sets which can be referenced using the volume, like PDSes identified by DDDEF entries, purposely do not get a data set alias with the temporary catalog alias prefix. Whether SMP/E runs from the driving system or the new target system, will be able to find the correct data set by using the VOLUME subentry in the DDDEF entry. Data sets which must be referenced through the catalog, such as VSAM, zFS, or SMS-managed data sets, do get the temp cat alias prefix data set alias to ensure the proper data set is referenced whether from the driving or target system.
Before APAR PH49385 (HSMA244 = UI83645, HSMA254 = UI83644) SM did create data set aliases for all data sets
This has worked fine before as long as I can remember and for us it's essential to have Alias for all datasets delivered in the ServerPac, now I have to define them myself!
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.