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 Future consideration
Created by Guest
Created on Dec 18, 2019

TWS not status update before Tracker start

【Environment】
z/OS 2.1
TWS 9.2
5Host SYSPLEX
JES-MAS
Event detection using JES-EXIT
Controller runs on one host

【Events】
During host maintenance, only the maintenance target host is stopped, and operation is continued in a degraded state.
When starting a host that was stopped after maintenance、Between JES2 startup and TWS tracker startup (about 8 minutes)
Status update of jobs executed on other hosts、What happened after starting JES2 on the running host and before starting the TWS tracker,
event occurred that caused the TWS status update to be lost.

For the running host, we received advice to leave the JES-MAS configuration by command until TWS tracker startup,it is judged that it is difficult to change from now on the system that has started production、This is a situation where fundamental measures have not been taken.

【Request]
In future TWS versions, we would like to request the addition of a function that can avoid the above phenomenon with the TWS function

Idea priority Medium