The component is not being 'refreshed' before each edit attempt. "All" the changes made up to the point where the error that is preventing the save (such as install date passed) is corrected, will subsequently be saved if/when the error is corrected. This can cause unintentional or unrealized changes to be saved on the ZMF Server side.
When editing a package component within the Serena perspective and leaving the session for a period of time the user is being disconnected. When they return to the edit session and attempt to save the component (CTRL+S) the session is not being reconnected in the expected manner and the user is prompted to save the component on the local machine. This fails and various error messages pop up.
If USERA attempts to edit a component that was previously saved by USERB, the changes are not saved and "Checkin failed CMN8262I - Component to be staged is locked by USERB." is issued. Also, Admins are allowed to edit the component successfully. If the user logins to ISPF ZMF, saves the component there and then attempt the edit in ZMF for Eclipse, the edit is then successful.
While installing ZMF4ECL, the default path for the ZDDOPTS SAMPLE members is ‘C:\Program Files\Serena\ZMF\711\ZEclipse\zddopts’ and cannot be overridden. The customer's C drive is ' write ' protected, so the install fails .
