Properties for the scm command line client can be controlled through the file. By default, the file resides in user home dir/.jazz-scm, but other locations can be specified by setting scm –config /path/to/other/location.

Repository Connection Timeout

Sets the connection timeout for contacting the repository. This is used to determine how long to wait when connecting to the remote repository. The value must be an integer number of seconds. The following would set the connection timeout to 10 minutes: repository.timeout: 600.

Default Password Mask

Controls whether the password prompt should attempt to mask user typing. Value may be either true, indicating that the password should be masked, or any other value to indicate that it should not. The following causes password keystrokes to be echoed when typed password.mask: false. The default is password.mask: true.

Content Download Threads

The command line client uses multiple threads to download content when possible. This value sets the maximum number of threads to use. The value must be a positive integer. The following command instructs the client to download up to 25 different items at a time: content.threads: 25 . The default is content.threads: 10

Pre-operation Refresh Policy

This value controls how the command line client handles uncommitted files discovered during download. By default, the command-line interface refreshes every file that may be modified during the download and warns the user if there are any uncommitted changes.This action is time consuming but safe. Users can prevent the refresh, and allow changes to be written to the Jazz backup shed. The value must be refresh, indicating that the client must refresh, or shed, indicating that the client must write uncommitted items to the backup shed. The default is local.collision.policy: refresh.

Maximum Check In Grouping

This value sets the maximum number of changes that are committed as an atomic group. If any single file upload fails in a commit smaller than this number, the entire check-in fails, and no changes are recorded in the remote workspace. The value must be a positive integer. If less than 10 files are checked in at one time, and one upload fails, no change set is modified. If 10 or more files are check in, and one upload fails, the remaining changes are stored in a change set. The following command sets the failure grouping to 10: commit.atomic.maximum: 10.

Dump exception on console

This value is used only in case of default logging. If the value is set to false, then the exceptions will only be logged. If the value is set to true, then the exceptions will be dumped on console in addition to logging it. The default is dump.exception: true.

Logging level

This value is used only in case of default logging. The levels in descending order are: SEVERE (highest value), WARNING, INFO, CONFIG, FINE, FINER, FINEST (lowest value). By default, logging level is set to SEVERE. This is to done to avoid bloating the disk with logs. log.level: SEVERE.

Disable Daemon Tracing

By default the SCM daemon records all interactions with clients for debugging purposes. The log can be disabled by setting the trace.disable configuration field. The value of the field does not matter. The following disables trace logging: trace.disable.

Daemon Trace Directory

By default the daemon records traces into the ~/.jazz-scm directory. The location can be changed by setting this value. Any valid file system path may be used. trace.dir: /home/user/traces/

Maximum Daemon Trace File Size

The daemon will rotate the trace file after it reaches a maximum size. Subsequent interactions will be recorded in a new file. Any positive integer value may be used. The following causes the trace file to rotate after it reaches 50 kilobytes in size: trace.file.max_size: 50000. The default is trace.file.max_size: 100000.

Daemon Trace File Compression

By default, the daemon compresses the trace file when rotating it. This value controls whether the compression should occur. Except in cases where performance is negatively impacted, or where the trace file size is extremely large, compression should be enabled. true and false are legal values. The following will disable compression: trace.file.compress: false. The default is trace.file.compress: true.

Maximum Daemon Trace Directory Size

The daemon will delete old trace files when the trace directory reaches a certain size. This value controls how large the total sum of trace file sizes may be before deletion occurs. Note: trace files are only purged after a trace file is being rotated. Any positive integer may be used. The follow will cause trace files to be deleted after the trace directory exceeds 800 kilobytes: trace.file.max_size: 800000. The default is trace.file.max_size: 1000000.

JSON Output

Setting this preference to true enables the JSON output for commands. The following will enable JSON output: json.output: true.


An optional external tool that you can configure to auto-resolve conflicts. If this tool is not configured, the built-in text merger is used.

Note: Some characters, such as " or $, can have a special meaning on certain operating systems. You may need to use escape characters to represent these characters. An example for Beyond Compare is: external.merge: "C:\Program Files (x86)\Beyond Compare 4\BComp.exe" "${file1Path}" "${file2Path}" /center="${ancestorFilePath}" /mergeoutput="${mergeFilePath}" /title1="${file1Title}" /title2="${file2Title}" /title3="${ancestorFileTitle}" /title4="${mergeFileTitle}" /automerge. To view examples for other common tools, run scm list prefererences –v.

Allow load into multiple sandboxes

Setting this preference to true suppresses the warning that is displayed when a workspace is loaded into a different location than when it was last loaded. It is recommended to leave it set to false and to add the --allow argument to the load command when required. The default is allow.multiple.sandbox.load: false.