Workaround: SCM operations may fail when using Rational Team Concert ISPF Client to load a repository when one is already loaded
Problem
The Rational Team Concert ISPF daemon creates and controls .jazzlock files for each repository workspace that a user ID loads. The .jazzlock files are acquired under ISPF daemon control when the user ID logs in. When an ISPF user ID loads a second repository workspace to a sandbox (to the same HFS UNIX directory or using the same data set prefix), the daemon tries to lock the /.jazz5/.jazzlock file in the sandbox and fails. The Pending Changes panel contains the error:
Error listing unresolved.
When you click the error message, the extended error message is:
Unable to lock file /<z/OS or UNIX sandbox>/.jazz5/.jazzlock
Note: All registered sandboxes for an ISPF user ID corresponding to their loaded repository workspaces are stored in the permanent ISPF table named BLZLOADS for the user.
Workaround
To avoid the error, when you use the ISPF client to load a repository workspace:
- Do not select a data set prefix location that is already used for another loaded repository workspace.
- Do not select a z/OS UNIX directory location that is already used for another loaded repository workspace.
Related information
Copyright © 2013 IBM Corporation
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means.
Learn more here.
Yes