Troubleshooting
Problem
This technote explains why attempts to use a version-extended pathname in the form of
Symptom
Using a version-extended pathname when referencing a symbolic link reports error:
No such file or directory.
Here's an example of trying to see version details by describing the symbolic link using the version extended path of the file version it points to:
%>cleartool describe -long file@@/main/br1/br2/1
cleartool: Error: Unable to access "file@@/main/br1/br2/1": No such file or directory.
[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"VOB","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"2003.06.00;7.0","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
29 September 2018
UID
swg21220890