Step 5: Load Tasks
This step is run to register the components for the Application to ISPW. It will populate an ISPW Assignment with an ISPW Task for each component.
Calling the Task Load
Option “T” from the M.AL screen (Option-M-AL) invokes this function.
Processing Overview
Producing the Task Load involves the steps listed in the following table. The first three steps are identical to those for Option “R”.
Producing the Task Load
Step | Description |
|---|---|
1 | Select Option “T” and specify Filter selections. |
2 | Press PF3 to create an initial report based upon just scanning the datasets (<prefix>.WALDSN.<APPL>.<LEVEL>). The JCL is also created to process the exits. |
3 | Submit the JCL. This processes the initial report with the exit WZUALX and produces the final report that corresponds to what will be loaded during the Task Load. The report name is: <prefix>.WALRPT.<APPL>.<LEVEL>. |
4 | The JCL then builds theISPW External Call Interface (ECI) commands from the report to load the components into ISPW as Tasks. These will be placed in the dataset named: <prefix>.WALECI.<APPL>.<LEVEL>. |
5 | The JCL then runs the ISPW ECI to load the tasks in ISPW. |
6 | Go into the ISPW Assignment and see the newly loaded Tasks. |
Filter List
When option “T” is selected, a list of all the Datasets defined for the Application/Stream and Level is presented, as shown in the following figure. This list is derived from the M.AD Tables.
List of Datasets Defined for the Application/Stream and Level
Using the same example as for Option “R”, a Member Pattern is selected for the COB Type and the LOAD library is removed. This would reflect an Application that follows a certain naming standard where the modules result in Object code only.
Pressing PF3 from this screen will cause all of the datasets to be scanned and the initial report and JCL to be created.
ECI Commands
The ECI Commands are built from the Report file and placed into the dataset <prefix>.WALECI.<APPL>.<LEVEL>.
ECI Commands
ECI Step
The final step of the Task Load JCL executes ISPW’s External Call Interface.
The ECI communicates with ISPW and processes each ECI command, loading the Tasks and associated Parts. This step should end with a return code of 0. Any errors are reported in the job output.
Assignment Tasklist
After the Task Load has been successfully run, the ISPW Assignment should be populated with the tasks as shown in the following figure.
Test Application Load
Note the last op of TL. This indicates that the task was loaded with the ECI Task Load call.
Entering the QP (Query Parts) operation will show that the parts have been successfully registered (Query Parts).
Query Parts
