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 May 8, 2017

Change externally stopped/started APL status to STUCK/STARTED2 if APL do not STOP/START within expected threshold

Improve IBM SA for z/OS to mark Externally stopped/started resource to PROBLEM status if resource is taking too long to STOP or START.

The SR (74898,001,866) was raised to resolve the issue when applications that have EXTERNAL STOP FINAL were left for a week in INAUTO status.

This occurred as a result of a user doing a STOP vote for an APG containing other APGs each with about 40 APLs. The APGs went to
STOPPING followed by the APLs, but before all the APLs had stopped, the user cancelled to top level STOP vote. This caused the APGs and APLs that were already STOPPED to restart, but those APLs in STOPPING stayed that way until manually corrected.

Could System Automation be improved to change the status of APLs to STUCK (if stopping) or STARTED2 (if starting) in above mentioned situation if STOP/START time thresholds were breached? As it is not right to leave APLs in good status such as AUTOTERM for whole week. If APLs is in STARTED2 or STUCK operators would be alerted.

Idea priority Medium