show status example

status example


Working in a sandbox, check the status to see whether there are any pending changes:

C:\local-workspaces\HelloJazz>lscm show status
Workspace: (1101) "HelloJazz" <-> (1102) "HelloJazz Stream"
  Component: (1103) "HelloJazz"
    Baseline: (1108) 3 "beta2 updates"
      m-- /com.example.hellojazz.rcp.ui/client.launch
      m-- /com.example.hellojazz.client/src/com/example/hellojazz/client/build.p>

      Change sets:
        (1116) ---@ <No comment>

The results indicate that there are two unresolved local changes.

When working in a sandbox that contains workspaces loaded from different repositories, if one of the repositories is not reachable, then the output from the status command would be:
Workspace: (1021) "Server2 Workspace" (This workspace is unreachable.)
    Workspace: (1020) "Server1 Workspace" <-> (1020) "Server1 Workspace"  (ADMIN @ server1)
      Component: (1022) "Server1-Comp1"
        Baseline: (1024) 1 "Initial Baseline"
          Change sets:
            (1025) *--@  "Share" 24-Sep-2012 12:33 PM
                --a-- \Server1-Comp1\
             --a-- \Server1-Comp1\File1.txt
The above output indicates that there is a problem with connecting to the repository from which Server2 Workspace is loaded. The details about the problem occurred when connecting to that repository can be found in the log file. For more information, see Enabling default logging.

Because you are working in a sandbox, you do not need to specify the -d  |  --dir ] workspace-path option. scm status gets the repository information from metadata associated with the sandbox.