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 Jul 7, 2020

Need job submitter userid in memory resident location

To obtain the job submitter of a job requires disk i/o to get the JCTTOKEN out of the JCT for the job and then use RACROUTE REQUEST=TOKENMAP against the JCTTOKEN to convert the security token into human readable text that is mapped by the ICHRUTKN macro, and the submitting user is pulled from the TOKSUSR field. There is no other JES2 control block that contains the submitting user of a job other than the JCTTOKEN, which makes it a performance problem to display it or use it in software that helps users manage jobs and job output. It would be beneficial to users and ISV's if it were in clear text in a control block such as the JQA (Artificial JQE) where disk i/o and a subsequent RACROUTE REQUEST=TOKENMAP would not be required. That would eliminate the performance problem and ISV's would be able to provide the job submitter on displays and make it available for use in scripts giving enhanced functionality.

Idea priority High