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 Apr 22, 2022

Mitigate potential security exposure of current ETT functionality by identifying/authenticating user triggering the ETT job

At present, there is potential security exposure for ETT triggers set up as 'JOBNAME REPLACE' = N. Reason being, any user can inadvertently or otherwise submit a trigger job defined in Production ETT database thereby triggering ETT application even though trigger itself might be cancelled by security rules that were in place. It appears 'A1-job card read' event is sufficient to trigger the application. Besides changing all the trigger jobs to 'JOBNAME REPLACE=Y' , there should be other options to prevent this. One option is to identify the "user" who triggers ETT. This will permit to check if the user is authorized or not to submit ETT trigger job, similar to what is currently available with dataset triggering function.


Idea priority Medium