Task Load – Load Parts
Purpose
This (optional) call is only used in conjunction with a TASK LOAD. It is used to define the individual parts associated with a component (for example, DBRM, load module, listing, etc.). Each Part must be defined in accordance with the Associations defined in Code Pipeline for the specific Component Type and Application the Part is associated with. Zero to many calls of this type follow a TASK LOAD.
API Parameter List
ECIR, TSIP
The ECIR Data Structure must have the values in the following table set.
ECIR Data Structure Values for Task Load – Load Parts
Parameter | Value |
|---|---|
OBJECT | TASK |
METHOD | LOADPART |
JCL Invocation
$DEFINE_TSIP
TSIP Data Structure
The TSIP data area contains details required to add the Parts associated with a Component. The TSIP layout is described in the following table.
TSIP Layout
Position | Length | Type | Description | JCL Keyword | API | JCL |
|---|---|---|---|---|---|---|
1 | 4 | CHAR | Target Environment, as indicated in the Code Pipeline Associations, to correctly identify where this Part is stored | TENV | Optional | Optional |
5 | 4 | CHAR | Set value as specified in the Code Pipeline Associations which relates to this Part (for example, GMT1) | ASSCSET | Mandatory | Mandatory |
9 | 1 | CHAR | Sequence value as specified in the Code Pipeline Associations which relates to this Part (for example, 2) | ASSCSEQ | Mandatory | Mandatory |
10 | 64 | CHAR | Name of the Part | PARTNAME | Mandatory | Mandatory |
153 | 1 | CHAR | Indicates whether this part is using SIMP collection: blank - part is not using SIMP collection (default) | SIMPFLAG | Optional | Optional |
154 | 8 | CHAR | SIMP collection type | SIMPTYPE | Optional | Optional |
162 | 4 | CHAR | SIMP collection class | SIMPCLAS | Optional | Optional |