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 Future consideration
Workspace z/OS
Categories JES2
Created by Guest
Created on Nov 11, 2022

Allow the number of JES2 NODES to be reduced without a cold start

We have a number of JES2 environments which have evolved over time. Decades ago, someone decided that it would be useful to define the NODENUM on the NJEDEF init parm as 9999, meaning we now have many systems defined with 9999 possible nodes. We actually only need 49 today.


The manual states that it's possible to increase the NODENUM parameter with a warm start, but to decrease it requires a cold start. As several of these JES2 environments are MAS environments in production, it is not feasible to perform a cold start without severe disruption (and the potential of bringing unexpected parameters into action - see idea ZOS-I-3480).


I would like a way to reduce the number of defined nodes, either via a warm start or an operator command.


This would also reduce the CPU required by some tools that scan all nodes to see if they are active or not - and I would think reducing the node numbers would free up storage used by JES2.

Idea priority High