IBM Support

About symbolic links and version-extended pathnames

Troubleshooting


Problem

This technote explains why attempts to use a version-extended pathname in the form of @@ for an IBM® Rational® ClearCase® symbolic link will produce the error []No such file or directory[].

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.

Cause

Symbolic links are not versioned and, hence, do not have version-extended pathnames.

Symlinks are not catalogued in the version history of the element. They serve only as a pointer to a target version, and allow you to create multiple access points to a single version. Review the ClearCase Command Reference Guide on the topic of ln (cleartool man ln) for more information.

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.

Resolving The Problem

You can describe a symbolic link using a non-version extended pathname as detailed below.


For example, if you have a link /vobs/jedi/xwing/yoda pointing to /vobs/jedi/yoda.txt:
  • The symlink can be described with a simple pathname, as follows:

    • %>cleartool describe -long yoda
    symbolic link "yoda" -> ../yoda.txt
    created 29-Sep-05.09:51:58 by Jane Doe (jdoe.100@pet1)
    master replica: pet1@/vobs/jedi
    Protection:
    User : jdoe : rwx
    Group: UNIX:GID-100 : rwx
    Other: : rwx
  • The actual text file that the symlink points to can be described with a simple pathname or using its version-extended pathname:

    • %>cleartool describe -long yoda.txt@@/main/br1/br2/1
    version "yoda.txt@@/main/br1/br2/1"
    created 18-Aug-05.14:22:08 by Jane Doe(jdoe.sybase@pet1)
    Element Protection:
    User : jdoe : r--
    Group: UNIX:GID-100 : r--
    Other: : ---
    element type: text_file
    predecessor version: /main/onyx/ring/0

Change request (RFE) RATLC00584686 has been opened requesting a -follow option for cleartool describe and other cleartool commands that will enable them to display the information about the target file that the link points to.

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 September 2018

UID

swg21220890

Page Feedback