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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Programming Languages
Product - Developer for System z
For recording keeping, the previous attributes were:
Brand - Rational
Product family - Design & development
Product - Developer for System z
It's true that TEST(ERROR) is saved for the next debug session when changed by the user.
In our shop we offer (or rather force) the users to start up whith a pre-configured workspace containing all the settings needed.
So I would like to now where in the workspace this information is stored. If it is possible to change a xml file or some preference file that will do the trick - but I can figure out where in the workspace this information is stored.
In RDz the changes made on the "Manage compiled language event..." dialog are global and saved. The changes made to that dialog will be used in the next zOS debug session. So you should only need to set the TEST(ERROR) once and all future debug sessions will use that value. As far as this request is concerned it should work as you requested as long as you are using RDz v7.x and above.
One thing to note....If you change workspaces it will default back to TEST(ALL) since the profiles are stored in the workspace. If you are NOT seeing the above behaviour then please let us know and we can investigate.