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.
CICS Explorer 5.3 includes a new Remote system Explorer Explorer view for z/OS assets which provides this capability
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
It appears that the ability to have two open edit sessions (one with Explorer and one with Edit) was by design:
https://www.ibm.com/developerworks/community/blogs/JoeWinchester/entry/z_os_explorer_and_file_locking
Personally, I think that this "optimistic lock" is opening the door for data loss. It gives the option to overwrite someone else's changes without even looking at them. The "pessimistic lock" forces the user to review their changes once the first edit is complete, since it prevents the second editor from getting an edit session in the first place.
This additional step to protect the data is one of the cornerstones of the Mainframe; one of the major architectural differences that sets the platform apart from distributed systems. The idea that the "data comes first" is what makes data loss on the Mainframe such a rare occurrence. It's really too bad that these new, cool development tools come at the expense of data integrity.
I agree on your first comment. Regarding the default opening action (browse or edit) the customer would like to have an option to decide what the default behaviour should be
I think that z/OS Explorer should only open in for browse if someone in ISPF Edit already has it open for write (and vice versa).
If nobody has the dataset and I open it in z/OS Exporer, I don't want to have to do something different to edit.