It's all about the answers!

Ask a question

problem using the lscm get change command

samuel wang (321923) | asked Apr 16 '14, 4:09 p.m.
edited Apr 16 '14, 7:03 p.m. by Geoffrey Clemm (30.1k33035)

I am testing the commands of the RTC client, problem I have:

1.      Not able to get data as expected when using command:  “lscm get change …” , need some examples. See the results below when using this command


2.      Is it possible to get data from stream directly by using command line or Java API? 

3.      Is it possible to automatically update my workspace in RTC server side when there is change(checked in by other team members)  in the stream, if so, how to configure the server to do that?


Another question is about the server console,

Not able to get email notification while creating new userId in the server admin console after re-installing RTC server, the password generated by server is in the email, so the new userId cannot be used,    I was able to do.

C:\dataRTC\RTCProjectArea Default Component>lscm get change 1017 / c:\dataRTC
Problem running 'get change':
"C:\dataRTC" already exists. Specify another path or use --overwrite option to o
verwrite the file.

C:\dataRTC\RTCProjectArea Default Component>lscm get change -o 1017 / c:\dataRTC

Problem running 'get change':
"C:\dataRTC" is not a file. Please specify a file name.

C:\dataRTC>lscm load -r -u admin -P ad
min --all -i 1010 --force
Successfully loaded items into the sandbox.

C:\dataRTC>cd "RTCProjectArea Default Component"

//After load data to local workspace, it can get result, but not as expected, it only gets one file,

C:\dataRTC\RTCProjectArea Default Component>lscm get change -o 1014 *.* *.*
Successfully extracted file to "C:\dataRTC\RTCProjectArea Default Component\WebE

C:\dataRTC\RTCProjectArea Default Component>lscm get change -o 1017 *.* *.*
Problem running 'get change':
Unable to extract file.
Load could not be completed because it would overwrite unchecked-in local changes.
An error has occurred. Kindly check the log for more details.

after delete files in local workspace, not able to get data using this command.

2 answers

permanent link
Shashikant Padur (4.2k27) | answered Apr 18 '14, 6:37 a.m.
edited Apr 18 '14, 6:38 a.m.
'lscm get change' is used to get individual changes from the change set.
For ex:
List the components of a stream:
$ lscm ls comp "Test"
Workspace: (1019) "Test"
  Component: (1020) "Comp1"
  Component: (1022) "Comp2"

Show history of "Comp1" in workspace "Test":
$ lscm show history -w 1019 -C 1020
Change sets:
  (1058) ----$ Sridevi Sangaiah "<No comment>" 03-May-2013 02:51 PM
  (1059) ----$ Sridevi Sangaiah "<No comment>" 03-May-2013 02:47 PM
  (1060) ----$ Sridevi Sangaiah "initial share" 03-May-2013 01:34 PM
  (1061) ----$ Sridevi Sangaiah "Initial for Comp1" 03-May-2013 01:30 PM

List the changes of the last change set in history:
$ lscm ls changes 1058 -w 1019
Change sets:
  (1058) ----$ Sridevi Sangaiah "<No comment>"
    Component: (1020) "Comp1"
    Modified: 03-May-2013 02:51 PM
      ---c- (1062) /comp1/file1.txt
      ---c- (1063) /comp1/file2.txt

Get the file from the change set:
$ lscm get change 1058 comp1/file1.txt /tmp/file1.txt
Successfully extracted file to "/tmp/file1.txt".

Alternatively you can specify the alias of the change in the change set:
$ lscm get change 1058 1062 /tmp/file1.txt
Successfully extracted file to "/tmp/file1.txt".

permanent link
Tim Mok (6.6k38) | answered Apr 21 '14, 11:37 a.m.
You cannot configure the server to automatically update a workspace when there are changes. It is an odd thing to do because it may unintentionally put a sandbox out-of-sync when the repository workspace backing it changes without the sandbox owner doing anything.

You should open another question about your email issue. That isn't related to the command line and will get more attention as a separate question.

Your answer

Register or to post 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.