Path Mappings
The YAML configuration file must contain the following path mappings:
path - The file path of the project, such as \MYFILE\COB). This path applies to any nested paths unless it’s defined separately, such as \MYFILE\COB\SOURCE.
- types - The YAML configuration file must contain the following two types:
- fileExtension - The file extension type for each path mapping (such as cob or clst)
- ispwType - The Code Pipeline type for each path mapping (such as COB or CLST)
The YAML configuration file can optionally contain the following types:
- cics - A ‘Yes’ or ‘No’ value indicating whether the source contains CICS
- flag1 - A user-defined flag with a one-character value
- flag2 - A user-defined flag with a one-character value
- flag3 - A user-defined flag with a one-character value
- flag4 - A user-defined flag with a one-character value
- genParms - A user-defined string with an 8-character value
- ims - A ‘Yes’ or ‘No’ value indicating whether the source contains IMS
- progType - A ‘Yes’ or ‘No’ value indicating whether the source is an executable component
- sql - A ‘Yes’ or ‘No’ value indicating whether the source contains SQL
The following is a sample of a YAML configuration file. You can also download for reference.
ispwApplication:
host: somehost.example.com
port: 12345
application: PLAY
subAppl: PLAY
assignmentPrefix: PLAY
runtimeConfig: RTCON
stream: PLAY
sandbox: Y
sandboxJoinAtLevel: STG1
pathMappings:
- path: \ASM
types:
- fileExtension: asm
ispwType: ASM
- path: \C
types:
- fileExtension: c
ispwType: C
- path: \CLST
types:
- fileExtension: clst
ispwType: CLST
- path: \COB
types:
- cics: 'No'
fileExtension: cob
flag1: A
flag2: B
flag3: C
flag4: D
genParms: GENPARMS
ims: 'No'
ispwType: COB
progType: 'Yes'
sql: 'No'
- path: \COPY
types:
- fileExtension: COPY
ispwType: COPY
- path: \JOB
types:
- fileExtension: job
ispwType: JOB
- path: \PLI
types:
- fileExtension: pli
ispwType: PLI
Multiple types can exist under the same path within the YAML file. In the following example path entry, the fileExtension and ispwType types are shown twice in the same path.
types:
\- fileExtension: cob
ispwType: COB
\- fileExtension: pli
ispwType: PLI
Java pattern matching
Code Pipeline/Eclipse supports using Java pattern matching. Pattern matching uses special characters to create a glob pattern and then relative path names can be compared against that pattern.
The following rules are used to interpret glob patterns:
- The * character matches zero or more characters of a name component without crossing directory boundaries.
- The ** characters matches zero or more characters crossing directory boundaries.
- The ? character matches exactly one character of a name component.
When the syntax is "glob", then the string representation of the path is matched using a limited pattern language that resembles regular expressions but with a simpler syntax. For example:
/home/*/* | Matches /home/gus/data on UNIX platforms |
/home/** | Matches /home/gus and /home/gus/data on UNIX platforms |
The expression string in YAML must be surrounded by double quotes.