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.

Add a new idea Subscribe
Status Future consideration
Workspace z/OS
Categories z/OSMF
Created by Guest
Created on Dec 12, 2023

RELATED IDEAS

z/OSMF REST API steps should allow multiple return codes as "expected"

zOSMF workflows will not be 100% complete when there is a Failed step. A workflow becoming "complete" is very important when using callable workflows. Values generated for instance variables in the called workflow will not be updated in the calling workflow until the called workflow is 100% complete.

The set of REST APIs provided by zOSMF is a good set, however, when defining a step in a workflow that uses a REST API you are only allowed 1 expected return code. If the API returns something else, the step is considered failed and the workflow will never "complete".

As an example, the query file system API - it will return a x'404' if a path does not exist or a x'200' if the path does exist. The expected return code would be x'200' as once the path is created that will be return code from then on. The workflow could choose to create the path when the x'404' is returned, however that x'404' will Fail the step.

There is no way to override the state of a Failed step. Updating z/OSMF to accept multiple "expected" return codes from a REST API call would fix this problem.


Idea priority Medium

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.