Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 z/OS Explorer
Created by Guest
Created on Mar 13, 2026

Enable the RSE API to support exact (non‑wildcard) PDS member queries without requiring pagination headers.

Customers frequently need to filter or retrieve a single, exact PDS member, but the current RSE API rejects non‑wildcard member queries whenever any pagination headers are included, which prevents IBM Z Open Editor and Zowe Explorer from supporting this use case. When users try to filter an exact member name, the server returns an HTTP 400 Bad Request with error CRRZR4007E indicating that pagination headers cannot be used for non‑wildcard queries. Allowing the RSE API to process precise member names without requiring wildcard patterns would make dataset navigation more intuitive, remove unnecessary errors, and align the API with common user expectations. The feature should allow DATASET(MEMBER) requests to succeed without requiring pagination.

Idea priority Medium
  • Admin
    Jason Chung
    May 5, 2026

    Hi, thank you for your RFE suggestion.

    The team wanted to clarify the following details :

    • What is the exact PDS member is identified by name or ordering index (integer)?

    • With both exact PDS member (by name or integer index) and range query provided (by start range name or start index), should the return be inline with both conditions?
      For example: PDS has member 'B' (index 2), for the exact filter name 'B' with memberAttrs query if:

      • start range name is 'C', or start index is 3, it will return nothing.

      • start range name is 'A', or start index is 1, it will return the member 'B' attributes.

    • Should the caller expect to have the index (integer) of the member returned in the response header?