Potential Conflicts at SAVEWORK/GETWORK in a Multi-write Environment
- Last UpdatedNov 13, 2025
- 1 minute read
There are a number of potential problems which are not discovered until SAVEWORK or GETWORK.
-
Two users could simultaneously use the same name for an element. This may not be discovered until the second user attempts to do a SAVEWORK or a GETWORK. In this case the second user must rename the offending element before SAVEWORK or GETWORK is allowed.
-
One user may insert a primary element in another element's list, say /PIPE1, whilst a second user deletes /PIPE1. Again SAVEWORK or GETWORK will throw an error, and the user will have to move or delete the offending branch in order for SAVEWORK or GETWORK to take place.
-
The opposite of (ii) can also occur (that is, you have deleted a primary element in which another user has created an item. In this case the user must QUIT the changes).
If any error occurs at SAVEWORK or GETWORK then the entire operation is aborted.