Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Not under consideration
Workspace z/OS
Categories USS
Created by Guest
Created on Sep 14, 2023

Provide more granular control over the maximum number of processes limits

Currently, the maximum number of processes is controlled by the MAXPROCSYS value in BPXPRMxx. There are warnings not to set this value too high as each process has the potential to consume its own address space. This means that MAXPROCSYS should not be set much higher than the MAXUSER otherwise too many processes might cause an ASID shortage. Tying MAXPROCSYS to MAXUSER is very limiting as setting MAXUSER too high can lead to other resource shortages (SQA, ESQA, etc) when that many address spaces run simultaneously. This is a major limitation for processes that do not require their own address spaces such as CICS socket connections and limits modernization efforts. Separate limits for processes that do and do not require their own address spaces would allow for more processes to be created without the need to increase MAXUSER to unreasonable values.

Idea priority Urgent
  • Guest
    Reply
    |
    Jan 26, 2024
    Accounting of processes and the associated system limits are tied up with the UNIX standard and therefore difficult to change. The proper approach is to use threads rather than processes in cases like this.