Subcommand exit codes commands set an exit status to indicate success or failure, and provide additional information to the caller. source control managementsubcommand exit codes

Scripted execution of command line tools can make use of the following exit status codes to make execution or flow control decisions. Value Status 1 There was a syntax error on the command line. 2 The client could not connect to the named repository URI with the credentials supplied by the user. 3 A failure occurred for an unknown reason 4 An internal error indicating that a subcommand could not be loaded. 5 The local workspace is misconfigured (its root could not be found, or is not shared). 6 A resource name collision was detected in the local workspace. An unshared resource in the local workspace has the same name as a shared resource in the repository workspace. This prevented the shared resource from being loaded. 7 A failure occurred due to an unknown internal error 8 The requested operation could not be completed because the local workspace is out of sync with the repository workspace. The user should reload or re-share the local workspace. 9 The requested operation could not be completed because a selector (name, alias, or UUID) supplied by the user either does not match enough items, or matches too many. 10 not used 11 There is a resource conflict in one or more repository workspaces accessed by the subcommand. The user must resolve those conflicts before continuing. 12 An unknown subcommand name was used. 13 reserved (OSGi exception) 14 A request to move a resource failed because the target exists and is unshared, or the target path is invalid. 15 Remote data changed during command execution. Re-run the command. 16 The requested operation could not be completed because it would introduce a gap into the change set history. 17 The requested operation was blocked by Team Process. 18 The requested operation failed because the user lacked one or more repository permissions. The message returned provides more information about the failure. 19 The requested operation could not complete because preconditions were not met. 20 The requested operation attempted to transfer a file that has improper line terminators or encoding. 21 The requested operation could not complete because it would create an n-way conflict in the change set history. 22 The requested operation could not complete because it would create one or more items that have no parent. 23 reserved (OSGi exception) 24 reserved (OSGi exception) 25 One or more specified repository items were not found. 26 Server error. 27 The local workspace is in use by another RCP process (an eclipse GUI or another command line client). 28 The requested operation could not complete because the repository workspace is misconfigured: the client could not find an item in the repository workspace. The user should verify that any repository workspace paths are correct. 29 The requested operation could not complete because of a license limitation.