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 Planned for future release
Created by Guest
Created on May 9, 2023

Enforcing JESSPOOL security rules on JCAN command

When JCAN is used to issue a cancel or purge command, it will issue the operator command $CJ(nnnnnn). This is like what SDSF does, when a line command C/P against the selected job. The significant difference is SDSF can/will perform a check against JESSPOOL to ensure the user has permission to cancel or purge that process running or purge output before issuing that opercmd. JCAN does not do this.

This opens up JCAN to destructive events when commands are generated in error, too broad, or bad actors, resulting in opercmds against batch work in a shared environment that the human/non-human ID should not have access to do.

JCAN should perform a check against the JESSPOOL for the jobname/number before issuing the opercmd or get an option to enable enforcing that.

Idea priority High