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 Under review
Workspace z/OS
Created by Guest
Created on May 31, 2024

Allow a cloud multipart object via gdkwrite/gdkget apis to restart on a particular part

It would be useful to allow a program using GDK_EXIT_DATALOCATION (streaming send exit) to resume sending data for a multi-part object.

For receiving cloud data I believe I can use range start and end to restart receiving data, but I didn't see anything additional for gdkwrite

Idea priority Low
  • Guest
    Reply
    |
    Jun 17, 2024
    I think I need more information about what your expectations would be. In general, cloud object storage does not support replacing a part of an object, nor appending to an existing object, which is why the Range header isn't allowed on PutObject REST API.
    Is your expectation more that you would like to 'pause' a multipart upload, leaving the UploadID as valid, and wanting to put another part as a restart from some checkpoint, wrapping up the full upload?
    1 reply