rpp-uploadsandbox

This command contains the Rational Team Concert™ scm commands that are required to upload the content of a sandbox to the Rational Team Concert server. It is called by the scmtools_entries.bat script file, which is produced by the migration.

Description of the command

This command completes the following tasks:
  • It creates the components if necessary (new projects),
  • It shares the new projects,
  • It checks in the modified projects,
  • It delivers the modifications.

Syntax

The following syntax is required:

scm rpp-uploadsandbox [options] [sandbox...] where [sandbox...] indicates the path to the sandbox.

Table 1. List of parameters
Options Comments Required
--certificate arg File that contains the user's login certificate. Yes
--smartCard Connected smart card for authentication. Yes
-c [--comment] arg  Comment on the change set. Yes
-k [--workitem] Number of a work item that is used to link all the change sets upon the upload to the server.

This work item must exist and must be configured to receive change sets (see the Rational Team Concert help).

The relevant .log files are automatically associated with this work item.

 
-l [--location] arg  Name of the Rational® Programming Patterns location. Yes
-m [--mapfolder] arg  Folder of the z/OS® language definitions mapping No
-N [--no-local-refresh] arg  Does not scan the file system for new changes. No
-P [--password] arg  Password to access the repository Yes
-p [--projectarea] arg  Name of the project area with which the components are to be associated.

It must exist before you run this command.

Yes
-q [--quiet]  Option to print the minimum of output during a normal process. No
-r [--repository-uri] arg  URI of the repository. Yes
-s [--stream] arg  Stream name.

It must exist before you run this command.

Yes
-t [--strategy] arg Strategy for the creation of change sets upon the upload to the server.
The two following values exist:
  • global is the default value. It corresponds to the creation of a change set for each component.
  • affinity is to be used only after the MIBJ procedure. The following rules apply then:
    • The generated files (.cbl for Programs, Screens, and Servers for example) and their associated metadata files (whose extension ends with pdp) are uploaded in the same change set.
    • Each design instance is uploaded, if possible, in the same change set as its generated file and associated metadata file.
    • Each non-generatable design instance is uploaded in a separate change set.
 
-u [--username] arg  User name, defined in Jazz™, to access the repository. Yes
-v [--verbose] Option to show more information. No
-w [--workspace] arg Name or UUID of the repository workspace.

You must indicate the same repository workspace to successively upload the data that comes from several Pacbase sessions.

If it does not exist, this workspace is created by the scmtools_entries.bat file.

Yes
-x [--createcobolcomp] arg Creation of a specific component for project .COB No
Note: --certificate arg and --smartCard are exclusive options. They are used for authentication when connecting to the Rational Team Concert server. You can connect by using one of the following elements:
  • A certificate
  • A smart card
  • A user/password identifier

Example

scm.exe rpp-uploadsandbox -r https://localhost:9443/ccm/ -u JAZZ -P JAZZ -w "MY_WKS" -l "MY_RPP_REPO" -p "TEST" -s "TEST" -c "TEST"

Feedback