Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 Delivered
Workspace z/OS
Categories z/OSMF
Created by Guest
Created on Oct 7, 2019

Prompt user if they try to start a second z/OSMF Workflow instance from the same Workflow Definition

Some z/OSMF processes might not be suited to having multiple instances running in parallel. However, because there is currently no way to know from a Workflow instance which Workflow Definition it was created from, it is possible to start a second instance even if there is a prior instance that has not yet been completed.

If z/OSMF could store the name of the associated Workflow Definition in each Workflow instance (see RFE 134878), it would seem to be relatively easy to enhance the Create Workflow process to check to see if there is an active instance of that Workflow Definition. If there is, the user could be prompted to see if it is acceptable to start a second instance when there is an existing instance that is not yet complete.

As a Version 2 of this enhancement, a field could be added to the Workflow Definition where the user could specify whether it is acceptable to start a second instance. The Create Workflow process could then check that flag, eliminating the need to prompt the user to see if it is OK to proceed or not.

This was previously submitted to RFE on July 24, 2019 as RFE 374879.

Comments:

Stan W Abramczyk, Jr
Posted: Aug 20, 2019 10:26 PM

-------------------------

Comment: A simple example might be a Workflow that started by deleting any work data sets that might be left over from a previous instance. If a second instance is started before the first instance completes, the second instance could delete the work data sets before the first instance has finished using them.

I agreed this could happen especially with a large shop spread out across the country

Whatever we can be do to avoid this possible issue we should do it.

Stan A

-------------------------

Stan W Abramczyk, Jr
Posted: Sep 30, 2019 04:29 PM

-------------------------

Sounds like another great idea, additional functionality is always a great idea!

Stan A

Idea priority Low
  • Guest
    Reply
    |
    May 26, 2023
    Displaying workflow definition name in workflow details panel was supported in z/OS 2.3 and above. In addition, to restrict a workflow to one instance only, please use the optional attribute 'scope' on the sub-element(<workflowID>). The value can be 'system', 'sysplex' or 'none'. Thanks.
  • Guest
    Reply
    |
    Dec 17, 2019

    Hi, Frank
    Thanks for your requirement. Today, you can specify "scope=system" or "scope=sysplex" in in the workflow definition. By doing so, only one workflow instance can be created in the same scope(system or sysplex) with same Workflow ID. If the user tries to create the second workflow instance, it will fail. Please let us know if this feature could address your need. Thanks!