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 Mar 22, 2019

SSI 80 Data Set List Request to JES2 should return correct attributes even if changed after data set creation

One of our products, Entire System Server, has a component to collect information about jobs and SYSOUT data from JES2 and JES3. When it was written in 2000, it used the SSI 80 request types available back then as well as JES2 and JES3 services e.g. to obtain spool data set information. We have replaced these JES specific services with SSI 80 request types available now, such as STATDLST (Request data set list).
Unfortunately the attributes in the SYSOUT Element Verbose Section(s) returned by STATDLST may reflect attribute changes made after the data set was created. This is documented in the section "Use Information for data set list requests" in chapter 3 of the document "Using the Subsystem Interface". However, our customers need to have the correct attributes also in these cases, and the attributes are available in the corresponding $JOE.
We have resolved this requirement by now by issuing an additional STATOUTT request for the job, and for every spool data set with an output group name we locate the associated SYSOUT terse element returned from the STATOUTT request and get those valid attributes from there. That works ok but is somewhat inefficient, and I think that should better be done in HASCSISC by obtaining the correct attribute data from the associated JOE.

Idea priority High