This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 updateson 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
In order to isolate SSH jobs in their own subsystem, you must use the instructions documented in this article: http://www-01.ibm.com/support/docview.wss?uid=nas8N1014744
However, this requires that you start the SSHD with the /QOpenSys/usr/sbin/sshd command and cannot use the STRTCPSVR *SSHD command. STRTCPSVR *SSHD always starts SSH in the QUSRWRK subsystem.
Support should be added, probably as an SSH property/attribute, to specify the subsystem in which the SSH jobs should run. This could be similar to how FTP and SMTP allow the subsystem to be configured.
I have a system with interactive users (5250), as well as many users that access the system with SSH. In addition, I have the database servers. I want to isolate each type of work into their own subsystem for improved management and control of the workloads. I can easily do this for all servers expect SSH, since STRTCPSVR for SSH will always start the daemon in QUSRWRK.
Do not place IBM confidential, company confidential, or personal information into any field.