A couple of questions regarding SCM command line tool

Hi

1. Why "scm" command line is so slow comparing to "cleartool"?

2. I seems "scm" command line can't be used together with RTC eclipse client, on the same workspace. If I have the RTC eclipse client open, and at the same time, run a scm command in the workspace, I will get an error like "file locked". This is weird, how if I want to debug something and want to run the same command from command line, then I have to close RTC first?

3. Workspace load status is not sync from RTC client and command line. In the (1st image) screen shot, same user, same workspace:
"Curam Development Stream Workspace" is already loaded in RTC, but "scm" doesn't know, and can't load again due to the lock.
"Curam Development Stream Build Workspace" is already loaded in "scm", but RTC doesn't know. Start a load will do re-load.

4. From RTC client, I can see there is nothing to deliver, but from command line, I can run deliver again and again, seeing nothing changed. see 2nd image.

5. If you look at image 2, it's asking for password for every command, why?

http://i56.tinypic.com/10p6hwj.png

http://i53.tinypic.com/2j0jjt0.png

1. Use 'lscm' instead of 'scm'. The 'lscm' starts a daemon in the background and subsequent invoke of lscm will not incur startup times.
2. If you use 'lscm' after starting the RTC Eclipse client you should not run into this issue. There is a known issue if you start lscm first and then the RTC Eclipse client.
3. a. Not sure what do you mean by "scm does not know", If you run 'lscm' in the sandbox it should show the status/pending changes.
3. b. Did you mean that the workspace loaded by scm cli is not recognized in RTC?
4. This has been fixed in 301. Now it should display "Nothing to deliver".
5. Was the login credentials cached? Can you run 'lscm ls cred' which lists all the repositories you have connected to and if the credentials have been cached?

1. Use 'lscm' instead of 'scm'. The 'lscm' starts a daemon in the background and subsequent invoke of lscm will not incur startup times.
2. If you use 'lscm' after starting the RTC Eclipse client you should not run into this issue. There is a known issue if you start lscm first and then the RTC Eclipse client.
3. a. Not sure what do you mean by "scm does not know", If you run 'lscm' in the sandbox it should show the status/pending changes.
3. b. Did you mean that the workspace loaded by scm cli is not recognized in RTC?
4. This has been fixed in 301. Now it should display "Nothing to deliver".
5. Was the login credentials cached? Can you run 'lscm ls cred' which lists all the repositories you have connected to and if the credentials have been cached?

3. That is how it works today. It is not automatically recognized because RTC Eclipse client doesn't know about the sandbox (not tracked) until you say load.
4. Please raise a defect.
5. The credentials was prompted because the url https://jazz.home.net:9443/ccm/ does not show up in your cached list.