Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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 Under review
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Aug 9, 2024

Need capability for restarting the failed process from the plugin step which actually failed

Currently when we repeat the failed process, it starts another run altogether and hence starts from begining again.

Instead we want a capability of restarting from the failed step similar to what a mainframe JCL offers.

This functionality is very critical for production deployments since the window for deployment is very short to reduce the application outage.

If we consider a typical deploy process for mainframe which has DB2 Bind, Deploy Datasets and CICS Newcopy and if the component version is having around 100 artifacts, if the newcopy step fails, repeating the process again will try to execute DB2 bind and deploy datasets again which will definitely take 5-6 mins which is unnecessary since those were already executed before.

Hence it would be efficient to just start from the failed point instead.

 

 

Idea priority High
  • Admin
    Randy Langehennig
    Reply
    |
    Sep 26, 2024

    Our development team assessment from an internal review is below:

    1. A partial restart is complex, can be error prone, and is something that we have declined to do before.

    2. Our product was never architected to do this. Since we track inventory, component steps will be skipped if the component version is already installed as an example but explicitly skipping a step is something we do not support. There are other ways you can design your workflow to skip previous steps that ran to completion prior.

    We would like to hear your point as well and we would like to facilitate a call with our lead mainframe engineer to explore options to help you in this area. Would you be open to a meeting to discuss this further? Please let us know and we will work to get this scheduled. Thank you!

  • Admin
    Randy Langehennig
    Reply
    |
    Sep 4, 2024

    Thank you for submitting this idea. We will review your request soon and provide you with an update.