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.

Add a new idea Subscribe
Status Future consideration
Workspace IBM Z System Automation
Created by Guest
Created on Apr 14, 2016

RELATED IDEAS

Ability to define a start and stop priority of High, Med or Low for APLs linked to a Pacing Gate.

For example if we have 53 tasks, WASA01 – WASA15, WASB01 – WASB22 and WASC01 – WASC16 linked to system 9S04, we would like the ability to define a Pacing Gate, set the Start limit to 4, but also have the ability to assign a priority such as High, Med and Low so we are able to control the order of which jobs start or stop within a particular Gate.
Assign High to the WASA* jobs so they start first, Med to the WASB* jobs so they would start once all High priority jobs are started, then assign Low to the WASC* jobs so they start after all High and Med priority jobs are started. The reverse for stop requests.

We currently accomplish this by defining application groups with MAWA dependencies between the groups, however a task ABEND at start could leave the group in a Problem state and prevent downstream tasks from starting. Using APGs also requires extra work in policy to make the appropriate definitions.

Idea priority Medium
  • Guest
    Reply
    |     May 18, 2016

    Hello Gary,
    thank you for this RFE. We discussed it today in the SA z/OS RFE meeting. A solution as requested in this RFE would require a major development and test effort.
    Even though we see the value of this RFE, we will not be able to work on it in the foreseeable future.
    We are focusing on RFE hot spots and client votes to set the correct strategic and RFE-related priorities.
    Here is an idea, that came up during the RFE Meeting: You may consider using SA z/OS triggers (TRG).
    As an example: When a certain number of the WASA* jobs is available, then a startup trigger for WASB* could be fulfilled, that allows to start WASB*. And a similar approach for WASC* jobs - when a certain number of the WASB* jobs are available, the startup trigger for WASC* is fulfilled, so the WASC* jobs could be started. I hope this gives you a satisfactory solution.
    Best Regards,
    Raimund Thielker
    SA z/OS Design & Development

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.