PVob is like a vob in that it can version files and folders.
But by convention, you don't use a pvob to "add to source control".
You use a PVob as a "admin vob" for a classic Vob in order to declare component(s) in it, and to manage all the matadata associated to UCM:
- Projects
- Streams
- Activity
- Merge Hyperlinks for deliver and rebase
In that case, as I mentioned here, PVob are visible in the ClearCase project Explorer, not the ClearCase Explorer.
As any "AdminVob", a pvob manages datatypes for the associated vobs: see "VOB datatypes and administrative VOB hierarchies".
Simply, a pvob will manage UCM types as well, making projects, streams and activities visibles for all the associated UCM vobs (which contain the actual data).
You can actually group pvob in a hierarchy, as explained in "Multiple PVOBs and a common administrative VOB".
If projects in one PVOB need to modify components in other PVOBs, your Rational? ClearCase? administrator needs to identify one PVOB to serve as a common administrative VOB for the PVOBs and the component VOBs.
In Figure 1, PVOB1 and PVOB2 use PVOB3 as their administrative VOB.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…