Options supported by the mass import tool

This topic lists and briefly describes the options available through the mass import tool.
Run the mass import command, zimport, from the Rational Team Concert™ for System z® command line interface (CLI). The mass import tool supports the following options:
-r
For repositoryURI. Use this option to specify the location of the repository to which you want to import the partitioned data set (PDS) members.
-u
For user. Use this option to specify a user name for the repository.
-P
For password. Use this option to specify a repository password.
Important: Use a capital P for this option, not a lower case p.
--hlq
For HLQ. Use this option to specify the high-level qualifier (HLQ) of the partitioned data sets you want to import.
--mapfile
For file. Use this option to specify the location of the mapping file to use. This mapping file describes the structure of the project to which you want to import the PDS members. You must always specify the location of the mapping file, and your mapping file must contain the following two types of mapping:
  • Mapping from the PDS members to the zComponent project to which you want to import them.
  • Mapping from the zComponent project to the Jazz™ component to which the project belongs.
It is optional for your mapping file to contain mapping from members to their associated language definition.
Remember: The language definition must already exist in the specified project area.
--projectarea
For projectArea. Use this option to specify the name of the project area where the data set definitions that are related to the imported members should be stored. This should be the same project area where the related language definitions are stored.
-s
Optional: For stream. Use this option to specify the name, alias, or UUID of the stream you want to set as the default flow target for the repository workspace that is created with your mass import.
-q
Optional: For quiet. Use this option to suppress console output.
-v
Optional: For verbosity. Use this option to increase the output verbosity.

Mapping file format

The mapping file is line-delimited, wherein each line must follow this format: <identifier character> : <key> = <value> The table below indicates possible line combinations. For more information about mapping file rule restrictions, see Mass import tool mapping file format.
Table 1. Mass import line combinations
Identifier Key Value Notes®
C zComponent project name Jazz component name Specifies to which Jazz Component a zComponent project should belong. zComponent projects that do not match project name rules specified in the mapping file cannot be imported.
P1, 2 Fully qualified member name (not including HLQ) zComponent project name [:zFolder name] Specifies to which zComponent projects PDS members should be imported. You can use wildcards in the key, indicated by an asterisk (*), to specify multiple members to put into the same zComponent project. Any member that does not match a member name rule specified in the mapping file cannot be imported.
L1 Fully qualified member name (not including HLQ) Language definition name [:file suffix] Specifies a language definition to associate with imported members. Remember: The language definition must already exist in the project area. You can use wildcards (*) in the key to specify multiple members to associate with a language definition.
X1 Fully qualified member name (not including HLQ) none Specifies members to exclude from the mass import. You can use wildcards (*) in the key to specify multiple members to exclude. Any member that matches the given key will not be imported.
Important:
  1. For the P, L, and X identifiers, members are referenced using pattern-matching strings that consist of the name of the PDS (without the HLQ), followed by a period, followed by the member name. For example, member HELLO in PDS SMITH.TEST.COBOL would be matched by the pattern TEST.COBOL.HELLO. The pattern TEST.COBOL.* would match any members in the data set named SMITH.TEST.COBOL. By default, members are imported as zFiles with the same name as the member. You can specify a language definition name like this, for example:

    L:TEST.COBOL.*=COBOL:cbl

    When you append such a file extension, like .cbl, for example, two things happen:
    1. Language definition COBOL is associated with any members matching the rule.
    2. .cbl is appended to the filename of the zFiles you imported.
  2. For the P identifier, by default, zimport imports members from a PDS to the specified zComponent project into a zFolder with the same name as the PDS. Optionally, you can change the name of the zFolder by adding a colon (:) after the name of the zComponent project, followed by a zFolder name of your choosing. For example, if you want to import all members from a PDS named MORT.BLD.TEST to zComponent project MortgageApp under a zFolder named MORT.BLD, the mapping file rule should be P:MORT.BLD.TEST.*=MortgageApp:MORT.BLD.
  3. You can also make back references in any line in the mapping file by using parentheses in the key and %n in the value. For example, if you want to import all the members in any PDS named MORT.*.BLD.TEST to a zComponent project named MORTApp in zFolders named whatever is between MORT. and .BLD, you could write the rule as P:(MORT).(*).BLD.TEST.*=%1App:%2.

Feedback