1. An invalid SER4155E in the eclipse or RDz client Data Set ENQ failure : SER4155E Serial lock could not be obtained 2. An invalid SER9500I message in the started task output
Users may see a ‘SER4155E Serial lock could not be obtained’ or a ‘SER4252E Dataset ENQ failure ’ on the staging dataset and the task may issue a ‘SER9500I Dataset in use’ on the same file. The issues therefore: i. the ZMF4ECL client should successfully reconnect in this scenario.
Observed file browsing failures . Using browse...with options did not correct the problem. Further research found that the Editor File Association was locked.
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.
After upgrading their live ZMF4ECL environment to 8.1 GA build 267 running against a 7.1.3.01 Server environment, a customer is reporting multiple incidents of components being invalidly locked. After a period of user inactivity, any subsequent close of a package component file fails to clear the CMNSTGER ENQueue and leaves the component locked from further editing for an unknown period of time. The only way to ensure clearing the ENQ is to recycle the task.
ZMF4ECL issues the following messages/pop-ups. a. ‘Data Set ENQ failure : SER4155E Serial lock could not be obtained’ b. ‘Checkin failed - unable to obtain Data Set ENQ for (personal development library name)’
