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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
This requirement has been re-assessed. It is not likely that this will be implemented in the next 12-24 months and so it is being declined at this point.
I am on IDz 14.2.1.1 and now do the filter string ETRO.D01501G1.BATCH.* work fine :-)
- Currently, IDz GUI alrealy has a similar option providing a finer result as ISPF to display the datasets of a GDG.
- It can be done with IDz in two step: first query with a fully qualified name of the GDG (with no trailing *), then expanding the result for the query. The final result would show only the datasets belong to the GDG, finer than the result returned from ISPF with a GDG_name.* query, which shows all datasets matching the prefix, including the non-GDG.
Not sure if the customer knows about this IDz option.
I am now using IDz 14.2.1 and ETRO.D01501G1.BATCH.* still gives an empty list.
With ETRO.D01501G1.BATCH* and ETRO.D01501G1.BATCH.**, as a filter, I get the GDG-base with an > in front of it.
If I expand > in front of the GDG-base then can I see all generation datatsets.
So there is still a difference between ISPF 3.4 and IDz regarding ETRO.D01501G1.BATCH.*, that is confusing and could result in problems for users.
/BoRa
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Development Tooling
Product - IBM Explorer for z/OS
Component - Other
Operating system - Windows
Source - Client
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Programming Languages
Product - IBM Developer for z/OS, including Enterprise Edition
Component - Remote System Explorer
Operating system - Windows
Source - Client
What happens is you use ETRO.D01501G1.BATCH* in your IDzfilter ? The IDz RSE organizes generations rolled into the base under that like a folder (think PDS member within PDS). ISPF lists everything alphanumerically regardless of whether they are rolled into the base.
In 14.1.7 (maybe other versions as well) you can see both type of list if you use .**
In 14.1.7 (maybe other versions as well) you can see both type of list if you use .**
There are two ways to view GDG's in IDz.
1. Drop the .* and you will see the mainname and just the generations in a list
2. Change .* to .** and you will get the full names like in TSO.