For example: test/doc/read.me@test-1
For example: test/doc/read.me-2@test-1
For example: test/doc/read.me:2@test:1
Like the work area reference forms, the first two forms can be ambiguous. For example, the specification "test/a-file-1@test-1" can mean a file named "a-file-1" with the version used in project "test-1", or version "1" of a file named "a file" in that project, or version "file-1" (which would be invalid by default) of a file named "a" in that project.
When referring to existing objects, if the third form is not specified, Rational® Synergy first looks for an object whose name matches. In the previous example, it looks for an object named "a-file-1" in the project. If no such object is found, the rightmost version delimiter is used to separate the last part of the path into a name and version. In the previous example, it looks for a file named "a-file" and version "1" of that object.
If this setting is TRUE and the version delimiter is the default of "-", you cannot create objects that start with "-" using the Rational Synergy CLI. For example, the ccm create -foo.c command fails. It fails because "-" is an option delimiter in the CLI and the foo.c option is not valid for that command.
In a DCM cluster, the best practice is for all databases to use the same value for this setting. Failure to use the same value can result in undesirable behavior similar to having objects with "~" in them, and changing the delimiter to a "~".