A committed file in ClearCase is indeed read-only.
If by "not read only" you refer to private files not yet added to a view, you can start by looking for private files, based on grep rules on a recursive ls
cleartool ls -r -nxn
That would be safer than the "read only" criteria, since private files can also be read only (even though they are "not checked-in" yet, not yet managed by ClearCase)
The idea behind a recursive ls
is to display all the rules associated with all the files of your view.
- No rule means "private" (whether the file is read-only or not)
Rule: ...\aBranch\LATEST
means it is committed (and -- incidentally -- read-only)
Rule: CHECKEDOUT
means it is committed, but being modified (read-write, but nothing prevents the user to make it read-only again without checking it in)
Rule: hijacked/eclipsed
: committed, but modified without having being checked-out yet (read-write, but again, can be turned read-only without notifying ClearCase)
So you can grep whatever set of files you actually need from that list, based on ClearCase rules (or lack thereof).