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 Feb 9, 2026

ETT Job Triggering should consider destination

This idea relates to the topic of ETT triggering based on jobs that run on a system not under zWS control. Especially in larger environments with multiple zWS trackers connected to the controller, it would be necessary to consider for ETT job triggering not only the jobname but also the destination, from which the event was created. 

This is useful in cases (like in our environment) when jobs are generated dynamically by other applications and the jobname may be the same on different systems. In this case you can only define one trigger, but maybe you don't want, that JOB1 on SYSA should trigger the same application as JOB1 on SYSB.

Also, if you want to integrate more different customers in one zWS system, you must always take care that there are no jobs running for customer A which could be a trigger for an ETT of customer B. If the destination was considered accordingly, that's not a problem.

Idea priority Medium