PM32034: ClearCase config spec without an unrelated wildcard or unrelated recursive rule will not resolve the end point of a symlink

APAR status

• Closed as Permanent restriction.

Error description

• ClearCase config spec without an unrelated wildcard or unrelated
  recursive rule will not resolve the end point of a symlink
  
  
  ClearCase 7.1.1.x or 7.1.2.x
  
  
  Multiple UNIX Hosts
  
  
  To Reproduce:
  
  1)  Make a new VOB (-tag /vob/test) and View (-tag test).  The
  View will have the default config spec of:
  
  element * CHECKEDOUT
  element * /main/LATEST
  
  
  2)  Mount the VOB and set to the View
  
  3)  cd into /vob/test
  
  4)  Make two labels:
  
  cleartool mklbtype -nc TEST-ROOT TEST-DIR
  Created label type 'TEST-ROOT'.
  Created label type 'TEST-DIR'.
  
  
  5)  Checkout the root of the VOB:
  
  cleartool co -nc .
  Checked out '.' from version '/main/0'.
  
  
  6)  Make a directory element:
  
  cleartool mkelem -nc -eltype directory DIR-A
  Created element 'DIR-A' (type 'directory').
  Checked out 'DIR-A' from version '/main/0'.
  
  
  7)  Make a symlink to DIR-A:
  
  cleartool ln -s DIR-A SYMLINK-DIR-A
  Link created: 'SYMLINK-DIR-A'.
  
  
  8)  Checkin DIR-A and the root of the VOB:
  
  cleartool ci -nc DIR-A .
  Checked in 'DIR-A' version '/main/1'.
  Checked in '.' version '/main/1'.
  
  
  9)  Apply the newly created labels as such:
  
  cleartool mklabel TEST-ROOT .
  Created label 'TEST-ROOT' on '.' version '/main/1'.
  bash-3.00$ cleartool mklabel TEST-DIR DIR-A
  Created label 'TEST-DIR' on 'DIR-A' version '/main/1'.
  
  
  10)  Issue a ?cleartool ls -l?
  
  cleartool ls -l
  directory version      DIR-A@@/main/1
  Rule: element * /main/LATEST
  symbolic link          SYMLINK-DIR-A --? DIR-A
  directory version      lost+found@@/main/0
  Rule: element * /main/LATEST
  
  
  11)  Change the config spec as follows:
  
  element /vob/test TEST-ROOT
  element /vob/test/DIR-A TEST-DIR
  
  
  12)  Issue a ?cleartool ls -l?
  
  cleartool ls -l
  directory version      DIR-A@@/main/1
  Rule: element /vob/test/DIR-A TEST-DIR
  symbolic link          SYMLINK-DIR-A --? DIR-A [no version
  selected]
  directory element      lost+found@@ [no version selected]
  
     NOTE:  The symlink is not resolving
  
  
  13)  Change the config spec as follows:
  
  element /vob/test TEST-ROOT
  element /vob/test/DIR-A TEST-DIR
  element /vob/test/... FAKE-LABEL
  
  
  14)  Issue a ?cleartool ls -l?
  
  cleartool ls -l
  directory version      DIR-A@@/main/1
  Rule: element /vob/test/DIR-A TEST-DIR
  symbolic link          SYMLINK-DIR-A --? DIR-A
  directory element      lost+found@@ [no version selected]
  
     NOTE:  The symlink now resolves with the recursive check for
  a nonexistent label
  
  
  15)  Change the config spec as follows:
  
  element /vob/test TEST-ROOT
  element /vob/test/DIR-A TEST-DIR
  element /vob/test/* FAKE-LABEL
  
  
  16)  Issue a ?cleartool ls -l?
  
  cleartool ls -l
  directory version      DIR-A@@/main/1
  Rule: element /vob/test/DIR-A TEST-DIR
  symbolic link          SYMLINK-DIR-A --? DIR-A
  directory element      lost+found@@ [no version selected]
  
     NOTE:  The symlink now resolves with the wildcard check for a
  nonexistent label
  
  
  
  Workaround:  Temporarily modify the config spec, if possible, to
  include a wildcard or recursive rule.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  ClearCase config spec without an unrelated wildcard or
  unrelated recursive rule will not resolve the end point of a
  symlink
  

Problem conclusion

• This behavior is consistent back to ClearCase SR6.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels