z/OS Build Phases
The following z/OS Phases can be used for the z/OS Build 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 | Build Phase | Dependent on |
|---|---|---|
M |
/ |
|
M |
||
M |
||
O |
||
O |
||
O |
/ |
|
O |
||
O |
||
O |
Mandatory Phases
There are three basic, mandatory, z/OS Build Phases.
They complement two IKAN ALM core Phases, i.e., the Retrieve Code Phase (retrieving the content from the VCR into IKAN ALM) and the Transport Source Phase (transferring the Source files to the IKAN ALM 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 IKAN ALM Agent to the Target location on the IKAN ALM Agent. The following Phases in the sequence will only use the copied files from this Target location. |
2 |
Copy Sources to PDS for compilation |
This Phase copies the files (object types specified in the properties files) from the Target location on the IKAN ALM Agent into temporary PDSs on the z/OS Platform. Before the file transfers, temporary PDSs will be created, as well as the PDSs necessary for compiling the files selected in the next Phase. |
3 |
Maps and Programs compilation |
This Phase creates the compile JCL, submits the job and runs the actual compilation on z/OS for each Map and next each program. After the compilation, the Phase will control the result and collect all resulting files generated by the compile job (listing, load modules, generated DB2 dbrm files, …) in the target location for adding to the IKAN ALM Archive. |
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) Build Phases may be inserted in between or after the mandatory Phases, in any order required.
Exception: The optional Collect Idms Components Phase starts from the Source location and only copies and controls IDMS components. It is not dependent on any of the other Phases and, if required, it may be executed before the Copy from Source to Target Phase.