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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Supplement my request.
In response to this request, please let me know if you think it is possible to change the specifications or if you think it is difficult to change the specifications.
If it is difficult, please tell me the reason.
Then my customers will be convinced.
It would be helpful if you could get this reply by 3/11.
Regards,
I have been instructed by my customer to proceed.
Please check the following.
Maintenance is performed by stopping the target host, but other hosts continue to provide services.
Stopping the host will stop the initiator and TWS tracker, and after about 8 minutes, stop JES2.
Between the time the TWS tracker is stopped and the time JES2 is stopped, the TWS status may be lost for jobs run on
non-maintenance hosts.
It received a reply that if JES2 is running, TWS-EXIT may be processed even on the host under maintenance, and the
TWS tracker is already stopped, so the TWS status will be lost.
It got an answer when I asked it in 2013.
As stated in the manual, I know that it won't be lost in JES independent mode.
(Managing the Workload Version 9 Release 5 Chapter 15 Overview of job tracking on z / OS)
However, my customer wants to improve this phenomenon without changing the system.
Therefore, please consider changing the specifications of TWS.
Regars,
Hello
Some respondents said that this scenario is a TWS specification.
Therefore, the request is made according to the request from the customer.
Please let me know if there is anything you need to do to proceed with this request.
Regards,
When the event occurred (2013), I answered that the inquiry was completed. Please contact us if you have any additional required information.
Regards,
We are inquiring with "PS" when it occurs in 2013.
In a SYSPLEX environment, work may also be assigned to JES2 EXIT on an LPAR where the TWS tracker has stopped.
Therefore, we have received an answer that the status will be lost.
The scenario should be described more clearly to understand which events were lost. Did you open a case and received suggestions on a specific system configuration to avoid the problem?