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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server
This requirement is satisfied by CICS TS 5.1 which is generally available December 14th 2012.
Hi Ellie, many thanks for looking at the 1103 fixpack and letting us know that you're happy with the behaviour there. We'll include the same functionality as-is in the 5.1 CICS Explorer, and I'll set the status to "Resolve -> Planned for Future Release" - which means that it is planned for the next planned release, which is the 5.1 CICS Explorer
We now have version V1103 installed, and it seems to be working as we would like for column customization and reset. Perhaps that can be the model for this RFE going forward.
The default Eclipse behaviour is for a view's contents to be independent of the perspective it is displayed in - when you switch perspective all that happens is that views are shown/hidden/moved. We only store one set of columns which apply to the view, irrespective of the perspective it's on, and I don't want to change this. However - we are thinking that if we had a way of saving/naming a set of columns together with filters and giving them a name, e.g. "my tasks" or "all disabled files", then you could recall these with a single click. This means that customizing columns is done once and stored and then easier to recall. If a view wasn't the way you liked it - you could just switch to the set of columns, and we could look at a way of sharing column layouts between users the way we allow sharing of connection details.
Comment Added 08/01/2012 (Lisa Fellows):
We have an Installation Specific Perspective that was developed to monitor Region Health. Currently that Perspective contains the Region Tab. If we customize the Region Tab in this or any perspective that change to the Region Tab is applied to ALL Perspectives.
We would like the ability to customize a Tab within a Perspective and have those changes applied ONLY to that Perspective. This would give us the ability to create other customized installation Perspectives without impacting those already in place.
Under these conditions when a Perspective Tab is customized that should be the new baseline for the Tab/Perspective, until such time that a Reset Column or Reset Perspective is performed. Upon Reset Column/Perspective the rules outlined above should apply, with the addition that the Reset Column should ONLY impact the Current Tab in the Current Perspective.