Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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
Created by Guest
Created on Mar 20, 2026

WAPL - ALLDEPS function

Due to changing scheduling and changing requirements it would be a plus to be able to query ALLDEPS for a certain operation in the CP, perhaps up until a certain nesting level to keep performance impact limited.

This can be a full list of all dependencies and/or a number representing how many i.e. successors there are. This value can even be set once per operation during a replan/extend.

There are different ways possible to assign a priority or criticality to an operation, but the amount of successors an operation has, has very often been overlooked.

A "non-critical" job abend that has 2 successors and runs in a calm night window will not create a huge impact when it's restarted during the day. But lets say that an operation has 10.000 successors and becuase of an abend at 01.00, which is restarted at 10:00, all those 10.000 operations run during a very busy 'online' window. This might cause higher stress on the machine or, in the case of limited initiator availability for "non-ciritical" jobs, an extra delay.

If it would be clear for i.e. an operator or an automation that a non-critical job might cause impact to 10.000 other operations, that operator/automation might take different actions.

Idea priority Low