Troubleshooting
Problem
This technote explains why performing a checkout using the IBM® Rational® ClearCase® Web interface can result in files being displayed as zero-bytes.
Cause
After checking out a file from the ClearCase Web interface, you notice that a different file is now shown as being zero-bytes.
Example:
1. Checkout a file called FOO.c from the ClearCase Web interface
2. You notice that another file called BAR.o is now shown as being zero bytes (0 bytes).
Note: If you were to perform the checkout from a different view (with same config spec) on a non-web ClearCase client, you would see BAR.o is now shown as checkedout but removed.
CAUSE:
FOO.c is a hard link of BAR.o.
When FOO.c is checked out, ClearCase copies a view private copy of the checked out file to the file that was checked out (FOO.c in this case).
However, because BAR.o and FOO.c reference the same element, ClearCase thinks that BAR.o has been checked out (which is correct) and removed (which is technically correct, since ClearCase did not copy a view private version of the checked out file to BAR.o).
This is why the web interface shows the file (BAR.o) as zero bytes - there is no view private file to reference.
Review technote 1149701 for more details on Hard Links causing checked out but removed or disputed checkout messages.
Resolving The Problem
Ignore the zero-byte file (BAR.o) and work on the (FOO.c) as expected. Upon checkin of FOO.c, the zero-byte file (BAR.o) will be restored.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21126974