z/OS Deploy Phases
The following z/OS Phases can be used for the z/OS Deploy process (M = Mandatory, O = Optional). The table indicates which other Phase they are dependent on. If there is no dependency, the Phase is working from the Source Environment location.
Click the name of one of the Phases in the table below to display all detailed information concerning the characteristics and usage of the Phase.
| M/O | Deploy Phase | Dependent on |
|---|---|---|
M |
/ |
|
M |
||
O |
||
O |
||
O |
||
O |
||
O |
/ |
|
O |
||
O |
||
O |
||
O |
||
O |
||
O |
||
O |
||
O |
||
O |
/ |
|
O |
||
O |
||
O |
||
O |
Mandatory Phases
There are two basic, mandatory, z/OS Deploy Phases.
They complement two Kobee core Phases, i.e., the Transport Build Result Phase (retrieving the content from the Build Archive into Kobee) and the Decompress Build Result Phase (unzipping the Archive files to the Kobee Source location).
| Sequence | Solution Phase | Usage |
|---|---|---|
1 |
Copy from Source to Target |
This Phase selects the files that need to be copied, using predefined filters and include/exclude masks. Next, the selected files are copied from the Source location on the Kobee Agent to the Target location on the Kobee Agent. The following Phases in the sequence will only use the copied files from this Target location. |
2 |
Promotion of components and load-modules |
This Phase copies the z/OS files selected from the Environment Target to their respective z/OS PDSs. The load-modules are copied to temporary sequential files and a JCL is created and submitted for receiving them in their PDSs. |
IMPORTANT:
The following sequence rules must be followed.
-
The mandatory Phases must be used in the sequence order specified in the table above.
-
The other (optional) Deploy Phases may be inserted in between or after the mandatory Phases, respecting the dependency rules.