Hey Endevor Users!!
We need your feedback!
If your site has chosen to use ELEMENT LOCKING, optional feature O0000315A/B in the ENCOPTBL to allow actions outside of package and SOFETCH=Y in the C1DEFFLTS Table there is a potential that an Element Locking/Package Execution issue could occur. The problem is when the element is located across the life cycle map and is locked by a package; for example is moving into production, then if you attempt an action in Quick-edit of that ELEMENT, and for some reason the package is scheduled to execute while that element is in EDIT mode the package will go into a WAIT/HOLDING status because of an enqueue. The problem is that there is no message issued at the time when you perform the action on the element in Quick-edit.
Here is what we need to know –
Here is the catch, if you ignore the lock/remove the package enqueue and allow one of the above actions, please remember that the MCF/Master will be updated at that time.
I am not sure if this is a good analogy but when we have a job waiting for datasets, the console message in the job job is intercepted by Ops/MVS and it sends a TSO message to the user saying 'Please release dataset ******.xxxxxxx so that job yyyyyyy can run'
Could the package execution issue some kind of waiting for resource WTO that can be picked up by any automated process?
Then the appropriate action for the situation can be taken. Just a thought.
I like option 2 - disallow edits while package execution is pending or 4 - leave it as-is.
In our shop we are using "ELEMENT LOCKING", make use of O000315A ref. SIGNIN-Action, have set SOFETCH=N in C1DEFLTS.
I believe, the intention of "ELEMENT LOCKING" is to ensure, that a CASTed package is kept executable without errors caused by interim changes to referred elements.
My vote is, that Quick-Edit may fetch a LOCKED element but must not allowed to save or modify the element so that the package becomes not faultlessly executable. This corresponds to your option "2" but even beyond: Quick-edit should fail to save or modify with an explaining error-message (C1G0503E), even when the package is not yet being executed (during the whole period of time, the element is locked).