I hope that transarc does not implement such a change. The nature of the vos release commands relies on both server-server communication, but supervised by the vos program. Interrupted vos commands can have serious implications on the state of the service environment. This would potentially allow a clueless user to seriously compromise the stability of a cell where different versions of a volume may then reside on different servers. Another argument against this is the number of active connections possible to the server (as used by vos et. al.). Unless the number has increased from four, you could have a failure if too many are releasing simultaneously. I feel much safer have a server process, similar to what has been mentioned, handle vos release requests for users. The server process will ensure completion of all commands and can be written to notify critical persons in case of failure. If Transarc deems it necessary to implement a clueless user vos release, I hope there will be a server flag that will disable it. Ezra Peisach
