The rules in a mapping file are line-delimited, and the
following restrictions apply to mapping file rules:
- The mass import tool ignores blank lines.
- The mass import tool ignores lines that begin with the pound sign
(#).
- Lines must adhere to the following format, where rule-type must
either be the character P, the character C,
the character L, or the character X:
rule-type:key=value
- P indicates that the rule maps a qualified
member name to the zComponent project and, optionally, to the zFolder
where it should be placed.
Note: After the P rule,
you have the option of specifying a zFolder to which to import the
member. To do this, add [:zFolder] after the P rule,
but replace zFolder with the name of the folder
where you want to import the member. Such a line might look similar
to this: P:TEST.COBOL.HELLO=MyProject:MyFolder
Attention: The qualification of the member name in the P rule
does not include the high-level qualifier (HLQ).
- C indicates that the rule maps a zComponent
project to the Jazz™ component
that should contain it.
Important: If the zComponent project
into which members are imported does not match any C rules,
those members will not be imported.
- L indicates that the rule maps a qualified
member name (without a high-level qualifier) to the name of a language
definition to associate with it.
Note: After the L rule,
you have the option of specifying a file suffix to append to the imported
zFile. To do this, add [:file suffix] after the L rule,
but replace the file suffix with the file extension you want to append
to the zFile. Such a line might look similar to this: L:TEST.COBOL.*=COBOL:cbl.
Important: The specified language definition must already exist
in the project area that you specified on the command line. Specifying
language definitions for imported members is optional, and members
without an associated language definition can still be imported.
- X indicates members to exclude from the mass
import.
Important: Any member that matches the given X
key rule will not be imported.
The contents of a mapping file might look like the following
example:
# Member to zComponent project mappings
# Specify the zComponent project and, optionally, the zFolder that will
# contain the imported members.
#
# Format:
# P:<member>=<zComponent project>[:<zFolder>]
P:MORTGAGE.*.(*).*=MortgageApp:%1
P:ALL.COBOL.*CALC=CalcApp:CobolSrc
P:ALL.COBOL.ATM*=ATMApp:CobolSrc
# zComponent project to Jazz Component mappings
# Specify the Jazz Component that each zComponent project will be shared to.
#
# Format:
# C:<zComponent project>=<Jazz Component>
C:MortgageApp=Mortgage
C:CalcApp=Sample Applications
C:ATMApp=Sample Applications
# Member to Language Definition mappings
# Optionally specify the Language Definition to associate with imported members.
#
# Format:
# L:<member>=<Language Definition name>
L:*.COBOL.*=COBOL:cbl
L:*.JCL.*=JCL
# Exclusion rules
# List members not to import
#
# Format:
# X:<member>
X:*.OBJ.*
If you run the zimport command for a PDS
named SMITH.MORTGAGE.BLD.COBOL, indicate SMITH as
the --hlq, and specify the mapping file rule P:MORTGAGE.BLD.COBOL.*=MortgageApp,
all of the contents of SMITH.MORTGAGE.BLD.COBOL would
be imported into a zComponent project named MortgageApp, inside
a zFolder named MORTGAGE.BLD.COBOL. If, instead, you specify
mapping file rule P:MORTGAGE.BLD.COBOL.*=MortgageApp:CobolSRC,
the zFolder would be named CobolSRC.