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 Feb 8, 2018

JES2 new Function (STAC Queue Corrupted)

ITAP-SSSE z/OS JES2 support, suggested that we submit a RFE, requesting that the development team introduce a new function in JES2 so that the STAC queue is verified when a STATUS/CANCEL SSI call is being handled and if queue error is detected, the issuer of the call would be notified via a new RC.

the suggestion was given in the scope of the PMR 63391,001,822 and 64047,001.822, that report performance problems after corruption in STAC Queue.

..... I have discussed with development.
They do agree to have some RAS enhancements (Reliability/
Availability/Serviceability) to a future release of JES2
to let the issuer of the STAC SSI call be aware the STAC
queue have been corrupted.
To make this official, I would suggest you submit an RFE
through this WEB site:
.
To recap, the enhancement would be to introcuce new function
in JES2 so that the STAC queue is verified when a
STATUS/CANCEL SSI call is being handled and if queue error
is detected, the issuer of the call would be notified via a
new RC......


Another enhancement that we would like to suggest, was to evaluate the possibility of refresh the STAC queue via a JES2 hotstart.

.... The STAC queue resides in a dataspace (JES2STAC) and the only
way to refresh the STAC queue is via a JES2 warmstart
(meaning an IPL). A JES2 hotstart will not rebuild the
dataspace (JES2AUX address space maintains the dataspace on a
hotstart).....

Idea priority High