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.
An option to consider might be to define a second session for each session with an alternate name. For example one named TSOwith and another named TSOwout.
Hello IBM, the main reasons for using an application without an initial dialog, is to change some Application Parameters as the TSO Logon Procedure Name or to use a second UserId in Sysview ...
A current Problem is also, to allow the user to login with PassPhrase or Password, if destination Application is not yet set to PassPhrase support but the Supersession is system already done this.
A initial dialog test is done in our sandbox systems every time before we go to production.
kind regards Svend
Thank you for your request. After careful consideration we have declined this request. A practical and reasonable alternative exists: For instance: While the dialog is under development and may be problematic two changes can be added. First: In KLSVSELA, add a test refresh before the VSSALLOC to be sure the dialog is valid. Second: Within the initial dialog, add logic like “If &VSSUSER NE diagdev return” to prevent its execution while the developer named diagdev is still testing it.
Thank you for the enhancement submission. We will send this to development for review.