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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
The lack of a logoff timer, now IBM are making more options available in view, can mean that a disconnected HMC user will hold the SE and prevent other access including a CE wishing to perform a Service Task. This happened recently and delayed a repair action slightly. Yes the userid could have been logged off with someone using acsadmin authority but that may not readily have been available and equally as in this case the people involved didnt want to just force a logoff.
I do agree with the Guest post above that this would be an option to enable (or not) and if selected a timer would be set which would happen after the disconnect timer had activated.
Ideally any logoff timer once they are disconnected would be defined per user / template, with the capability to set to 0 to prevent any forced logoff.