VUE 3.2(284) reverts the locking under Windows back to the way it was prior to 3.2(280), meaning that although it prevents two Windows users from VUEing the same file in update mode, it allows read-only access to a file that is being VUE'd. Starting with 3.2(280), we made the locking more strict to better coordinate locking between cross-platform users, but this had the undesirable side effect of making it impossible to compile a program in one job if it was being VUE'd in another. To activate the stricter locking, you can now add the following to the INI.VUE:
LOCKSTRICT = TRUE
Otherwise, the more permissive style locking will be in force. Note that the permissive locking is not believed to be reliable in cross-platform environments. (In such cases, or whenever you have mixture of VUE and EDITOR users, you should probably use the LCKFILE=TRUE option.)