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 JES2
Created by Guest
Created on Jun 18, 2021

Unsupported NJE remote executed commands improvement

The existing implementation of the $N command for NJE remote command execution does not fully support all commands. For instance, the $TA and $VS commands when send via the $N routing results in the issuance of $HASP649 - this is not a good error message since the commands is actually syntactically VALID and executable on the LOCAL JES2. The necessary SAF calls and parsing is not being performed at the remote executon. I propose a new NDEDEF option that will allow these commands to be proper processed on the receive node. This will allow for backward compatibility. Another option might be to validate the sending NODE name in the SAF call at the receiving node to provide end to end security. Please see the PMR that was opened in April 2021 timeframe.

Idea priority Medium