Windows and UNIX clients can share config specs, which are portable between the two operating systems. That is, clients on both systems, using views whose storage directories reside on either kind of host, can set and edit the same set of config specs. However, Windows and UNIX network regions often use different VOB tags to register the same VOBs. Only single-component VOB tag names, like \src2vob, are permitted on Windows clients; multiple-component VOB tags, like /vobs/src/proj1, are common on UNIX. When the VOB tags diverge between regions, config spec element rules that use full pathnames (which include VOB tags) are resolvable (at config spec compile time) only by hosts in the applicable network region. This implies a general restriction regarding shared config specs: a given config spec must be compiled only by hosts on one operating system or the other—the operating system for which full pathnames in element rules make sense. That is, a config spec with full pathnames can be shared across network regions, even when VOB tags disagree, but it must be compiled in the right place.
This restriction does not apply if any of the following are true:
- The config spec's element rules use relative pathnames only, which do not include VOB tags.
- Shared VOBs are registered with identical, single-component VOB tags in both Windows and UNIX network regions. (The VOB tags \r3vob and /r3vob are logically identical, differing only in their leading slash characters.)
- The config spec does not include any load rules or element rules.