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 BCP_SMF
Created by Guest
Created on Aug 29, 2023

Avoid arbitrary MEMLIMIT=NOLIMIT assignments to REGION=0M jobs

Our IEFUSI->SMFLIMxx conversion was halted by an unpredictable design choice, which is: An implicit MEMLIMIT=NOLIMIT default when REGION=0M that *overrides* the explicit MEMLIMIT default in SMRPRMxx.

This creates problems, such as: If a user does not specify MEMLIMIT=NOLIMIT, then it will default to NOLIMIT when REGION=0M is specified or defaulted to.

We realize that we could code REQMEMLIMIT(NOLIMIT) in SMFLIMxx, but this will *also* override explicit MEMLIMIT=NOLIMIT requests, which is not desired.

So we are forced to either accept MEMLIMIT=NOLIMIT when it is not specified in JCL, or to accept something else when MEMLIMIT=NOLIMIT is specified/desired.

In all circumstances, the MEMLIMIT value in SMFPRMxx should be honored when MEMLIMIT is not specified in JCL and is not overridden in SMFLIMxx.

We can handle one job allocating 2GB memory, but cannot handle that job trying to allocate 16 exabytes.

This conditional behavior is something that no user would expect. It has several inherent problems and adds no value.

Idea priority High