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 Future consideration
Workspace z/OS
Categories z/OSMF
Created by Guest
Created on Apr 21, 2025

Misleading e-tag mismatch after uploading to sequential data set

  1. Create a sequential data set with RECFM=VB. In this case I created a data set with my username (4 characters long) as the high-level qualifier: USER.TEST.PS

  2. Use the z/OSMF API endpoint to write to a data set (PUT request, /zosmf/restfiles/ds/<dataset-name> endpoint)

  3. Notice a successful response (204 No Content), take note of the e-tag returned from the initial upload in the response headers: 86C2A8... (rest omitted for brevity)

  4. Use the z/OSMF API endpoint to read the contents of this data set (GET request, /zosmf/restfiles/ds/<dataset-name> endpoint)

  5. Notice a successful response (200 OK), but the e-tag in the response header is different: 55B96C...

  6. Try to use the e-tag returned from step 2 for another write request by passing it as the value for the If-Match request header. The request fails with error 412 Precondition Failed instead of the expected, successful response (204 No Content).

  7. Now, try using the e-tag returned from step 5 for the If-Match request header. This write request is successful with status code 204.

I am unable to reproduce this with PDS members, but can consistently reproduce it with a sequential data set on my test system. It's possible that this issue also affects PDS members on certain systems.

Idea priority High