Show modification status of items in a workspace.
Purpose
The scm status subcommand
reports on the Rational Team Concert™ source
control status
of items in a workspace.
Synopsis
- To run scm status after you have used scm
login to create stored credentials:
scm status { [ -d | --dir ] workspace-path [ -v | --verbose ] }
- To run scm status supplying credentials on
the command line:
scm status [ -u | --username ] user ID in repository [ -P | --password ] password for user ID in repository { [ -d | --dir ] workspace-path [ -v | --verbose ] }
Options and arguments
- [ -B | --xbaseline ]
- Expand baselines to see contained change-sets.
- [ -C | --xchangeset ]
- Expand change-sets to see changes and work
items.
- [ -d | --dir ] workspace-path
- The path name of a local workspace created
by scm load or scm share.
This subcommand runs with workspace-path set as
the current working directory. You can omit this option if the current
working directory is in a local workspace.
- [ -P | --password ] password for user ID in repository
- The password for the specified user ID in
the named repository. If this option is not included on the command
line, you are prompted for a password. If you specified a repository
URI or nickname for which you have stored credentials using the scm
login command, this option is ignored.
- [ -u | --username ] user ID in repository
- Specifies a user ID that exists in the named
repository. If you specified a repository URI or nickname for which
you have stored credentials using the scm login command,
this option is ignored.
- [ -v | --verbose ]
- Provide additional informational messages
while operating.
Examples
Working in a local workspace, check
the status to see whether there are any pending changes:
C:\local-workspaces\HelloJazz>scm status
Workspace: (1101) "HelloJazz" <-> (1102) "HelloJazz Stream"
Component: (1103) "HelloJazz"
Baseline: (1108) 3 "beta2 updates"
Unresolved:
m- /com.example.hellojazz.rcp.ui/client.launch
m- /com.example.hellojazz.client/src/com/example/hellojazz/client/build.p>
Outgoing:
Change sets:
(1116) --@ <No comment>
The results indicate that there are two unresolved
local changes.
Because you are working in a local workspace,
you do not need to specify the [ -d | --dir ] workspace-path option. scm
status gets the repository information from metadata associated
with the local workspace.