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).
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.
The telnet protocol for a printer session does not have an associated user profile. Therefore, it is not possible to use an authorization list to restrict users from starting a printer session for a particular printer device. The server-side steps for starting a printer session could be modified to prevent ALL printer session from starting a print writer. Starting the print writer would require a separate action (Start Print Writer (STRPRTWTR) command) using some other authenticated connection (such as a display session). This disruptive design change would impact print procedures currently in use by customers. Would you and those following this IDEA run with that restriction in place?
Best practice documentation describing how to protect print output with the existing behavior is being drafted. The primary mitigation is to create spooled files in an output queue that is not located in the QUSRSYS library. When these spooled files are to be printed using a printer session, the printer session must be started and then the print writer must be changed to use the output queue where the spooled files are located. This will enforce that the user changing the print writer is authorized to the output queue and spooled files.
IBM Power Systems Development