Hypothetical question ... has anyone encountered "filename too long" problems when using Rational Team Concert on a Windows client? I have had a quick look on the forum and the existing questions in this space do not seem to boil down to RTC issues.

ClearCase suffered badly from this problem as the limitations imposed by the operating system were/are compounded by the "filename" having to incorporate the full file system path which for the MVFS includes everything from the view root (e.g. X:/ or M:/viewname) right through to the version selection string (i.e. X:/....@@/main/branch/branch/999). Reference: https://www-304.ibm.com/support/docview.wss?uid=swg21127935. There are several solutions to the problem on ClearCase, my favourite but typically impractical being to rebase and deliver on anything other than a windows client. Anyway, back to the point ...

The above problem naturally dictated the branching and merging strategies adopted at Clearcase sites - cascading projects have to be avoided and restrictions are necessarily imposed on stream (branch) name lengths. Aside for the visible limitations placed on the user community, there is an administration overhead with limiting the cascading of projects as each release stream has to be cloned or merged onto the mainline at the worst possible time (just before or just after a production release).

Is it safe to assume that an RTC project using native source control (i.e. no source in ClearCase accessed via adapter) can cascade without limitations on windows?

Any thoughts / experiences appreciated!

Ian.