Command line tools fail to run after upgrade from 3.0.1.5 to 4.0.1 - mkroot problem?
![]()
After upgrading the from 3.0.1.5 to 4.0.1 I'm unable to run the command line tools without setting SCM_ALLOW_INSECURE environment variable.
When I run them I see: $ lscm statusIf I modify the lscm script and provide an explicit definition for RTC_SCRIPT_BASE to /opt/IBM/SDP/scmtools/eclipse/scripts/unix (where mkroot is installed to my system) still no look. I can execute mkroot directly from the same shell I'm running lscm from so this doesn't appear to be a permission problem as has been reported in other posts. Is there a workaround for this? What's the risk associated with setting SCM_ALLOW_INSECURE? Cheers, Tim |
3 answers
![]()
It looks like that error message can result from a failure of the mkroot script and not only just because the script could not be found.
You could try and set the environment variable "trace_permission_utils" which will cause the scm tool to output tracing/debugging status to stderr. Perhaps this output would give more indication of what is going wrong. You might want to use "scm" while debugging this, I'm not entirely sure where the lscm error output is going. I'm not really sure what the impact of SCM_ALLOW_INSECURE is. |
![]()
I have just had the same issue and raised a call with IBM support. Their solution was to set $RTC_SCRIPT_BASE and $PRGPATH. However you should set these to /opt/IBM/SDP/scmtools/eclipse/scripts. You might need to stop all running scm and java processes and move /home/tbartley/.jazz-scm so that the directory gets created with the correct permissions.
|
Your answer
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.