Step 4: Review Load Report
This step is performed to verify that correct Tasks will be loaded (without actually loading them). It uses the same Filtering and User Exits as the Task Load, so it is a useful tool to test any User Exits and to confirm that the Component registration process will work correctly.
Calling the Load Report
Option “R” from the M.AL screen (Option M.AL) invokes this function.
Processing Overview
Producing the Load Report involves the steps listed in the following table.
Producing the Load Report
Step | Description |
|---|---|
1 | Select Option “R” 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>. |
Filter List
When option “R” 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
In this example, 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.
Review the Report
After the job has been submitted, the report should be reviewed for completeness, because this is the basis on which the components will be registered to ISPW as tasks. An example report is shown in the following figure.
Sample Load Report
