Protect Workfile (PROTECTWORKFILE)
The PROTECTWORKFILE attribute tells QVCS whether it should write-protect the work file after it has been stored in the QVCS archive. It also determines whether a work file will be write-protected after QVCS gets a revision from a QVCS archive.
When storing new revisions, if PROTECTWORKFILE is on, and DELETEWORK is off, QVCS write-protects the work file after adding the revision to the QVCS archive (if DELETEWORK is on, QVCS deletes the work file and ignores the state of the PROTECTWORKFILE attribute).
When retrieving revisions, if PROTECTWORKFILE is on, and CHECKLOCK is on, QVCS will write-protect any non-locking fetches. If CHECKLOCK is off, QVCS ignores the PROTECTWORKFILE attribute.
The purpose of all of this is to use the protection mode of the work file as a reminder of whether the work file was retrieved from the QVCS archive with or without a lock. When PROTECTWORKFILE and CHECKLOCK are both on, work files will be writable only if they've been checked out with a lock. If you simply perform a get on a QVCS archive without locking the requested revision, QVCS will write-protect the resulting work file -- you won't be able to edit it. This serves as a reminder that you need to check out the revision before you'll be allowed to make edits to the work file.
QVCS Attributes
| 
