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.
Hey! I've been experimenting with this feature and we may have gotten to a point where I believe it's ready to be shipped as a first iteration. See attached screenshots for a preview of how the setting work.
To recap:
1. I've named the feature "Pinned History Files". The concept of "Default History File" is already taken.
2. Once you put an history file name there, it becomes always visible in the tree and cannot be removed.
3. Currently, there is no validation of the name. If you put invalid data, it will be displayed anyways.
4. Diagnostics are provided only for the Zowe profile name (the key).
WDYT?
Perfect thanks. The question about AppData was mostly to understand whether single users would be able to "override" default settings. Let's say you deliver A,B,C in AppData\Roaming\Code\User\settings.json, the user might want to add its own files on top of those, and it should be able to do so by specifying the same option in the workspace' .vscode\settings.json file.
Question: how are VS Code settings deployed to your users right now?
Are company-wide settings delivered alongside the installation and stored under AppData\Roaming\Code\User (on Windows), or are you using .vscode/settings.json (settings per workspace)?
This is important to understand what would happen if we decide to store this new information under VS Code Settings.
Sounds good! Let's keep this Idea strictly related to pre-defined resources. Could you create a new Idea for Views support? We are better off tracking them separately imo.
Ahhh ok! So basically what you're looking for is support for Views. It's in our backlog already, so it will be delivered at some point in the future. We'll start with just the ability to add and open existing Views, and then we'll work on the View Editor UI (which obviously will take more time).
The second part of the enhancement request seems to be valid for both History Files and Views: being able to set resource names that are then shown to the user by default, as soon as VS Code is opened.
Is my understanding correct?
Hi! To clarify, we're talking about a client-only "default" (a.k.a. shown by default) history files, or is there a z/OS host involvement I'm missing?
I'm asking because Fault Analyzer already has a concept of "default history file" that you're able to configure through IDICNF00 or IDIOPTS for a single user. We don't support that either at the moment, but the clarification is needed to understand the direction we have to take.