This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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.
See this idea on ideas.ibm.com
Hi
I've some across the requirement to submit a set of job streams (group) while maintaining the correct external follows dependencies. When doing this manually, this means that it should be done with great caution and in a correct order.
What we need is a logical grouping of job streams (f.e. application) so that we can simply submit the application while adhering to the correct dependencies (like the planner does during the extend).
Implementing a logical grouping would also alleviate the need for nested job streams and will require less development effort.
Idea priority | High |
RFE ID | 89438 |
RFE URL | |
RFE Product | IBM Workload Scheduler (IWS) |
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Cloud
Product family - Workload Automation and Control Desk
Product - IBM Workload Scheduler (IWS)
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - ITSM Automation and Control Desk
Product - IBM Workload Scheduler (IWS)
This feature would also help the issue of job streams that have jobs that run from job stream A then from job stream B and then more from job stream A. Submitted through the planner, they run correctly, submitted manually job stream A needs to be submitted first. then job stream B, but then the successors to job stream B in job stream A do not have the predecessors attached.